[Kst] Re: OS X plugin directory for non-installed build

Ted Kisner tskisner.public at gmail.com
Thu Dec 2 18:06:42 CET 2010

ok, I guess I should go read the documentation some more :-)  I also see that there is a conditional statement in the *.pro files when linking kst.  On OS X it sets LIBS to the framework path and uses qtAddLibrary.  On Linux it just adds the link flags directly.  This same switch is currently needed in d2asc and all the plugin directories.

Seems like we could unify this a bit.

I'll send an email by the end of the day with an update on all the OS X issues / fixes.


On Dec 2, 2010, at 9:00 AM, Peter Kümmel wrote:

> On 01.12.2010 20:46, Ted Kisner wrote:
>> The DMG bundles work great for installing on OS X.  For development testing, I just run from the build directory and set DYLD_FRAMEWORK_PATH and it works fine (rather than using macdeploykst to put files in /Library/Frameworks).  The one problem is that it does not find the datasources.  The data source files are in build/plugin and also (following what is done in macdeploykst) I copied them to build/bin/kst2.app/Contents/PlugIns.  Neither of these directories is searched by the datasource plugin manager.  I needed to add the attached patch to the search path.
>> cheers,
>> -Ted
> I read about changing the search path in the qt doc
> http://doc.trolltech.com/4.7/deployment-mac.html
> but ofter having no problems with the dmg I didn't patch the code.
> Does the changed of the doc also work?
> Is it an advantage to add the plugin path relative to the binary?
> Peter
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst

More information about the Kst mailing list