Closed GoogleCodeExporter closed 9 years ago
Building n Windows is hard. Try making sure JAVA_HOME is defined with forward
slashes '/' in the path name not back-slashes.
Original comment by art.cla...@gmail.com
on 28 Oct 2009 at 1:36
JAVA_HOME with forward slashes '/' does not help:
...
configure:16774: checking for javac
configure:16790: found /c/Program Files/Java/jdk1.5.0_16/bin/javac
configure:16801: result: javac
configure:16813: checking for java include file jni.h
configure:16841: result: C:/Program Files/Java/jdk1.5.0_16/include
configure:16865: checking for java include file jni_md.h
configure:16869: result: not found
configure:16871: error: in
`/d/EclipseWorkspace/xuggle/xuggle/java/xuggle-xuggler/build/native/i686-pc-ming
w32':
configure:16876: error: Could not find required Java header file jni_md.h.
Try defining JAVA_HOME to point to where you've
installed the JAVA JDK
Original comment by luzifer42
on 28 Oct 2009 at 3:22
ah, yes -- turns out that the build system on windows doesn't deal well with
paths
with spaces in it. Try setting JAVA_HOME to c:\Progra~1\Java\jdk1.5.0_16.
For reference on our windows build server here's where we set JAVA_HOME to (and
install our JDK):
c:\software\java\jdk1.5.0_19
Marking this Invalid because, while a bug in the autoconf tool suite, it's not
something we'll fix.
- Art
Original comment by art.cla...@gmail.com
on 28 Oct 2009 at 4:15
JAVA_HOME without spaces does not help either:
...
configure:16774: checking for javac
configure:16790: found /c/Progra~1/Java/jdk1.5.0_16/bin/javac
configure:16801: result: javac
configure:16813: checking for java include file jni.h
configure:16841: result: C:/Progra~1/Java/jdk1.5.0_16/include
configure:16865: checking for java include file jni_md.h
configure:16869: result: not found
configure:16871: error: in
`/d/EclipseWorkspace/xuggle/xuggle/java/xuggle-xuggler/build/native/i686-pc-ming
w32':
configure:16876: error: Could not find required Java header file jni_md.h.
Try defining JAVA_HOME to point to where you've
installed the JAVA JDK
Original comment by luzifer42
on 29 Oct 2009 at 7:30
The problem is that 'find' is used to find jni_md.h
But here, c:\windows\system32\find.exe was used instead of msys\bin\find.exe.
Reordering the paths fixed this problem.
avoiding find, or checking the find version would help.
Original comment by luzifer42
on 29 Oct 2009 at 7:54
Original issue reported on code.google.com by
luzifer42
on 28 Oct 2009 at 8:32