[Fwd: Build problem with the new KDevelop]

Richard Dale Richard_Dale at tipitina.demon.co.uk
Thu Jun 14 12:42:07 UTC 2001

On Thu, 14 Jun 2001, Ralf Nolden wrote:
> could you give Ian a hand ? :) I'd like him to make his kpp stuff as a
> gideon plugin so we have that done as well.
> Maybe adding that to the README or something would help for now.
Yes, I'll try and do that. 

ian reinhart geiser wrote
> Hey I am trying to build the new kdevelop but make -f Makefile.cvs fails with 
> a problem with $JVMLIBS not being defined.  Do you know where or how i set 
> that?

There is a macro in kdelibs/aclocal.m4 called KDE_CHECK_JAVA_DIR, which looks
for various Java resources - javac, jni.h and the libraries for the JVM and
Java thread library. The macro is expecting the thread lib to be called
'libhpi.so'. Is the problem that it is called 'libthreads.so' or similar
instead on your machine?

dnl Look for libjvm.so
kde_cv_java_libjvmdir=`find $kde_cv_java_bindir/.. -name libjvm.so | sed 's,libjvm.so,,'|head -n 1`
dnl Look for libhpi.so and avoid green threads
kde_cv_java_libhpidir=`find $kde_cv_java_bindir/.. -name libhpi.so | grep -v green | sed 's,libhpi.so,,'`

> p.s. as soon as i can build the bugger i can start testing the kpp plugin :)
Is the plugin written in Java then, as Gideon now builds without Java support by
default?  If the plugin is C++ you shouldn't need to get Java configured. 

-- Richard

to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«

More information about the KDevelop-devel mailing list