Hi Stefan,
a plugin or module is just another CMake target, as far as CMake is
concerned. You can call any CMake commands in your plugins
CMakeLists.txt file, like FIND_PACKAGE, FIND_LIBRARY, etc. and then link
to your plugin like
TARGET_LINK_LIBRARIES(${PLUGIN_TARGET} ${my_external_libs})
The variable PLUGIN_TARGET is set to the target name of your plugin
after you called MACRO_CRATE_MITK_PLUGIN or similar macros. The same
procedure is followed by our internal plugins/modules which depend on
external libraries, like APIs to tracking devices etc.
Best,
Sascha
On 05/13/2010 12:51 PM, Stefan Dänzer wrote:
sebastian,
thanks for the hint! is there any date scheduled when this goes into
the svn repository?
Anyways, a method to include custom libs in one's plugin or module
would be a "nice to have" feature for plugins which use additional
libraries than VTK, ITK, QT.
stefan
On Wed, May 12, 2010 at 2:42 PM, sebastian ordas
<[email protected] <mailto:[email protected]>> wrote:
Hi Stefan,
Do the following:
http://bugs.mitk.org/show_bug.cgi?id=3689
best regards,
sebastian
------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/mitk-users
--
--
Stefan Daenzer
Körnerplatz 8
04107 Leipzig
Tel.: +49-176-61157550
"Work like you don't need the money, love like you've never been hurt
and dance like no one is watching." - Randall G Leighton
------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
