O.k., progress so far: Commented lines in osx-app.sh about pangox.aliases, seems to not have had any negative effect. Running otool -L and the lengthier version in the script (it runs grep and stuff to get the strings down to just the pathnames) however also only references -quartz variants, and no -x11 so I still don't know where it gets those names from. However, while complaining about those libraries, the script finishes and at least on my machine the bundle runs (although with an icon in the dock for inkscape and for inkscape-bin, annoyingly) I wanted to test on my brother's more "just out of factory" like MBP but he's busy studying so that will have to wait. I attached both otool outputs as a textfile, not sure that will be of much use, but who knows.
@jiho looking at the python script and the gimp way, but for ex. the python script for me just says ":: mkdir -p Inkscape.app/Contents/Frameworks/" and I didn't look more closely at it yet after that. As for the gimp build: I'd rather make it work properly with my current macports install, (apart from maybe deactivating/activating one port or another) both for HD constraint reasons (macports is on / which is only 80 GB in my case, and that can't change) (though ofc it might be the better way if I had a dedicated machine for that)
@Henning I'd rather stay away from CMake if possible, for one I know next to nothing about it, and it seems to handle the creation of actual installers for mac software, which really shouldn't be necessary for inkscape (because we shouldn't need to change any system files or anything, or do other install kung-fu) Basically the form in which it is packaged now is just a folder, that appears as one ".app" package to the user, and he just drag& drops it to Applications or even elsewhere if he wants.
I uploaded the most recent package I made (probably far from perfect but I need some testers) to http://rapidshare.com/files/180771457/Inkscape_2_.dmg Sorry for rapidshare, I have some personal webspace too, but mailinglist archives have such a long memory ... So if any mac users are readings this, please test this. (btw, anything less than leopard is even less tested, I'm not sure about ppc, but probably won't work either)
so long ...
On Wed, Jan 7, 2009 at 7:51 AM, Michael Wybrow <michael.wybrow@...38...> wrote:
On 07/01/2009, at 2:42 PM, step21 wrote:
I'll continue with the packaging tomorrow cause it's going to be 5 am soonish, but currently I have the following issues if anyone has a quick thought on one of those. I was under the impression I could use osx-app.sh for native packaging too, but so far: (note: in the paths below /opt/local/ is the macports install path passed to "osx-app.sh" with --libraries) /opt/local/etc/pango/pangox.aliases is not in my macports install (which it tries to copy) so is this a file specific to x11 pango (pango was installed with macports using +no_x11 ofc)
pangox.aliases contains information about the X font set, so if you're not using X11 then I imagine it can just be omitted.
Also the script is looking for: /opt/local/lib/libgtk-x11-2.0.0.dylib /opt/local/lib/libgdk-x11-2.0.0.dylib Only in a native version those would have to be: /opt/local/lib/libgtk-quartz-2.0.0.dylib /opt/local/lib/libgdk-quartz-2.0.0.dylib And so far I'm not quite sure how it gets the impression that it needs the x11 version, at first I thought it was hardcoded in the script, but it's not.
No, none of the dependencies are hardcoded. It determines what they are by recursively calling "otool -L" on the inkscape executable and all the libraries it depends on. Thus, I'd say that if you're seeing this then it means that something didn't compile properly in Macports as +no_x11 and still has the libgtk-x11 library as a dependency. You can probably just use otool yourself to figure out which dependency this is and address the problem.
This is a it strange since the app bundling script should only reference libraries that that copy of Inkscape is linked against -- that is, it shouldn't really be possible for it to reference a non-existent library, or it wouldn't have linked in the first place... unless maybe you have forced removal of a macports package after linking Inkscape. Weird!
Cheers, Michael