Installation of SlicerExecutionModel

[fbudin69500]

When running the install step of SlicerExecutionModel, only one file is installed:
<CMAKE_INSTALL_PREFIX>/lib/ModuleDescriptionParser/libModuleDescriptionParser.a
It is therefore not possible to install SlicerExecutionModel and use it. It would be great to have a real install step that would install all the necessary files to be able to actually install SlicerExecutionModel.

[jcfr]

👍

Here are the steps:

• Add missing install rules and properly specify components
• Update SlicerExecutionModelConfig.cmake so that it can work from either the build or install tree
  • documentation: https://cmake.org/cmake/help/v3.5/manual/cmake-packages.7.html#creating-packages
  • example 1: https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/blob/7381d004886d6ed5f21c561fc8c1a9a2e376b7bb/CMakeLists.txt#L372-L417
  • example 2: https://github.com/commontk/DCMTK/blob/545de8711c76c9d51c1509b83e6714635a899a10/CMake/GenerateCMakeExports.cmake

[fedorov]

👍

@naucoin can you please work on resolving this issue, as part of the QIICR activities?

[jcfr]

@naucoin To help you in the process, I updated #44 (comment) with some references. Do not hesitate to ask if you have any questions.

[naucoin]

@fedorov @jcfr I'll look into it, can you assign the issue to me?

[fedorov]

By April 5 @naucoin will provide time estimate for completing this task

[naucoin]

@fedorov
Starting work on it today, should be done by early next week.

[jcfr]

👍

[naucoin]

@jcfr I'd found the documentation on making cmake packages before, but it jumps right into the complexities. Do you know of any examples that use a simpler set up, or a uses step by step approach as a how to rather than jumping right into a complex cmake file? I'm working my way through it but could use a better tutorial.

[fedorov]

Based on the discussion with Nicole today, this task turned out to be much more difficult than initially estimated. We need to address immediate deadlines on other projects, so I asked Nicole to lower the priority of this issue. Resolving this issue is not a stopper for us, since it is sufficient to package the build directory, or to just build the repository, since it is relatively small.