|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | == Background ==
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:getbuildtest here]</font></big> |
| − | | |
| − | The getbuildtest script was created to simplify the process of setting up a build on a new system. It ''get''s the needed code from repositories, ''build''s the code with a compatible set of configuration options, and ''test''s the resulting binaries and submits them to the dashboard as an experimental build.
| |
| − | | |
| − | == getbuildtest.tcl == | |
| − | | |
| − | Three files are used as part of this process:
| |
| − | * slicer_variables.tcl contains global settings for the build process including what versions of support libraries to checkout.
| |
| − | * Scripts/genlib.tcl builds all the support libraries (puts them in Slicer3-lib)
| |
| − | * Scripts/getbuildtest.tcl calls genlib and once it completes successfully it builds slicer3 in Slicer3-build
| |
| − | | |
| − | | |
| − | == getbuildtest2.tcl ==
| |
| − | | |
| − | The getbuildtest2 script an experimental version that should/will someday replace getbuildtest.
| |
| − | | |
| − | The main differences are:
| |
| − | * libraries are pulled from [[Slicer3-lib-mirror]]
| |
| − | * extra libraries like python and BatchMake are being added
| |
| − | | |
| − | As of September 2007, python is not building correctly with all the desired libraries so work on getbuildtest2 is still ongoing.
| |
| − | | |
| − | Most developers should be using getbuiltest for now.
| |
Latest revision as of 17:20, 10 July 2017
Home < Slicer3:getbuildtestNote: We are migrating this content to the slicer.org domain - The newer page is here
