Difference between revisions of "2012 Summer Project Week:ITKv4 Integration"
From NAMIC Wiki
Hjmjohnson (talk | contribs) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
<gallery> | <gallery> | ||
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]] | Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]] | ||
| + | Image:ITKv4Integration-screenshot.png| Screenshot | ||
</gallery> | </gallery> | ||
| Line 9: | Line 10: | ||
* SPL: Steve Pieper | * SPL: Steve Pieper | ||
* Kitware: JC, Julien | * Kitware: JC, Julien | ||
| + | * NLM (C): Bradley Lowekamp | ||
| + | * NoWare: Bill Lorensen | ||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
| Line 14: | Line 17: | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
| − | Move Slicer from ITKv3 to ITKv4 | + | # Move Slicer build from ITKv3 to ITKv4 |
| + | ## Complete build from scratch with packaging | ||
| + | ## Build against ITKv4 | ||
| + | ## Build with SimpleITK | ||
| + | # Pass Rule 1 and Rule 2 of "Rons Rules for tools" | ||
| + | ## You make it, I break it. [1] | ||
| + | ## Your tool does not exist, until it works on my laptop with my data. [2] | ||
| + | |||
</div> | </div> | ||
| Line 21: | Line 31: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
Figure out how to get packaging working when building with ITKv4 | Figure out how to get packaging working when building with ITKv4 | ||
| + | * Basic building is working (Has been for a long time). | ||
| + | * Compiler propagation to submodules needed | ||
| + | |||
</div> | </div> | ||
| Line 26: | Line 39: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | + | * | |
| + | During Project Week we resolved the packaging issues. | ||
| + | # ITKv4 now supports runtime only installs. (Thanks Bill Lorensen) | ||
| + | ## This required changes to both Slicer and ITKv4 (for complete compliance). | ||
| + | ### The Slicer changes are checked into the repo. | ||
| + | ### The ITKv4 changes are tested and merged into master branch of ITKv4 | ||
| + | ### BRAINSTools was cleaned up to support the COMPONENT Runtime Install | ||
| + | |||
| + | # Clean build process | ||
| + | ## Remove configuration warnings about unnecessary/unused configuration commands | ||
| + | ## Fix shared library linking for python on Mac for creating successful install | ||
| + | ## Complete build success tested to respect superbuild requested compiler (set default CC=/dev/null and CXX=/dev/null to force errors) | ||
| + | ## | ||
</div> | </div> | ||
</div> | </div> | ||
Latest revision as of 13:49, 22 June 2012
Home < 2012 Summer Project Week:ITKv4 Integration
Screenshot
Key Investigators
- Iowa: Hans Johnson, Kent Williams
- GE: Jim Miller
- SPL: Steve Pieper
- Kitware: JC, Julien
- NLM (C): Bradley Lowekamp
- NoWare: Bill Lorensen
Objective
- Move Slicer build from ITKv3 to ITKv4
- Complete build from scratch with packaging
- Build against ITKv4
- Build with SimpleITK
- Pass Rule 1 and Rule 2 of "Rons Rules for tools"
- You make it, I break it. [1]
- Your tool does not exist, until it works on my laptop with my data. [2]
Approach, Plan
Figure out how to get packaging working when building with ITKv4
- Basic building is working (Has been for a long time).
- Compiler propagation to submodules needed
Progress
During Project Week we resolved the packaging issues.
- ITKv4 now supports runtime only installs. (Thanks Bill Lorensen)
- This required changes to both Slicer and ITKv4 (for complete compliance).
- The Slicer changes are checked into the repo.
- The ITKv4 changes are tested and merged into master branch of ITKv4
- BRAINSTools was cleaned up to support the COMPONENT Runtime Install
- This required changes to both Slicer and ITKv4 (for complete compliance).
- Clean build process
- Remove configuration warnings about unnecessary/unused configuration commands
- Fix shared library linking for python on Mac for creating successful install
- Complete build success tested to respect superbuild requested compiler (set default CC=/dev/null and CXX=/dev/null to force errors)
Delivery Mechanism
As part of the CMake build system
