Difference between revisions of "Developer Meetings/20130305"

From Slicer Wiki
Jump to: navigation, search
m (Text replacement - "slicerWiki/index.php" to "wiki")
 
(4 intermediate revisions by one other user not shown)
Line 7: Line 7:
 
* DIcom issue of Daniel - See http://slicer-devel.65872.n3.nabble.com/Problem-with-DICOM-module-tt4027815.html
 
* DIcom issue of Daniel - See http://slicer-devel.65872.n3.nabble.com/Problem-with-DICOM-module-tt4027815.html
 
* Python: https://github.com/jcfr/python-cmake-buildsystem
 
* Python: https://github.com/jcfr/python-cmake-buildsystem
<pre>
+
** See instruction: http://www.slicer.org/wiki/Documentation/Labs/CMake-ified_Python
# Download python source and CMake build system
 
## Windows/Unix: Open your unix terminal or windows git bash console, then run:
 
  
git clone git://github.com/jcfr/python-cmake-buildsystem -b next
+
== Conclusion ==
curl -O http://www.python.org/ftp/python/2.7.3/Python-2.7.3.tgz
+
* Alex talked about his recent work associated with MRML references. Before integrating, considering this is a MAJOR change involving the backbone of Slicer, we agreed that it would make sens to present the work on the mailing list to gather YOUR feedback and give you a chance to try things out.
tar -xzvf Python-2.7.3.tgz
+
** Email: http://slicer-devel.65872.n3.nabble.com/mrml-references-redesign-tt4027889.html
mkdir Python-2.7.3-build
 
cd Python-2.7.3-build
 
 
 
 
 
# Configure the project
 
## Windows:
 
  
Open cmake-gui
+
* Presented preliminary result associated with cmake'ified python. If you would like to try to build it, see updated build instruction: http://www.slicer.org/wiki/Documentation/Labs/CMake-ified_Python
Source dir : /path/to/python-cmake-buildsystem
 
Build dir  : /path/to/Python-2.7.3-build
 
Configure & Generate
 
Open /path/to/Python-2.7.3-build/Python27.sln
 
Build all
 
Run /path/to/Python-2.7.3-build/bin/python.exe
 
  
 +
* Discussed issue [http://na-mic.org/Mantis/view.php?id=2935 2935] - It would probably make sens to re-enable the corner annotation. That said we need to make it doesn't impact performance because of the font handling by VTK.
 +
** Jc: Check with VTK folks what is the status
  
## Unix (MacOSX, Linux)
+
* Discussed naming convention associated with Slicer packages
 
+
** download.slicer.org: Date associated with Nightly should not be displayed. Since the date associated with the build is the date of the associated commit, that would minimize confusion and always indicate the nightly is the latest available independently of the date. On the other hand the revision number should be maintained since it give an indication for the user aware of its meaning.
cd Python-2.7.3-build
+
*** We also talked about the name of the folder associated with MacOSX bundle. It is currently "Slicer.app", we should be changed to follow this scheme:
cmake ../python-cmake-buildsystem
+
**** Nightly: Slicer-rXXXX-YEAR-MONTH-DAY.app
make -j8
+
**** Release: Slicer-MAJOR-MINOR[-PATCH[-TWEAK]].app
./bin/python
 
 
 
 
 
 
 
Available build options:
 
 
 
BUILD_SHARED:  Build python static library
 
BUILD_STATIC:    Build python shared library
 
 
 
ENABLE_<EXTENSION>: If ON, the corresponding python extension will be built.
 
BUILTIN_<EXTENSION>:  If ON, the corresponding python extension will be built-in the built python librarie(s). No need to use Setup.local
 
 
 
 
 
To report problem, create an issue: https://github.com/jcfr/python-cmake-buildsystem/issues
 
</pre>
 
 
 
== Conclusion ==
 

Latest revision as of 17:05, 21 November 2019

Home < Developer Meetings < 20130305

To discuss

Conclusion

  • Discussed issue 2935 - It would probably make sens to re-enable the corner annotation. That said we need to make it doesn't impact performance because of the font handling by VTK.
    • Jc: Check with VTK folks what is the status
  • Discussed naming convention associated with Slicer packages
    • download.slicer.org: Date associated with Nightly should not be displayed. Since the date associated with the build is the date of the associated commit, that would minimize confusion and always indicate the nightly is the latest available independently of the date. On the other hand the revision number should be maintained since it give an indication for the user aware of its meaning.
      • We also talked about the name of the folder associated with MacOSX bundle. It is currently "Slicer.app", we should be changed to follow this scheme:
        • Nightly: Slicer-rXXXX-YEAR-MONTH-DAY.app
        • Release: Slicer-MAJOR-MINOR[-PATCH[-TWEAK]].app