Changesets: Slicer
2145-support-for-installing-extension-from-file 87b969bc 2013-05-27 15:31:57 Details Diff |
ENH: moved label to tool tip git-svn-id: http://svn.slicer.org/Slicer4/trunk@22042 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/Loadable/TractographyDisplay/Widgets/Resources/UI/qSlicerTractographyEditorROIWidget.ui | Diff File | ||
mod - Modules/Loadable/TractographyDisplay/Widgets/qSlicerTractographyEditorROIWidget.cxx | Diff File | ||
2145-support-for-installing-extension-from-file cf891c06 2013-05-27 14:05:48 Details Diff |
COMP: Reduce number of copy/compile python targets Set variable CTK_COMPILE_PYTHON_SCRIPTS_GLOBAL_TARGET_NAME to "Slicer" to create targets: CopySlicerPythonResourceFiles CopySlicerPythonScriptFiles CompileSlicerPythonFiles Before this commit, for each set of script processed directly or indirectly by the macro "ctkMacroCompilePythonScript", two targets are created. For example: [...] CopyAAAPythonFiles CopyAAAPythonResourceFiles CompileAAAPythonFiles [...] CopyBBBPythonFiles CopyBBBPythonResourceFiles CompileBBBPythonFiles [...] CopyCCCPythonFiles CompileCCCPythonFiles [...] After integrating the commit, independently of the number of set of scripts, within Slicer core the following three targets will be available: CopySlicerPythonResourceFiles [If there are python resources] CopySlicerPythonScriptFiles CompileSlicerPythonFiles Note that this will apply only for Slicer core, by default, if an extension bundles 2 scripted modules, the following targets will be available: CopyModule1PythonScriptFiles CompileModule1PythonFiles CopyModule2PythonResourceFiles CopyModule2PythonScriptFiles CompileModule2PythonFiles git-svn-id: http://svn.slicer.org/Slicer4/trunk@22041 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMakeLists.txt | Diff File | ||
2145-support-for-installing-extension-from-file 3c1e22de 2013-05-25 12:52:54 Details Diff |
BUG: 3054. Added dimensions check in ImageLabelCombine module git-svn-id: http://svn.slicer.org/Slicer4/trunk@22040 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/CLI/ImageLabelCombine/ImageLabelCombine.cxx | Diff File | ||
2145-support-for-installing-extension-from-file 6ddeada5 2013-05-25 08:15:15 Details Diff |
ENH: Added help text for the edit fibers checkbox git-svn-id: http://svn.slicer.org/Slicer4/trunk@22039 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/Loadable/TractographyDisplay/Widgets/Resources/UI/qSlicerTractographyEditorROIWidget.ui | Diff File | ||
2145-support-for-installing-extension-from-file cd985077 2013-05-25 02:23:55 Details Diff |
COMP: Allow use of 'project()' in CMakeLists.txt of extension/module The previous approach enforcing to NOT use "project()" in CMakeLists.txt is not required anymore. This was done so that SlicerConfig.cmake included after calling "find_package(Slicer)" could: (1) include SlicerBlockSetCMakeOSXVariables (2) then call the project() statement Using recent version of CMake, this "hack" was preventing extension from being built. To prevent the configure error, "SlicerBlockSetCMakeOSXVariables" is not included anymore automatically after calling "find_package(Slicer)" That said, to allow the CMAKE_OSX_* to (optionally) be set automatically, a different approach is now considered. This also make it possible to call "project()" within the CMakeLists.txt of extension or module. To optionally have the CMAKE_OSX_* variable set within a project, the developer could call: find_package(Slicer COMPONENTS ConfigurePrerequisites) before any "project()" calls. For completeness, the discussion with CMake developer regarding the possible approach to automatically set the CMAKE_OSX_* variables have been reported below. // ------------------ From Jc: Hi Brad, To summarize, the user build a building using a line similar to: cmake -DSlicer_DIR:PATH=/path/to/Slicer-build -DCMAKE_BUILD_TYPE:STRING=Release ../MyPlugin Passing Slicer_DIR is the only requirement. // ------------------ You are right the file in source/build tree won't help. // ------------------ Currently, the value for CMAKE_OSX_* are set in SlicerConfig.cmake and I would like the plugin to use these. The current approach is to force the following convention: set(EXTENSION_NAME "Foo") find_package(Slicer) include(${Slicer_USE_FILE}) [...] where project() was called within the Slicer use file. // ------------------ By using this new approach: find_package(Slicer COMPONENTS ConfigurationPrerequisites) project(Foo) find_package(A ..) find_package(B ..) Can I be sure that the first call to "find_package" will be done before language feature are enabled ? Thanks Jc // -------------------------- From Brad: On 04/19/2013 10:54 AM, Jean-Christophe Fillion-Robin wrote: > cmake -DSlicer_DIR:PATH=/path/to/Slicer-build -DCMAKE_BUILD_TYPE:STRING=Release ../MyPlugin Great, so find_package doesn't actually need to search but only load the package config file. > Currently, the value for CMAKE_OSX_* are set in SlicerConfig.cmake > and I would like the plugin to use these. The current approach is > to force the following convention: > > set(EXTENSION_NAME "Foo") > find_package(Slicer) > include(${Slicer_USE_FILE}) > > where project() was called within the Slicer use file. Instead of the above three lines, try these three:: project(Foo NONE) find_package(Slicer) SlicerConfigPlugin() SlicerConfig.cmake provides the SlicerConfigPlugin macro to: * FATAL_ERROR if languages are already enabled and tell the plugin author to add NONE to the project command * Get the extension name from PROJECT_NAME, or alternatively from an optional explicit argument * Set OS X platform variables and call enable_language() Larger projects that provide a Slicer plugin along with a bunch of other unrelated stuff will not want Slicer to control their enable_language calls. Therefore SlicerConfig should add another macro (or options to this one) to just check that an already enabled language has a matching platform selection and skip its enable_language calls. > find_package(Slicer COMPONENTS ConfigurationPrerequisites) > project(Foo) > find_package(A ..) > find_package(B ..) > > Can I be sure that the first call to "find_package" will be > done before language feature are enabled ? Yes, but the above method may be even simpler. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22038 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerConfig.cmake.in | Diff File | ||
mod - CMake/UseSlicer.cmake.in | Diff File | ||
mod - Extensions/CMake/SlicerBlockBuildPackageAndUploadExtension.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 940b1f85 2013-05-24 16:37:58 Details Diff |
COMP: ExtractSkeleton - Fix clang -Wparentheses-equality warning Detailed output from Clang: warning: equality comparison with extraneous parentheses [-Wparentheses-equality] if( (result[i] == OBJ) ) ~~~~~~~~~~^~~~~~ note: remove extraneous parentheses around the comparison to silence this warning git-svn-id: http://svn.slicer.org/Slicer4/trunk@22037 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/CLI/ExtractSkeleton/tilg_iso_3D.cxx | Diff File | ||
2145-support-for-installing-extension-from-file 61c97630 2013-05-24 16:15:52 Details Diff |
COMP: Fix Xcode build error related to vtkpng library This commit ensure that "CMAKE_CFG_INTDIR" is considered on all multi-configuration environment and not only windows. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22036 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_teem.cmake | Diff File | ||
2145-support-for-installing-extension-from-file e1f8ffd8 2013-05-24 11:32:03 Details Diff |
ENH: Added selection, de-selection, deleting-of-selected fibers. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22035 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/Loadable/TractographyDisplay/MRMLDM/vtkMRMLTractographyDisplayDisplayableManager.cxx | Diff File | ||
mod - Modules/Loadable/TractographyDisplay/MRMLDM/vtkMRMLTractographyDisplayDisplayableManager.h | Diff File | ||
2145-support-for-installing-extension-from-file 9ed155b2 2013-05-23 18:40:07 Details Diff |
COMP: Fix configure error occurring when using XCode generator Note that this fix only allow an "Archive" build to be successfully done using Xcode. This could be done through the menu "Product" -> "Build For" -> "Archiving" Commit r21879 ensured python was systematically build in Release on multi-configuration generator. Since additional external project steps specific on unix and apple system were not considered by the previous fix, it was causing configure error like the one reported below: ../ExternalProject.cmake:1049 (add_custom_command): add_custom_command given APPEND option with output "/Volumes/Dashboards/Experimental/Slicer-Superbuild-Release-cmake-2.8.11-XCode/CMakeFiles/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/python-complete" which is not already a custom command output. [...] This commit ensure that the additional steps consider the value of "CMAKE_CFG_INTDIR" forced to Release. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22034 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_python.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 98db4355 2013-05-23 17:42:09 Details Diff |
COMP: Fix unused variable warnings related to qRestAPI project See commontk/qRestAPI@5a81c92f9 git-svn-id: http://svn.slicer.org/Slicer4/trunk@22033 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_qRestAPI.cmake | Diff File | ||
2145-support-for-installing-extension-from-file eb9b0263 2013-05-23 16:56:18 Details Diff |
COMP: Fix clang build error related to qRestAPI Associated qRestAPI commit is commontk/qRestAPI@082dabd and the corresponding message as been copied below: // ------------- Fix build CLang build error by making static helper method public. For the record, the reason this fails on Mac and not on Linux is the following : http://clang-developers.42468.n3.nabble.com/Access-to-static-protected-member-from-friends-of-derived-classes-td4030444.html The Q_DECLARE_PRIVATE macro declares the qXnatAPIPrivate class and makes it a friend of qXnatAPI, which is sufficient for G++ to give it access to qRestAPI's static protected methods, but the Clang developers have a different understanding of the standard, so it doesn't work on Clang. Thanks to Steve Pieper, Florian Vichot and Sascha Zelzer for their help fixing the issue. // ------------- git-svn-id: http://svn.slicer.org/Slicer4/trunk@22032 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_qRestAPI.cmake | Diff File | ||
2145-support-for-installing-extension-from-file e7b28138 2013-05-22 20:35:34 Details Diff |
COMP: Fix linux build of qRestAPI Ironically, while commit r22030 fixed windows static build it also broke linux build. This commit fixes the problem. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22031 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_qRestAPI.cmake | Diff File | ||
2145-support-for-installing-extension-from-file aab26dae 2013-05-22 19:39:43 Details Diff |
COMP: Fix inconsistent linkage error related to qRestAPI Associated qRestAPI commit is commontk/qRestAPI@6339e0c and the corresponding message as been copied below: // ------------- Support windows static build Following commit commontk/qRestAPI@5c056f2, the project could be built as a shared library this caused problem on windows where the qRestAPI_EXPORT macro was also defined in the case of static build causing an "inconsistent linkage" error. This commit explicitly define qRestAPI_EXPORT based on the BUILD_SHARED_LIBS option. // ------------- git-svn-id: http://svn.slicer.org/Slicer4/trunk@22030 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_qRestAPI.cmake | Diff File | ||
2145-support-for-installing-extension-from-file dce4ae04 2013-05-22 18:02:30 Details Diff |
COMP: Use qRestAPI instead of deprecated qMidasAPI project In addition to provide Midas support, qRestAPI also provides support for XNat (qXnatAPI.h) See https://github.com/commontk/qRestAPI git-svn-id: http://svn.slicer.org/Slicer4/trunk@22029 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Base/QTCore/CMakeLists.txt | Diff File | ||
mod - Base/QTCore/qSlicerExtensionsManagerModel.cxx | Diff File | ||
mod - CMake/SlicerConfig.cmake.in | Diff File | ||
mod - CMake/SlicerGenerateSlicerConfig.cmake | Diff File | ||
mod - CMakeLists.txt | Diff File | ||
mod - SuperBuild.cmake | Diff File | ||
rm - SuperBuild/External_qCDashAPI.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 76081669 2013-05-22 08:53:06 christopher.mullins Details Diff |
BUG: Fixes duplicate class name so that correct constructor is called git-svn-id: http://svn.slicer.org/Slicer4/trunk@22028 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Extensions/Testing/EditorExtensionTemplate/EditorEffectTemplate/EditorEffectTemplate.py | Diff File | ||
2145-support-for-installing-extension-from-file 1c07f30b 2013-05-20 18:53:42 Details Diff |
STYLE: Reference private member using "this->" git-svn-id: http://svn.slicer.org/Slicer4/trunk@22027 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/Loadable/ViewControllers/qSlicerViewControllersModuleWidget.cxx | Diff File | ||
2145-support-for-installing-extension-from-file f3b155fd 2013-05-19 22:16:03 Details Diff |
COMP: Simplify external project removing CMake 2.8.8 compatibility git-svn-id: http://svn.slicer.org/Slicer4/trunk@22026 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild.cmake | Diff File | ||
mod - SuperBuild/External_BRAINSTools.cmake | Diff File | ||
mod - SuperBuild/External_BatchMake.cmake | Diff File | ||
mod - SuperBuild/External_CTK.cmake | Diff File | ||
mod - SuperBuild/External_CTKAPPLAUNCHER.cmake | Diff File | ||
mod - SuperBuild/External_DCMTK.cmake | Diff File | ||
mod - SuperBuild/External_EMSegment.cmake | Diff File | ||
mod - SuperBuild/External_ITKv3.cmake | Diff File | ||
mod - SuperBuild/External_ITKv4.cmake | Diff File | ||
mod - SuperBuild/External_LibArchive.cmake | Diff File | ||
mod - SuperBuild/External_MultiVolumeExplorer.cmake | Diff File | ||
mod - SuperBuild/External_MultiVolumeImporter.cmake | Diff File | ||
mod - SuperBuild/External_NUMPY.cmake | Diff File | ||
mod - SuperBuild/External_OpenIGTLink.cmake | Diff File | ||
mod - SuperBuild/External_OpenIGTLinkIF.cmake | Diff File | ||
mod - SuperBuild/External_PCRE.cmake | Diff File | ||
mod - SuperBuild/External_SciPy.cmake | Diff File | ||
mod - SuperBuild/External_SimpleITK.cmake | Diff File | ||
mod - SuperBuild/External_SlicerExecutionModel.cmake | Diff File | ||
mod - SuperBuild/External_VTK.cmake | Diff File | ||
mod - SuperBuild/External_cmcurl.cmake | Diff File | ||
mod - SuperBuild/External_incrTcl.cmake | Diff File | ||
mod - SuperBuild/External_jqPlot.cmake | Diff File | ||
mod - SuperBuild/External_python.cmake | Diff File | ||
mod - SuperBuild/External_qCDashAPI.cmake | Diff File | ||
mod - SuperBuild/External_qMidasAPI.cmake | Diff File | ||
mod - SuperBuild/External_tcl.cmake | Diff File | ||
mod - SuperBuild/External_teem.cmake | Diff File | ||
mod - SuperBuild/External_tk.cmake | Diff File | ||
mod - SuperBuild/External_zlib.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 6f9be787 2013-05-19 21:44:08 Details Diff |
COMP: Ensure out-of-source CLI module use Slicer library wrapper Commit r19677 removed the setting of Slicer_CLI_SHARED_LIBRARY_WRAPPER_CXX from SlicerConfig by ensuring the use of the wrapper provided by SlicerExecutionModel. Then, commit r21592 added the ITKFactoryRegistration library and also re-introduced a custom cli wrapper without making sure module externally built would consider it. This commit set "SlicerExecutionModel_CLI_LIBRARY_WRAPPER_CXX" in SlicerConfig.cmake to allow module externally built to consider the Slicer wrapper. It also address the issue discussed in the following Slicer thread: http://massmail.spl.harvard.edu/public-archives/slicer-devel/2013/012491.html git-svn-id: http://svn.slicer.org/Slicer4/trunk@22025 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerConfig.cmake.in | Diff File | ||
mod - CMake/SlicerGenerateSlicerConfig.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 5f0916e9 2013-05-18 08:15:34 Details Diff |
BUG: Remove check of spacing in LabelStatistics Because small differences in spacing can be introduced by rounding or the way floating point numbers are handled, the check of exact equality caused false negatives. Removing this check will allow valid use cases to succeed, while the other checks still prevent incorrect calculations (where the grids to not actually align in pixel space). git-svn-id: http://svn.slicer.org/Slicer4/trunk@22024 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Modules/Scripted/LabelStatistics/LabelStatistics.py | Diff File | ||
2145-support-for-installing-extension-from-file 178bd4e1 2013-05-17 18:05:19 Details Diff |
BUG: Ensure library can be loaded from different place using @rpath Before this commit, attempt have been made (r18311, r18325, r18581) to install both built-in CLI and extension CLI executable in a folder located at some depth of the main Slicer executable. This was needed because all libraries were referenced based on the location of the main Slicer executable using "@executable_path". This was working *only* in the case of built-in CLI but wasn't scaling very well for the extension CLI executable. Indeed, being able to both differentiate the different installed extension and keeping the depth to 1 level wasn't easily feasible: /path/to/Slicer.app/Contents/MacOS/Slicer /path/to/Slicer.app/Contents/cli-modules/MyCLI /path/to/Slicer.app/Contents/Extensions-21855/SkullStripper/cli-modules/MyCLI A solution could have been to install extensions directly in "Slicer.app" folder and update the cli install sub dir to get something like: /path/to/Slicer.app/Extensions-21855/SkullStripper/MyCLI While possible, it would have remain a special case to maintain. Instead, by using "@rpath", CLI modules can now be installed in the Slicer standard location "Slicer_CLIMODULES_LIB_DIR" instead of "Slicer_CLIMODULES_SUBDIR". This commit remove the special case which never worked (issue 0003051) Waiting the topic "tweak-bundleutilities-for-rpath" is fully matured and integrated in CMake, use custom version of BundleUtilities and GetPrerequisites. See http://cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/tweak-bundleutilities-for-rpath Since our custom version of the CMake modules now consider "~/usr/.*/lib", the implementation of "gp_resolved_file_type_override" has been removed. Remove the hack specific to LibArchive (introduced by commit r19615), since the library is fixed up using the default library matching pattern, it will be installed in the expected location. SlicerExecutionModel has also been updated to link the CLI executable and library with "-rpath" so that they can resolve the location of Slicer libraries. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22023 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Applications/SlicerApp/CMakeLists.txt | Diff File | ||
mod - Base/CLI/CMakeLists.txt | Diff File | ||
mod - Base/QTCLI/qSlicerCLIExecutableModuleFactory.cxx | Diff File | ||
mod - Base/QTCLI/qSlicerCLIModuleFactoryHelper.cxx | Diff File | ||
add - CMake/BundleUtilitiesWithRPath.cmake | Diff File | ||
add - CMake/GetPrerequisitesWithRPath.cmake | Diff File | ||
mod - CMake/SlicerCPack.cmake | Diff File | ||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File | ||
mod - CMake/SlicerExtensionCPack.cmake | Diff File | ||
mod - CMake/SlicerExtensionCPackBundleFixup.cmake.in | Diff File | ||
mod - CMake/UseSlicer.cmake.in | Diff File | ||
mod - CMakeLists.txt | Diff File | ||
mod - SuperBuild/External_SlicerExecutionModel.cmake | Diff File | ||
2145-support-for-installing-extension-from-file 3df88ffe 2013-05-17 18:05:16 Details Diff |
STYLE: Easier configuration of fixup path in bundle script git-svn-id: http://svn.slicer.org/Slicer4/trunk@22022 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerCPack.cmake | Diff File | ||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File | ||
mod - CMake/SlicerExtensionCPack.cmake | Diff File | ||
mod - CMake/SlicerExtensionCPackBundleFixup.cmake.in | Diff File | ||
2145-support-for-installing-extension-from-file b6c80e97 2013-05-17 18:05:14 Details Diff |
COMP: Simplify expression used in gp_item_default_embedded_path_override. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22021 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File | ||
mod - CMake/SlicerExtensionCPackBundleFixup.cmake.in | Diff File | ||
2145-support-for-installing-extension-from-file d38232de 2013-05-17 18:05:12 Details Diff |
COMP: Do not explicitly fixup CLI shared libraries Considering that (1) CLI shared lirbary are dependency of CLI executable and (2) CLI executable are already discovered by the fixup mechanism. There are no need to use candidate pattern for CLI shared library. git-svn-id: http://svn.slicer.org/Slicer4/trunk@22020 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File | ||
mod - CMake/SlicerExtensionCPackBundleFixup.cmake.in | Diff File | ||
2145-support-for-installing-extension-from-file 18ddefef 2013-05-17 18:05:11 Details Diff |
COMP: Ensure library paths used for BundleFixup are valid The helper macro "_fixup_paths_append" is now used consistently to append path to the "libs_path" variable. Let's also note the following updates: - CMAKE_RUNTIME_OUTPUT_DIRECTORY is not used anymore, instead ${Slicer_BUILD_DIR}/@Slicer_BIN_DIR@ is used. - Path "@Slicer_BINARY_DIR@/@Slicer_QtPlugins_DIR@" is not considered anymore since it didn't exist in the build tree. Instead, the plugin path are composed using "${Slicer_BUILD_DIR}/@Slicer_BIN_DIR@" git-svn-id: http://svn.slicer.org/Slicer4/trunk@22019 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File | ||
2145-support-for-installing-extension-from-file 84c12c88 2013-05-17 18:05:09 Details Diff |
COMP: Ensure Python library directory is considered when fixing up package When the expression "@SLICER_PYTHON_LIB_DIR@" has been introduced in commit r21252 [1], it was already resolving to an empty string because since r15463 [2] the file SlicerBlockCTKAppLauncherSettings is included in the Applications/SlicerApp/CMakeLists.txt. Both the fixup script and the launcher settings have been updated to use the variable "PYTHON_LIBRARY_PATH" introduced in the top-level CMakeLists.txt by commit r16822 [3] To prevent such error from happening again, a convenient macro named "_fixup_paths_append" has been introduced. It basically check if the path passed as parameter exists and append it to the list of paths. If not, it throw an error. [1] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21252 [2] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=15463 [3] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=16822 git-svn-id: http://svn.slicer.org/Slicer4/trunk@22018 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - CMake/SlicerBlockCTKAppLauncherSettings.cmake | Diff File | ||
mod - CMake/SlicerCPackBundleFixup.cmake.in | Diff File |