Difference between revisions of "Documentation/Labs/NUMPY171"
From Slicer Wiki
m (→Issues) |
m (→Issues) |
||
| Line 6: | Line 6: | ||
= Issues = | = Issues = | ||
| − | * http://www.na-mic.org/Bug/view.php?id=3158 | + | * [http://www.na-mic.org/Bug/view.php?id=3158 #3158] - Building Slicer with numpy-1.4.1 failed using VS2010 |
| − | * http://www.na-mic.org/Bug/view.php?id=3159 | + | * [http://www.na-mic.org/Bug/view.php?id=3159 #3159] - Update Slicer build system to use numpy 1.7.1 |
| − | * http://www.na-mic.org/Bug/view.php?id=3160 | + | * [http://www.na-mic.org/Bug/view.php?id=3160 #3160] - Make sure numpy 1.7.1 can be build on Unix and MacOSx without requiring Fortran compiler |
= Possible approaches = | = Possible approaches = | ||
Revision as of 17:47, 19 June 2013
Home < Documentation < Labs < NUMPY171Contents
Goal
- Slicer is currently building Numpy 1.4.1. We would like to upgrade to a more recent version of Numpy to bring the latest and greatest of Numpy to Slicer community.
Issues
- #3158 - Building Slicer with numpy-1.4.1 failed using VS2010
- #3159 - Update Slicer build system to use numpy 1.7.1
- #3160 - Make sure numpy 1.7.1 can be build on Unix and MacOSx without requiring Fortran compiler
Possible approaches
- Keep the current version and back-port to vs2010/12 support.
- Use different version for windows (1.7.1) and unix-like (1.4.1) system.
- Ideally, use 1.7.1 on all platform/compiler.
