Hi Augustin, On Friday, 2011-02-25, augustin wrote: > Hello, > > My name is Augustin and this is my first post on this mailing list.
Welcome to KDE development :) > http://www.dwheeler.com/program-library/Program-Library-HOWTO/x36.html > shows that LD_LIBRARY_PATH can be set on the command line to override the > library load directory. > > What would the equivalent be for a KDE plugin? KDE basically looks at a list of search paths configurable through $KDEDIRS. See the output of kde4-config --path module for your current setup. > I am just starting to learn how to modify some KDE applications. > I did a first test by modifying a plugin that is normally installed in > usr/lib/kde4. However, for obvious development and testing purposes, I do > not want to overwrite the files from my distro's official packages. > How to I start a KDE application so that it looks for the plugin within my > build directory? What environment variables should I set? When not explicitly specifying /usr as the installation prefix, KDE's build system will install into /usr/local, so you could just install there if /usr/local is already in the search list of your current KDE configuration. This has the advantage (assuming matching versions) that your main KDE session can load your new plugin. You can specify a different installation prefix at cmake time using option -DCMAKE_INSTALL_PREFIX=/your/install/path In this case you have to add this as an additional prefix to $KDEDIRS, I think your TechBase wiki has instructions on how to setup a development account. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
