ITK/Policy and Procedures for Adding Remote Modules: Difference between revisions
From KitwarePublic
< ITK
Jump to navigationJump to search
(Created page with "Remote modules are downloaded at CMake configuration time into the ''Remote'' module group, i.e. into the ''Modules/Remote'' directory of the repository tree. A Remote Module ca...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Remote modules are downloaded at CMake configuration time into the ''Remote'' module group, i.e. into the ''Modules/Remote'' directory of the repository tree. A Remote Module can be enabled by setting the ''Fetch_<module name>'' CMake configuration variable to ''ON''. | Remote modules are downloaded at CMake configuration time into the ''Remote'' module group, i.e. into the ''Modules/Remote'' directory of the repository tree. A Remote Module can be enabled by setting the target ''Fetch_<module name>'' CMake configuration variable to ''ON''. | ||
== Purpose of Remote Modules == | == Purpose of Remote Modules == | ||
Revision as of 03:59, 24 April 2012
Remote modules are downloaded at CMake configuration time into the Remote module group, i.e. into the Modules/Remote directory of the repository tree. A Remote Module can be enabled by setting the target Fetch_<module name> CMake configuration variable to ON.
