Compiling HEAD on a KDE 2.2 system ( libraries paths ?)

Hugo Varotto hugo at varotto-usa.com
Sat Sep 15 14:33:58 UTC 2001


Greetings,

I got the latest version from CVS yesterday, and compiled it with the switch 
--enable-gideon-qt2 to use QT 2.3.1 Before that, I moved my previous Gideon 
directory to another place and got everything from the CVS server ( I wanted 
to make sure that there were no problems with the code that I'm currently 
writing ).

Everything compiled fine, did and installation and everything was fine ( so 
it seems ). So, I copied my new parts subdirectories to the parts directory, 
continued working, compiled the new parts, installed and tried to test. 
Horror ! it wasn't working ! ( not that I'm very surprised, my code never 
works at the first, second or third try ;-)  

So I started to debug, couldn't find any particular problem, and then I 
realized ( after modifying the GUI a little bit ), that what I was actually 
running was the previous version that I had compiled two days ago ( which 
were located at /opt/kde/lib/kde2 ). The new versions ( and actually, all the 
new Gideon parts compiled in the last day after getting the latest HEAD ) 
were however installed in /opt/kde/lib/kde3  ( the acinclude.m4.in in the 
admin directory defines the library path to be lib/kde3 now ).

No problem,I thought, I'll just copy everything in kde3 to kde2. Didn't work, 
Gideon crashes now. OK, I'll just delete the versions inside lib/kde2, but 
now Gideon cannot find the new versions of the parts ( included the ones that 
were coming from the CVS version ).

SO... my question is, what do I need to set up/modify so that 
/opt/kde/lib/kde3 is also included in the library search path ? ( I have no 
problems in having a version for KDE 3 and another for KDE 2). I looked at 
LD_LIBRARY_PATH  and ld.so.conf and there're no references to 
/opt/kde/lib/kde2 anywhere, just to /opt/kde/lib in LD_LIBRARY_PATH. I think 
I could go and modify the acinclude.m4.in file to put lib/kde2 as the 
installation path and recompile everything, but that doesn't sound too 
elegant, portable, etc

Hugo










-
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