Difference between revisions of "Slicer3:getbuildtest"
From Slicer Wiki
| (One intermediate revision by the same user not shown) | |||
| Line 22: | Line 22: | ||
As of September 2007, python is not building correctly with all the desired libraries so work on getbuildtest2 is still ongoing. | 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 | + | Most developers should be using getbuildtest for now. |
Latest revision as of 20:13, 20 May 2008
Home < Slicer3:getbuildtestBackground
The getbuildtest script was created to simplify the process of setting up a build on a new system. It gets the needed code from repositories, builds the code with a compatible set of configuration options, and tests 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
MAC OS X 10.5 issues Slicer3:getbuildtest:macosx10.5
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 getbuildtest for now.
