pombreda / libkml

Automatically exported from code.google.com/p/libkml
Other
0 stars 0 forks source link

0.3.2 buld generates no .java files #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. cd build; ../configure --with-java-include-dir=/opt/jdk1.6.0_06/include
--with-java-lib-dir=/opt/jdk1.6.0_06/lib
--with-python-include-dir=/usr/local/python/include/python2.5
--with-python-lib-dir=/usr/local/python/lib/python2.5

2. make

What is the expected output? What do you see instead?
Should have .java files in build/src/swig.  No java files are generated
there.  I DO get the kmldom.py file, and I also get the
libkmldom_swig_java.so library.  The configure/build completed with no
errors reported.

What version of the product are you using? On what operating system?
libkml 0.3.2, RHEL 4u4.

Did you run the unit test suite that comes with the project? Did all test pass?
Didn't get that far.

Please provide any additional information below.

Original issue reported on code.google.com by wedg...@gmail.com on 16 Jul 2008 at 7:04

GoogleCodeExporter commented 9 years ago
Version 0.4.0 does not seem to have corrected this problem.

Original comment by wedg...@gmail.com on 15 Aug 2008 at 7:41

GoogleCodeExporter commented 9 years ago
It appears that the section of build/src/swig/Makefile with the calls to swig is
never reached.  No .java files are made, neither kmldom_java.cc nor 
kmlengine_java.cc
is made, and the Python files are not copied out of their source location.  I 
can run
swig from the command line with the same options as the Makefile, and 
everything is
created properly.

Original comment by wedg...@gmail.com on 20 Oct 2008 at 3:44

GoogleCodeExporter commented 9 years ago
Same happens with .9 release

Original comment by RyanRett...@gmail.com on 4 Mar 2009 at 1:47