On ven, 2009-01-23 at 17:02 +0100, Lorenzo Mancini wrote: > Hello guys, > > from Leopard on, the special name @executable_path cannot be used > anymore in library paths for runtime substitution; two new special names > (@rpath and @library_path) were introduced for similar purposes.
The link you posted: http://www.codeshorts.ca/2007/nov/01/leopard-linking-making-relocatable-libraries-movin says that the ld flag "-executable_path" is gone, not the @executable_path special symbol within binaries. If Apple dropped the special symbol, the old binaries would suddenly stop working, and I think this is not an option for Apple. By removing the command line option, they're simply forcing *developers* to use the new option when they switch to 10.5. > PyInstaller currently uses @executable_path to do its magic: it should > continue to do so if running under Mac OS X < 10.5, and switch to @rpath > if running under >= 10.5. In any case, the patch is wrong because it checks the version of the host computer (running PyInstaller) not the target computer (running the final product). PyInstaller should try to generate executables as compatible as possible, so using the old system seems preferrable. Otherwise, we would have to introduce a way to specify, within the spec file, "I want to build an executable that runs on Mac OSX 10.5+", and then use *this* flag to do such a check. The host operating system version is immaterial. -- Giovanni Bajo Develer S.r.l. http://www.develer.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
