Building Processing from source (Windows)

antony74

Building Processing from source (Windows)

in Integration and Hardware • 1 year ago

Hi,

I've run into trouble trying to build Processing from source on Windows. I'm an experienced programmer but I'm afraid this particular task is completely new for me. Can anyone shed any light on this error for me, please? - It's semi-transient in that I did get a lot further earlier, but once I hit this problem the only way I've been able to make it go away is to delete my entire source tree and get it again from svn.

Thanks in advance for any assistance, -Antony.

D:\processing-read-only\build>svn info
Path: .
Working Copy Root Path: D:\processing-read-only
URL: http://processing.googlecode.com/svn/trunk/processing/build
Repository Root: http://processing.googlecode.com/svn
Repository UUID: fe3ceab9-de17-3b67-bb2e-7d58edd5e4d6
Revision: 10263
Node Kind: directory
Schedule: normal
Last Changed Author: fry@processing.org
Last Changed Rev: 10224
Last Changed Date: 2012-09-10 22:01:26 +0100 (Mon, 10 Sep 2012)

D:\processing-read-only\build>ant run
Buildfile: D:\processing-read-only\build\build.xml

run:

revision-check:

windows-checkos:

subprojects-build:

compile:

BUILD FAILED
D:\processing-read-only\build\build.xml:52: The following error occurred while e
xecuting this line:
D:\processing-read-only\build\build.xml:96: The following error occurred while e
xecuting this line:
D:\processing-read-only\core\build.xml:13: java.lang.IllegalStateException: No m
atch found
        at java.util.regex.Matcher.group(Matcher.java:485)
        at PAppletMethods.process(PAppletMethods.java:220)
        at PAppletMethods.execute(PAppletMethods.java:94)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:392)
        at org.apache.tools.ant.Target.performTasks(Target.java:413)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
        at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(Single
CheckExecutor.java:38)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
        at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
        at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:303)
        at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:221)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:392)
        at org.apache.tools.ant.Target.performTasks(Target.java:413)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
        at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(Single
CheckExecutor.java:38)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
        at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
        at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)

        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:392)
        at org.apache.tools.ant.Target.performTasks(Target.java:413)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:41)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
        at org.apache.tools.ant.Main.runBuild(Main.java:811)
        at org.apache.tools.ant.Main.startAnt(Main.java:217)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)

Total time: 0 seconds

D:\processing-read-only\build>

Replies(6)

antony74

Re: Building Processing from source (Windows)

11 months ago

I'm still in the market for an answer to this if anyone can help please? Or for that matter has anyone done a successful Windows build of Processing recently?

(Perhaps I should go buy a book about Ant (e.g. Ant in Action), since when I tried building in Ubuntu as a work-around, I wasn't able to make much of that error message either).

Manindra29

Re: Building Processing from source (Windows)

11 months ago

I've been building Processing on Windows and I've not seen this error before. I'd suggest updating the trunk to the latest revision - 10311 as of this post. (It'd be best if you checkout a fresh copy). Then do a ant clean, and then ant build.

And, make sure you're on java 1.6.

Also, is this the first time you're building on Windows and getting this error?

antony74

Re: Re: Building Processing from source (Windows)

11 months ago

Thanks for the advice. I've done a fresh checkout.

JAVA_HOME=d:\jdk1.6.0_37

I've also installed Quick Time, as the build instructions are a bit vague about whether it's still a dependancy.

I'm afraid I'm still getting the same error :-(

Yes, I'm new to building Processing so this is the first time.

ben.fry

Re: Building Processing from source (Windows)

11 months ago

All the Windows releases are built from Windows itself, so yes, the build.xml is up to date.

What sort of line endings are being used in the files inside core/src/processing/core/*.java?

And if you do "java -version", you get a Sun/Oracle JDK, right?

antony74

Re: Re: Building Processing from source (Windows)

11 months ago

Line endings. Thanks Ben, you're a genius!

I didn't think it mattered because the build wasn't getting far enough to be anywhere near a compiler, but I guess Ant does some pre-parsing or something. Perhaps it's a pity it chokes so easily and opaquely on something as trivial as whitespace. Or perhaps it serves me right for editing a file in Microsoft Visual Studio which is what I'm used to. I've installed Eclipse too now, and that seems to be fine.

So yes I've got this sketch which is cross-compatible between Java and Javascript modes...

http://www.openprocessing.org/sketch/74982

...and it was driving me crazy there was a single line I had to comment in or out every time I flipped mode...

String eval(String sCode) {return "";}

...so I've compiled it into my Processing core and (now that it's got the right line ending) everything's working great now. Thanks again for your help! :-)

antony74

Re: Building Processing from source (Windows)

11 months ago

Ah, so it's a regex query inside of a custom Ant task inside of Ant that was failing, is it?

Would it be possible to improve the logging generated if this happens? - It's quite a steep learning-curve for someone who was a complete newbie to Ant, the Processing source code, and indeed Java projects this big in general. I think I understand what's going on now, though.

I don't think it was line-endings, I think it was because I'd put the whole of my new function on a single line - both the declaration and the body, and PAppletMethods was executing some code for handling semi-colons at the end of abstract function definitions, on the code inside my curly brackets. If I use the expected coding style then the problem goes away.

Anyway, this source code change...

https://github.com/Antony74/Processing/commit/ed73b5d683b6d173d954b6a1452bd7d3803b1686

...changes this error message...

java.lang.IllegalStateException: No match found

...to this instead...

java.lang.RuntimeException: No match found while parsing PGraphics.java line 140. Check coding style?

...would that be an improvement?

Best wishes,

Antony

Top Reply