Well, with help from many people and activity on the IRC channel, I've blindly cobbled together some stuff for an OSX .app package. This basically works a lot like our Win32 package: all the libraries come along for the ride. (Which makes it giant: installed >100M, .dmg is 32M) New things in the CVS tree: - configure has --enable-osxapp which turns on my guesses at path locations in src/path-prefix.h - packaging/osx-app.sh attempts to create a .app package from a built inkscape - Info.plist is built from Info.plist.in. I have no idea if this file is valid. To compile inkscape on OSX, with modern fink, everything is available except gc 6.4. I updated the wiki here: http://www.inkscape.org/cgi-bin/wiki.pl?CompilingMacOsX I didn't get into the gc details, but if you build your own gc, and install it in ~/sw, you can build inkscape with: SW=~/sw export CPPFLAGS="-I$SW/include -I/sw/include" export LDFLAGS="-L$SW/include -L/sw/lib" ./configure --prefix=$SW After a "make install", you can build your Inkscape.app with: bash packaging/osx-app.sh Inkscape ~/sw/bin/inkscape Info.plist which should also build the Inkscape.dmg This is all completely untested. The only thing I know for sure is that the library resolution works right (I can run inkscape from the .app directory -- via command line). I have no idea what happens from within OSX itself (I'm ssh'd into a friend's machine). But I'm pretty sure whatever goes wrong can be fixed via src/path-prefix.h and Info.plist.in Good luck! I'm going to sleep! :) -- Kees Cook @outflux.net