[MacPorts] #23092: InsightToolKit should not clean on each build

[MacPorts]

#23092: InsightToolKit should not clean on each build
---------------------------------+------------------------------------------
  Reporter:  trog24@…            |       Owner:  dweber@…           
      Type:  defect              |      Status:  reopened           
  Priority:  Normal              |   Milestone:                     
 Component:  ports               |     Version:  1.8.2              
Resolution:                      |    Keywords:                     
      Port:  InsightToolKit      |  
---------------------------------+------------------------------------------

Comment(by dweber@…):

 Oh, interesting.

 Also, here is a very interesting response from the insight-users at itk.org
 list, by Luis Ibanez (THE guru on ITK):
 {{{
 Hi Darren,

 Let me address first one of the issues that seems to
 be making harder to track the real underlying problem.


        The fact that ITK builds on Mac always
        start to build from scratch.


 We have observed this behavior in the continuous
 builds in Mac Minis in the Dashboard:

 http://www.cdash.org/CDash/index.php?project=Insight#Continuous


 See for example

    *   thurmite.kitware
    *   mini3.nlm


 We believe that this related to a configuration problem
 that was introduced while improving support for SSE
 for other platforms.

 This is a pending issue that we have to solve.

 We suspect (although this is mostly speculation at
 this point) that the problem may be related to try-
 compiles associated with SSE, that were not
 defined correctly in this platform.


     Luis
 }}}


 This is a puzzle to me, because it "appeared" that my build system moved
 very quickly to +75% complete on resuming a prior build.  Also, note in my
 previous snippet that gnumake clearly indicates that some of the Tcl and
 Python builds had "Nothing to be done".

 I wonder if the -o option should appear after the "build" command, i.e.:
 {{{
 $ sudo port -d build -o InsightToolkit  ${variants}
 $ # instead of
 $ sudo port -v -o install InsightToolkit  ${variants}
 }}}
 Also, I wonder if the "install" command is doing the auto-clean, even when
 the build fails.  When testing the port, I use the "build" or "destroot"
 commands.  When I want to run the "install", I also use the -k option to
 keep all the work files.

 Thanks for looking into all this, I hope we get it working.

 PS, maybe something like this would help to track the xorg deps (for the
 c++ dylibs):
 {{{
 for f in /opt/local/lib/InsightToolkit/*.dylib; do otool -L $f | grep
 'xorg'; done
 }}}
 The problem is the right grep pattern - I have no idea what pattern will
 identify links to xorg libs.

-- 
Ticket URL: <http://trac.macports.org/ticket/23092#comment:21>
MacPorts <http://www.macports.org/>
Ports system for Mac OS