Hi Matt,

In recent CMake versions there are a couple of helpful macros for this 
kind of thing and there are also a few tutorials / guidelines out there. 
I would say it depends a lot on the minimum CMake version you are 
requiring for your project. MITK still has a lot of hand-crafted CMake 
code (not only for the MITKConfig.cmake file) which would be nice to 
update. Especially the absolute / relative path issue can be handled 
better by using a certain CMake macro (can't remember the name right 
now). See

http://www.cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-packages

The CTK stuff was done in one of the last hackfests and the install 
rules are propagated due to the usage of the ctkMacroCreatePlugin macro. 
But this was a side-effect which is usually not what is wanted. Note 
that the MITK "make package" support creates an installer and not a SDK. 
A MITK install tree cannot (yet) be used for development of external 
projects.

Best,
Sascha

On 10/13/2014 01:03 PM, Clarkson, Matt wrote:
> Hi there,
>
> I notice that MITK has an MITKConfig.cmake.in which gets populated at 
> configure time, into the build folder.
> This means 3rd party builds can access MITK, and get hold of all paths and 
> includes for compiling against MITK.
>
> However, the same would be useful for a 3rd party project. e.g. NifTK.
> So, we require to generate an NifTKConfig.cmake.in
>
> Can people advise us on where to start and what to do. Are there any useful 
> macros?
> I notice that if I do a make package … the CTK plugins are already exported 
> into the package structure into a lib/include folder. How did that happen?
> How do we make sure that all the MITK macros are available to uses of NifTK?
>
> I also notice that the paths in the MITKConfig.cmake are absolute.
> Is there anyway to make this work with relative paths, so that the whole 
> directory structure could be moved about.
>
> Has anyone tried something similar?
>
> Thanks
>
> Matt
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to