Difference between revisions of "2008 Winter Project Week:CPack"

From NAMIC Wiki
Jump to: navigation, search
Line 61: Line 61:
  
 
* CMake/CPack support for "NAMICSetup" executable instead of running ctest -S
 
* CMake/CPack support for "NAMICSetup" executable instead of running ctest -S
* Like Cygwin setup - do you want to be: "End User", "Module Developer", "Dashboard", "Uber Developer"  
+
* Like Cygwin setup - do you want to be: "End User", "Module Developer", "Dashboard", "Uber Developer"
 +
* Need design requirements document/wiki page for NAMICSetup
  
 
==Additional feedback/bug reports?==
 
==Additional feedback/bug reports?==

Revision as of 00:21, 11 January 2008

Home < 2008 Winter Project Week:CPack
Slicer3 Dashboard


Key Investigators

  • BWH: Katie Hayes, Steve Pieper
  • Kitware: Bill Hoffman, Sebastien Barre, Will Schroeder, Stephen Aylward

Objective

We have created a list of outstanding CPack and CMake issues and bugs (see below) that we would like to get working by the end of the AHM.

Approach, Plan

Our challenge is to rework the existing CPack and CMake framework to incorporate bugfixes, and get Slicer3 to compile and pack with newer versions of the C-tools. Our main purpose at the Project Week is to collaborate on bugfixes and decide how to approach the issues.

Progress

January 2008 Project Week

TBA




Outstanding CPack Issues and Bugs

Gathered for AHM 2008 in Salt Lake City.

Issues:

Katie is hand editing some ITK 3.4 files - niftilib and znzlib cmake_install.cmake files

  • Katie is testing changes to ITK to fix this bug.

Jim and Sebastien - ongoing

RPM support needs testing / validation

  • Awaiting CMake release 2.6.0

Some 32-bit Linux platforms are having trouble with self-extracting STGZ installer, see this bug report.

Windows installer is adding to the Path environment variable in spite of being told not to (seen on Slicer3 for Cmake 2.4.2 and 2.4.7)

Building Slicer3 against an installed VTK rather than a build tree causes trouble; see mail trail from slicer-devel.

C-tools vs. getbuildtest build strategies make continuing support for CPack and compiling difficult.

  • CMake/CPack support for "NAMICSetup" executable instead of running ctest -S
  • Like Cygwin setup - do you want to be: "End User", "Module Developer", "Dashboard", "Uber Developer"
  • Need design requirements document/wiki page for NAMICSetup

Additional feedback/bug reports?