Leadership:Slicer3-compilation-2008 - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T18:07:13Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Melonakos at 18:48, 6 November 2008

2008-11-06T18:48:50Z

Melonakos at 01:40, 6 November 2008

2008-11-06T01:40:35Z

Kikinis: /* How it will be when we are done */

2008-02-04T18:57:35Z

How it will be when we are done

Pieper: /* How we will get there */

2008-02-03T19:59:50Z

How we will get there

Pieper: /* How we will get there */

2008-02-03T19:53:46Z

How we will get there

Pieper: /* How we will get there */

2008-02-03T19:50:59Z

How we will get there

Pieper: /* How we will get there */

2008-02-03T19:47:50Z

How we will get there

Pieper: /* slicer3 */

2008-02-03T19:38:14Z

slicer3

Pieper: /* Current Situation */

2008-02-03T19:37:11Z

Current Situation

@@ Line 38: / Line 38: @@
 == slicer3 ==
-Slicer3 started a new KWWidgets application framework for which the modules are being reworked (see [http://www.slicer.org/slicerWiki/index.php/Slicer3:Loadable_Modules Slicer3:Loadable_Modules]).
+Slicer3 started a new KWWidgets application framework for which the modules are being reworked (see [https://www.slicer.org/wiki/Slicer3:Loadable_Modules Slicer3:Loadable_Modules]).
 The genlib and cmaker scripts were combined in slicer3 into a single script called getbuildtest.tcl.  getbuildtest also invokes ctest to run tests and submit to the dashboard, and also has options to build in release mode.
@@ Line 61: / Line 61: @@
 *** enable/disable features (e.g. python or libxml2)
-To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Loadable_Modules Slicer3:Loadable_Modules] and [http://www.slicer.org/slicerWiki/index.php/Slicer3:Build/Modules] projects.
+To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [https://www.slicer.org/wiki/Slicer3:Loadable_Modules Slicer3:Loadable_Modules] and [https://www.slicer.org/wiki/Slicer3:Build/Modules] projects.
 Terry is working on changes to slicer3 internals to support module loading.  Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).
 With this infrastructure in place Steve and Wendy will review the user requirements for a command line and GUI interface to simply the build and install process.  Dan Blezek has also begun prototyping what the GUI interface could look like.

@@ Line 38: / Line 38: @@
 == slicer3 ==
-Slicer3 started a new KWWidgets application framework for which the modules are being reworked (see [[Slicer3:Loadable_Modules]]).
+Slicer3 started a new KWWidgets application framework for which the modules are being reworked (see [http://www.slicer.org/slicerWiki/index.php/Slicer3:Loadable_Modules Slicer3:Loadable_Modules]).
 The genlib and cmaker scripts were combined in slicer3 into a single script called getbuildtest.tcl.  getbuildtest also invokes ctest to run tests and submit to the dashboard, and also has options to build in release mode.
@@ Line 61: / Line 61: @@
 *** enable/disable features (e.g. python or libxml2)
-To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [http://www.slicer.org/slicerWiki/index.php/Slicer3:Build/Modules] projects.
+To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Loadable_Modules Slicer3:Loadable_Modules] and [http://www.slicer.org/slicerWiki/index.php/Slicer3:Build/Modules] projects.
 Terry is working on changes to slicer3 internals to support module loading.  Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).
 With this infrastructure in place Steve and Wendy will review the user requirements for a command line and GUI interface to simply the build and install process.  Dan Blezek has also begun prototyping what the GUI interface could look like.

@@ Line 61: / Line 61: @@
 *** enable/disable features (e.g. python or libxml2)
-To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [[Slicer3:Build/Modules]] projects.
+To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [http://www.slicer.org/slicerWiki/index.php/Slicer3:Build/Modules] projects.
 Terry is working on changes to slicer3 internals to support module loading.  Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).
 With this infrastructure in place Steve and Wendy will review the user requirements for a command line and GUI interface to simply the build and install process.  Dan Blezek has also begun prototyping what the GUI interface could look like.

@@ Line 46: / Line 46: @@
 *.deb .rpm and ... for linux
 * ?? for mac
-* use directory tree in http://slicer.spl.harvard.edu/Downloads for webpresence (will eventually migrate to http://www.slicer.org/Downloads)?
+* use directory tree in http://www.slicer.org/Downloads for webpresence
 =How we will get there=

← Older revision		Revision as of 19:59, 3 February 2008
Line 64:		Line 64:

	Terry is working on changes to slicer3 internals to support module loading. Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).		Terry is working on changes to slicer3 internals to support module loading. Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).
		+
		+	With this infrastructure in place Steve and Wendy will review the user requirements for a command line and GUI interface to simply the build and install process. Dan Blezek has also begun prototyping what the GUI interface could look like.

← Older revision		Revision as of 19:53, 3 February 2008
Line 62:		Line 62:

	To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [[Slicer3:Build/Modules]] projects.		To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [[Slicer3:Build/Modules]] projects.
		+
		+	Terry is working on changes to slicer3 internals to support module loading. Sebastien is working inside CMake to support customized builds of slicer3 modules (in particular adding svn/cvs support to CMake).

@@ Line 56: / Line 56: @@
 ** We would like to move from a slicer-custom set of utilities to a standardized, cmake-based solution that would provide the advanced features for use by various projects.
 ** We want to work on new functionality rather than reimplementing existing solutions.  I.e. focus on developing the cmake-based build process for modules before rewriting getbuildtest.
 To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [[Slicer3:Build/Modules]] projects.

← Older revision		Revision as of 19:47, 3 February 2008
Line 49:		Line 49:

	=How we will get there=		=How we will get there=
		+
		+	Sebastien, Will, Steve, Katie, Stephen, and Brad met at the AHM to evaluate options. After much consideration we decided on some general goals and specific plans.
		+
		+	* Goals:
		+	** We would like a ''user centered'' installation process that simple and efficient (users in this case means the customers of NA-MIC who would like access to the NA-MIC kit as either a binary or as a source code platform for implementing their own solutions -- wherever possible the same interface should provide easy upgrade from binary to source installations).
		+	** We would like to move from a slicer-custom set of utilities to a standardized, cmake-based solution that would provide the advanced features for use by various projects.
		+	** We want to work on new functionality rather than reimplementing existing solutions. I.e. focus on developing the cmake-based build process for modules before rewriting getbuildtest.
		+
		+	To this end, we held a tcon on January 28, 2008 between Steve, Alex, Terry and Sebastien to coordinate the efforts of the [[Slicer3:Loadable_Modules]] and [[Slicer3:Build/Modules]] projects.

← Older revision		Revision as of 19:37, 3 February 2008
Line 19:		Line 19:

	=Current Situation=		=Current Situation=
		+
		+	All build systems in slicer have been based on cmake since it was introduced. CMake addresses compile options and project dependencies but does not address accessing source code repositories (cvs/svn).
		+
		+	== slicer2 ==
		+
		+	The following scripts were developed for slicer2:
		+
		+	* genlib.tcl generates all the libraries (tcl, tk, vtk, itk) including cvs/svn checkout, configure, and build.
		+	* cmaker.tcl updates, configures, runs cmake and invokes the copiler
		+	** the slicer base
		+	** on each of the modules
		+	* tarup.tcl which assembled all libaries and resource files into a distribution bundle.
		+
		+	Note that the '''module discovery process''' cmaker and tarup was identical to the one used by slicer2 at starup. This allowed a unified approach to module development and deployment.
		+
		+	Modules in slicer2 are based on the tcl package facilities which provided a clean layering of dependencies and modularity of both C++ and tcl code.
		+
		+	== slicer3 ==
		+
		+	Slicer3 started a new KWWidgets application framework for which the modules are being reworked (see [[Slicer3:LoadableModules]].
		+
		+	The genlib and cmaker scripts were combined in slicer3 into a single script called getbuildtest.tcl. getbuildtest also invokes ctest to run tests and submit to the dashboard, and also has options to build in release mode.

	=How it will be when we are done=		=How it will be when we are done=