Hi,
usually, libraries are linked using their full path, so we shouldn't
need a *_LIBRARY_DIRS variable for linking (there are exceptions for
GDCM due to its build system).
The full path is known to external projects via the "exports file" of
MITK. I think that qtsingleapplication is missing from the export set
which results in it being linked using the library name directly.
@Matt Could you try and add "qtsingleapplication" to the
"targets_to_export" CMake variable in MITK/CMakeLists.txt:920 ?
@Miklos Yes, the MITK Workbench builds because "qtsingleapplication" is
a known target to the MITK build system. Your code looks good but you
should remove the "include_directories" statement in your "After"
version (mitk_use_modules takes care of that).
Thanks,
Sascha
On 03/10/2014 05:21 PM, Miklos Espak wrote:
Weird, because the MitkWorkbench builds well with the new
mitk_use_modules function.
I switched back to the deprecated MITK_USE_MODULE macro, now I get
some ugly CMake warnings, but the application builds and runs.
The change I made (and what I had to revert):
Before:
MITK_USE_MODULE(niftkCore)
MITK_USE_MODULE(qtsingleapplication)
include_directories(${ALL_INCLUDE_DIRECTORIES})
After:
mitk_use_modules(TARGET ${MY_APP_NAME} MODULES qtsingleapplication
niftkCore)
include_directories(${ALL_INCLUDE_DIRECTORIES})
And I put the new calls after the FunctionCreateBlueBerryApplication call.
Sascha, do you see any problem with this code?
Cheers,
Miklos
On 6 March 2014 16:34, Clarkson, Matt <[email protected]
<mailto:[email protected]>> wrote:
Hi All,
I am looking at mitkFunctionUseModules.cmake and I can’t see how a
specified module’s library directories are added to
ALL_LIBRARY_DIRS or similar.
Our app can’t link to qtsingleapplication because, the variable
qtsingleapplication_LIBRARY_DIRS is never added to a list of
directories.
Is that right?
Thanks
Matt
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move
to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually
works.
Faster operations. Version large binaries. Built-in WAN
optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
