Hello Viktor, On 2008/11/20 Szakáts Viktor <[EMAIL PROTECTED]> wrote:
>> >> Well, then I'd guess that the rpath should be embedded into the >> harbour executable and the executables generated by it. Adding >> "--rpath=<your desired path>" (or maybe "-Wl,rpath,<your desired >> path>", not tested) to the gcc command line should do the trick and >> save you of having to specify LD_RUN_PATH each time. >> This is an obscure (for me, at least) feature of gcc, and I could very >> well be wrong, and I shiver at the idea of adding the current >> directory to the run path. But if this is in the line of what you >> want, it could be worth to investigate. >> If this is not in the line of what you want, I'm afraid I completely >> missed your point :-) > > Above is an even worse nightmare :) I'd prefer to not > embed _any_ absolute locations (or any local environment > specific setting whatsoever) anywhere in a program. > An executable always knows the directory it resides in, > and this should be enough for it to find everything needed. > > This is also a main rule for all desktop apps in OSX. I was not thinking of absolute locations when I wrote that. Of course, I share your view about embedding absolute paths. But, AFAIK, changing the paths is precisely what is done when creating OSX apps (by using install_name_tool, I think I remember) I mentioned in another post the ELF statifier <http://statifier.sourceforge.net/>. This creates in linuxes a (pseudo-)static binary, á la OSX. Is perhaps something like this what you have in mind? Best regards, -- Lost _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
