SlicerExecutionModel
SlicerExecutionModel copied to clipboard
An open-source CMake-based project that provides macros and associated tools for the easy building of 3D Slicer command line interface (CLI) modules.
Only one file is installed: ```lib/ModuleDescriptionParser/libModuleDescriptionParser.so``` Is this what's intended? The description says: ``` project that provides macros and associated tools```.
When compiling a target that has specific C++ requirements, one can use the new CMake function [target_compile_features()](https://cmake.org/cmake/help/v3.6/command/target_compile_features.html) [1]. There is currently no way of passing these requirements to `SEMMacroBuildCLI`, and...
Comment associated with these issues could be integrated in the documentation: - https://github.com/Slicer/SlicerExecutionModel/issues/7#issuecomment-231274525 - https://github.com/Slicer/SlicerExecutionModel/issues/26#issuecomment-231275396
See http://www.na-mic.org/Bug/view.php?id=4225 Cc: @vovythevov
Discussion: http://slicer-devel.65872.n3.nabble.com/Temporary-directory-for-CLI-modules-td4035464.html Reason to reject initial patch from @ prastawa : Patch Slicer/Slicer#400 will be problematic when the CLI is executed directly without Slicer. Proposal: - CLI should always expect...
In order for CLI to report progress, the following output is the standard: ``` ... ... ... ``` There is in Slicer (Base/CLI) some utility classes that observe ITK and...
See: http://na-mic.org/Mantis/view.php?id=2781
Sometimes it is useful to pass CMake variables into C++ code. The way to do it is to use the CMake configure_file() macro. It takes a *.h.in as input and...