Hi Phil, >> 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.
Thank you very much for the information and research. install_name_tool needs old value, so it's not very easy to work with at first sight. I most probably won't have enough time to make deeper changes here now, so if you have free time + motivation, pls feel free to make modifications in that direction. Pbly the easiest would be to embed HB_INSTALL_PREFIX in install name on build when HB_SYSLOC != yes. It would cover most real-life scenarios. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
