Folks, <br><br>In most of the test associated with the ctkDICOM applications, I noticed that target_libraries.cmake is used. <br><br>Few remarks:<br><br>  - Using the macro ctkFunctionGetTargetLibraries in CMakeLists.txt associated with tests hasn't been tested -- But I guess nothing prevent would prevent from using it<br>

<br>  - Even if possible, using this macro and the associated <b>target_libraries.cmake</b> file won't be useful. Indeed, the initial idea behind <b>target_libraries.cmake</b> is to know the dependency of library from the Superbuild level. The system doesn't handle the dependency associated with tests. (It could be extended to do so ...)<br>

<br>   - Since the file is <b>target_libraries.cmake </b>parsed using a regular expression, conditional definition won't work within the file. <br><br>It means the following files should be fixed:<br>  - <a href="https://github.com/commontk/CTK/blob/master/Applications/ctkDICOM/Testing/Cpp/CMakeLists.txt">https://github.com/commontk/CTK/blob/master/Applications/ctkDICOM/Testing/Cpp/CMakeLists.txt</a><br>

  - <a href="https://github.com/commontk/CTK/blob/master/Applications/ctkDICOM/Testing/Cpp/target_libraries.cmake">https://github.com/commontk/CTK/blob/master/Applications/ctkDICOM/Testing/Cpp/target_libraries.cmake</a><br>

  - The same remarks applies for all tests associated with ctkDICOM applications<br><br>What shout be done:<br>  - If testing a command line application: Invoke that application<br>  - If designing some unit testing for some widget of that application: <br>

       - May be these widgets should belong to CTK libraries .. ?<br>       - If not, create a statit or shared librarie that both the application and the test could link against<br clear="all"><br>Any questions, let me know<br>

Thanks<br>Jc<br><br>-- <br>+1 919 869 8849<br><br>