MacOSXPort
Inkscape under Mac OS X
You can run Inkscape by compiling by using Fink. http://fink.sourceforge.net
It's (almost) as simple as: #fink -y install inkscape
Fink will get all the dependencies and install them.
Inkscape requires X11 to use, so you'll need to have a Mac OSX X11 system - Apple has great one you can use for free: http://www.apple.com/macosx/features/x11/download/
However, Inkscape is currently in the unstable tree of Fink, so you will need activate unstable packages first, as described at http://fink.sourceforge.net/faq/usage-fink.php?#unstable.
Special Note for Fink Newbies: On a fresh Fink install for inkscape you will see X11 packages installed. This is fine, it will not overwrite Apple's X11 implementation. They are requirement libraries for Inkscape to run, and once fully installed you will be able to run Inkscape under Apple's X11
Compiling Inkscape under Mac OS X
This could be done using:
http://gtk-osx.sourceforge.net/index.html
Notes
mrdocs has a build machine available
OS X Issues
I recently installed Inkscape and am impressed. However, it seems that there's an issue with window layering. Popups on some dialogs appear *behind* the dialog, eg in the Gradient Editor, clicking the stops popup appears to do nothing. However, if I add a dozen stops, then click the stops popup again, I see the list of added stops *behind* the Gradient Editor dialog.
I wondered if it was because I had used
defaults write com.apple.x11 wm_ffm true
to turn on 'focus follows cursor' but switching that off didn't change the popups/layering issue. --JohnKershaw
X11 Issues
I ran Inkscape for the first time, and it told me that I needed to install X11. I checked out my Utilities folder and sure enough X11 was already installed. I tried running it, and it worked. So I thought it might be a version issue and downloaded X11 from Apple's website. When I run the X11 intaller, it refuses to install because it claims the version of X11 currently installed is newer than the one it's trying to install. In reality, both are version 1.0.
It's lame that something like this prevents the app from working.