[CMake] Failure of Bundle Utilities on OS X to update a library.

[Michael Jackson]

Funny, I just got to looking at this again. I ended up just blowing away the build directory and recompiling and now it all works as it should. To answer your questions though:

  The output stated that libPipelineBuilder.dylib was being fixed up.
  I was running a script that moved some stuff around in the final installation location which should NOT have been recopying in the built library but things can happen.

 Sorry for the noise.
--
Mike Jackson <www.bluequartz.net>

On Jun 12, 2012, at 1:40 PM, David Cole wrote:

> Are there any errors or warnings reported in the full output stream?
> 
> Is there output indicating that "libPipelineBuilderLib.dylib" is being fixed up at some point?
> 
> Is it possible that something is overwriting/re-copying libPipelineBuilderLib.dylib after it's been fixed up?
> 
> 
> On Mon, Jun 11, 2012 at 4:42 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> I have an App that gets built and installed (DREAM3D.ap) that depends on a shared library (libPipelineBuilder.dylib) that also gets built during the whole compile process. I run "make install" (from command line - Makefiles are generated) and after BundleUtilities is called and I check the libPipelineBuilder.dylib file with "otool -L" the paths are not updated correctly. I switched on the verbose output for BundleUtilities and I think this is the relevent section:
> 
> -- 5/14: copying '/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'
> -- key='libPipelineBuilderLib_dylib'
> -- item='/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'
> -- resolved_item='/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'
> -- default_embedded_path='@executable_path/../lib'
> -- embedded_item='@executable_path/../lib/libPipelineBuilderLib.dylib'
> -- resolved_embedded_item='/Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib'
> -- copyflag='1'
> 
> 
> That all looks correct. But otool -L gives this output:
> 532:[mjackson at Ferb:zRel]$ otool -L /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib
> /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib:
>  libPipelineBuilderLib.dylib (compatibility version 0.0.0, current version 0.0.0)
>  /Users/Shared/Toolkits/Qt-4.7.4-Cocoa/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.4)
>  /Users/Shared/Toolkits/Qt-4.7.4-Cocoa/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.4)
>  /Users/Shared/Toolkits/hdf5-187/lib/libhdf5.1.8.7.dylib (compatibility version 1.8.7, current version 1.8.7)
>  /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
>  /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)
> 
> 533:[mjackson at Ferb:zRel]$ otool -L /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/MacOS/DREAM3D
> /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/MacOS/DREAM3D:
>        @executable_path/../Frameworks/QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.4)
>        @executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.4)
>        @executable_path/../lib/libPipelineBuilderLib.dylib (compatibility version 0.0.0, current version 0.0.0)
>        @executable_path/../lib/libhdf5.1.8.7.dylib (compatibility version 1.8.7, current version 1.8.7)
>        /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
>        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)
> 
> 
> Has anyone seen a failure like this before? Seems odd.
> ___________________________________________________________
> Mike Jackson                    Principal Software Engineer
> BlueQuartz Software                            Dayton, Ohio
> mike.jackson at bluequartz.net              www.bluequartz.net
> 
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>