On Sat, Nov 21, 2009 at 11:08 PM, Viktor Szakáts <harbour...@syenar.hu> wrote: > of dylibs. Plus such requirement makes it not possible > to move around .dylib once it's created (but maybe this > how it's meant to be done on OS X). > > What to do? > > 1) Use whatever HB_INSTALL_PREFIX we may have at build pass. > 2) Reapply this parameter on install? (if that's possible)
probably it can be done using otool. > 3) Else? I think that on OS X, one is supposed to produce application bundles which include all libraries not installed by Apple. If you want dylibs for including into app bundles, you should use @executable_path token instead of full path in install_name and have no problems. If install_name (copied to executable from dylib at link time) does not have a correct full path to dylib or @executable_path, one has to set DYLD_LIBRARY_PATH envvar for app to locate it. It seems that these are the only two dylib relocation options offered. -- Ph. _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
