Difference between revisions of "Documentation/Nightly/Developers/Build system"
From Slicer Wiki
m |
|||
| Line 4: | Line 4: | ||
;[[Documentation/{{documentation/version}}/Developers/Versioning|Versioning]] | ;[[Documentation/{{documentation/version}}/Developers/Versioning|Versioning]] | ||
: Convention to name Slicer packages. | : Convention to name Slicer packages. | ||
| + | |||
| + | ;[[Documentation/{{documentation/version}}/Developers/ReleaseProcess|Release Process]] | ||
| + | : Step-by-step guide to create Slicer release | ||
;[[Documentation/{{documentation/version}}/Developers/Factory|Factory description]] | ;[[Documentation/{{documentation/version}}/Developers/Factory|Factory description]] | ||
Revision as of 22:46, 14 November 2014
Home < Documentation < Nightly < Developers < Build system
|
For the latest Slicer documentation, visit the read-the-docs. |
Leveraging the ExternalProject module provided by 
CMake, Slicer SuperBuild system allows developers to quickly install and configure the multiple open-source packages and libraries it depends on.
- Versioning
- Convention to name Slicer packages.
- Release Process
- Step-by-step guide to create Slicer release
- Factory description
- Current configuration of Slicer's factory machines.
- Build ExtensionsIndex
- How to build an ExtensionsIndex (collection of extension description files) ?
- Factory Dashboard setup
- Provide a general overview of the slicer application and extensions dashboard script organization
- Qt resource files
- Describes the
genqrc.pytool for automatic generation/updating of Qt resource scripts.
