No problem. I just ask questions when there's not enough information... and
when I get lucky: things fix themselves. :-)
On Tue, Jun 12, 2012 at 1:43 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> Funny, I just got to looking at this again. I ended up just blowing away
> the build d
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 ar
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
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
libP
