Difference between revisions of "Documentation/Labs/SlicerConfigAndUseSlicerTweaks"

From Slicer Wiki
Jump to: navigation, search
(Created page with ' == Overview == This page describes possible improvements to the SlicerConfig.cmake and UseSlicer.cmake files. These files are used when calling: <code> find_package(Slicer REQ…')
 
Line 4: Line 4:
 
This page describes possible improvements to the SlicerConfig.cmake and UseSlicer.cmake files. These files are used when calling:
 
This page describes possible improvements to the SlicerConfig.cmake and UseSlicer.cmake files. These files are used when calling:
  
<code>
+
<pre>
 
find_package(Slicer REQUIRED)
 
find_package(Slicer REQUIRED)
 
include(${Slicer_USE_FILE})
 
include(${Slicer_USE_FILE})
</code>
+
</pre>
  
 
The idea is to re-factor these files to avoid extension developers to implement clever work around and hacks for their use-cases, and facilitate overall maintenance.
 
The idea is to re-factor these files to avoid extension developers to implement clever work around and hacks for their use-cases, and facilitate overall maintenance.

Revision as of 23:11, 6 September 2015

Home < Documentation < Labs < SlicerConfigAndUseSlicerTweaks

Overview

This page describes possible improvements to the SlicerConfig.cmake and UseSlicer.cmake files. These files are used when calling:

find_package(Slicer REQUIRED)
include(${Slicer_USE_FILE})

The idea is to re-factor these files to avoid extension developers to implement clever work around and hacks for their use-cases, and facilitate overall maintenance.

Use-cases

SPHARM-PDM

Extension: https://github.com/NIRALUser/SPHARM-PDM/blob/master/SuperBuild.cmake

The goal is to re-use only the Slicer packaging macros without having the external projects built by Slicer included in the extension.

The Slicer extension projects are not needed by the extension because it builds a static version of these projects.