No problem. I just ask questions when there's not enough information... and when I get lucky: things fix themselves. :-)<div><br><br><div class="gmail_quote">On Tue, Jun 12, 2012 at 1:43 PM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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:<br>
<br>
The output stated that libPipelineBuilder.dylib was being fixed up.<br>
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.<br>
<br>
Sorry for the noise.<br>
--<br>
Mike Jackson <<a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a>><br>
<div class="HOEnZb"><div class="h5"><br>
On Jun 12, 2012, at 1:40 PM, David Cole wrote:<br>
<br>
> Are there any errors or warnings reported in the full output stream?<br>
><br>
> Is there output indicating that "libPipelineBuilderLib.dylib" is being fixed up at some point?<br>
><br>
> Is it possible that something is overwriting/re-copying libPipelineBuilderLib.dylib after it's been fixed up?<br>
><br>
><br>
> On Mon, Jun 11, 2012 at 4:42 PM, Michael Jackson <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
> 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:<br>
><br>
> -- 5/14: copying '/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'<br>
> -- key='libPipelineBuilderLib_dylib'<br>
> -- item='/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'<br>
> -- resolved_item='/Users/mjackson/Workspace/DREAM3D/zRel/Bin/libPipelineBuilderLib.dylib'<br>
> -- default_embedded_path='@executable_path/../lib'<br>
> -- embedded_item='@executable_path/../lib/libPipelineBuilderLib.dylib'<br>
> -- resolved_embedded_item='/Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib'<br>
> -- copyflag='1'<br>
><br>
><br>
> That all looks correct. But otool -L gives this output:<br>
> 532:[mjackson@Ferb:zRel]$ otool -L /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib<br>
> /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/lib/libPipelineBuilderLib.dylib:<br>
> libPipelineBuilderLib.dylib (compatibility version 0.0.0, current version 0.0.0)<br>
> /Users/Shared/Toolkits/Qt-4.7.4-Cocoa/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.4)<br>
> /Users/Shared/Toolkits/Qt-4.7.4-Cocoa/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.4)<br>
> /Users/Shared/Toolkits/hdf5-187/lib/libhdf5.1.8.7.dylib (compatibility version 1.8.7, current version 1.8.7)<br>
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)<br>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)<br>
><br>
> 533:[mjackson@Ferb:zRel]$ otool -L /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/MacOS/DREAM3D<br>
> /Users/Shared/Toolkits/DREAM3D.v3/DREAM3D.app/Contents/MacOS/DREAM3D:<br>
> @executable_path/../Frameworks/QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.4)<br>
> @executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.4)<br>
> @executable_path/../lib/libPipelineBuilderLib.dylib (compatibility version 0.0.0, current version 0.0.0)<br>
> @executable_path/../lib/libhdf5.1.8.7.dylib (compatibility version 1.8.7, current version 1.8.7)<br>
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)<br>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)<br>
><br>
><br>
> Has anyone seen a failure like this before? Seems odd.<br>
> ___________________________________________________________<br>
> Mike Jackson Principal Software Engineer<br>
> BlueQuartz Software Dayton, Ohio<br>
> <a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a> <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
><br>
> --<br>
><br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
<br>
</div></div></blockquote></div><br></div>