Hi Gellule,
Good to hear about your progress on this.
I'm probably the best person to talk to about the install_name_tool, since I'm the main person working on the OS X packaging scripts. I think the main issue with adding -headerpad_max_install_name to the default LDFLAGS is that it needs to be done when building all the libraries in Macports on which Inkscape depends, not just for the Inkscape code itself. I found that some of these Macports libraries don't have enough space for the path rewriting. One hacky solution might be to put all the dylibs in the Inkscape.app/Contents/MacOS directory along with the inkscape executable resulting in a shorter path of just "@executable_path/libsomething.dylib". I didn't experiment too much to see exactly how long the paths could be, because it takes so long to do the path rewriting -- hence the ridiculously long suggested path currently. Even if you were to move all the libraries there, you'd still need to go about relocating all the GTK and python plugins and correcting their paths for the application.
Hi Michael,
Did you consider using ige-mac-bundler / ige-mac-integration?
For the bundling aspect, ige-mac-bundler seems to be working quite well. Currently, I have a working quartz version of Inkscape. I'm going to edit the following blueprint with what I got so far.
https://blueprints.launchpad.net/inkscape/+spec/mac-os-native
-Julien/Gellule