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
