On 8/9/09 09:24, ~suv wrote:
On 8/9/09 06:38, Michael Wybrow wrote:
Also, it the package no longer uses the DYLD_LIBRARY_PATH environment variable to specify where the libraries can be found. Instead they all have their internal paths rewritten at packaging time to be relative to the path of the executable. To allow enough space in the libraries and executables for this path rewriting, the packager must use a Macports installation that has been installed in a longer than normal PREFIX. I don't know what the minimum size is, but I've put a requirement in the packaging script to check that it is at least 50 characters. Thus it needs to be installed in something like /opt/ local-universal-macports-in-really-long-prefix-for-inkscape-etc-etc... you get the idea. This should solve a lot of problems with our bundled libraries conflicting with system versions.
i.e. unless I modify the limit in osx-app.sh locally, I have to rebuild the complete MacPorts tree for Inkscape if I 'svn update' to the current version of the packaging files in trunk?
sorry, I was answering in a haste and didn't read all changed lines in 'osx_app.sh' to the end - the instructions in the comments are loud and clear ;-)
Could you take a look at my patch in Bug #424394 “Launching and Path problems under Mac”? https://bugs.launchpad.net/inkscape/+bug/424394
I have been using it for several days now with different application paths (several ' ', '&', '|' and '#' combinations). As I wrote in the last comment I had to change the '#' escaping for the other two resource files as well which eliminates the need for 'ESCAPED2TOP'.
~suv