[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Debugging gideon with kdevelop 2.1.5
From:       Mario Scalas <mario.scalas () libero ! it>
Date:       2003-02-25 22:31:50
[Download RAW message or body]

Hi all,
	i'd like to write a part for gideon with the goal of evaluating code metrics. 
Since I'm pretty new to kde development I'd like to spend some weeks looking 
at the code to familiarize (ok, actually I may need more time ;) with it. I'd 
also like to use the last kdevelop 2.1.5 to do my tests but here I got in 
troubles with gideon's plugins architecture: to retrieve all the plugins at 
gideon start-up!

I checked the kde developer faq and found one (they are unnembered so I can't 
give you the correct reference) which suggests to add symlink .libs  to lib 
and add it to the $KDEDIRS env variable. I need to already do this in a 
couple of cases so nothing new. The problem is:

mario@xamel kdevelop $ find . -name *.so
./lib/.libs/libkdevelop.so
./lib/qextmdi/src/.libs/libkdevelopqextmdi.so
./parts/cvs/.libs/libkdevcvs.so
./parts/cvs/globalcvs/.libs/libkdevglobalcvs.so
./parts/diff/.libs/libkdevdiff.so
./parts/phpsupport/.libs/libkdevphpsupport.so
./parts/ctags/.libs/libkdevctags.so
./parts/tools/.libs/libkdevtools.so
./parts/grepview/.libs/libkdevgrepview.so
./parts/doxygen/.libs/libkdevdoxygen.so
./parts/konsole/.libs/libkdevkonsoleview.so
./parts/perlsupport/.libs/libkdevperlsupport.so
./parts/perlsupport/.libs/kio_perldoc.so
./parts/distpart/.libs/libkdevdistpart.so
./parts/appwizard/.libs/libkdevappwizard.so
./parts/pythonsupport/.libs/libkdevpythonsupport.so
./parts/pythonsupport/.libs/kio_pydoc.so
./parts/filecreate/.libs/libkdevfilecreate.so
./parts/fileview/.libs/libkdevfilegroups.so
./parts/fileview/.libs/libkdevfileview.so
./parts/abbrev/.libs/libkdevabbrev.so
./parts/fortransupport/.libs/libkdevfortransupport.so
./parts/astyle/.libs/libkdevastyle.so
./parts/regexptest/.libs/libkdevregexptest.so
./parts/cppsupport/.libs/libkdevcppsupport.so
./parts/debugger/.libs/libkdevdebugger.so
./parts/trollproject/.libs/libkdevtrollproject.so
./parts/javadebugger/.libs/libkdevjavadebugger.so
./parts/filter/.libs/libkdevfilter.so
./parts/outputviews/.libs/libkdevoutputviews.so
./parts/antproject/.libs/libkdevantproject.so
./parts/javasupport/.libs/libkdevjavasupport.so
./parts/texttools/.libs/libkdevtexttools.so
./parts/openwith/.libs/libkdevopenwith.so
./parts/uimode/.libs/libkdevuichooser.so
./parts/editor-chooser/.libs/libkdeveditorchooser.so
./parts/history/.libs/libkdevhistory.so
./parts/classview/.libs/libkdevclassview.so
./parts/scriptproject/.libs/libkdevscriptproject.so
./parts/autoproject/.libs/libkdevautoproject.so
./parts/fileselector/.libs/libkdevfileselector.so
./parts/visualboyadvance/.libs/libkdevvisualboyadvance.so
./parts/valgrind/.libs/libkdevvalgrind.so
./parts/doctreeview/.libs/libkdevdoctreeview.so
./parts/doctreeview/.libs/kio_kdeapi.so
./parts/tipofday/.libs/libkdevtipofday.so
./parts/perforce/.libs/libkdevperforce.so
./parts/qeditor/.libs/libqeditorpart.so
./parts/buglist/.libs/libkdevbuglist.so
./parts/customproject/.libs/libkdevcustomproject.so
./plugins/gccoptions/.libs/libkdevgccoptions.so
./plugins/pgioptions/.libs/libkdevpgioptions.so

That's a lot of dirs to add to $KDEDIRS. So what I ask is: what is the most 
correct approach to address this? Am I missing anything else?

Thanks for any clarifying answer ;)
Mario

-- 
Mario Scalas <mario.scalas at libero.it>
Homepage: http://digilander.iol.it/zakuteam

"Miser, miser! Modo niger et ustus fortiter."


_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]