inkscape-xcodeproject-mac

On 2013-03-19 09:16 +0100, Alek Slater wrote:
> Have any of you attempted to create an XCode project for inkscape?

As far as I know no one did (or if so, did not publish the results of
such an attempt). Inkscape only has a few developers active at any time,
and most of those do not use OS X for developing and have no access to
OS X systems either.

> Or at the very least managed to get the main branch of inkscape
> building on a Mac OS X Mountain Lion ?

1) Inkscape itself (stable release branch <lp:inkscape/0.48.x> as well
as current trunk <lp:inkscape>) compiles ok on Lion, and AFAIK on
Mountain Lion too, at least the regular command line version.
Note: stable branch only builds with llvm-gcc-4.2 (or Apple's GCC 4.2.1
on Mac OS X 10.5.8), latest trunk now builds with clang too
(work-in-progress).

2) Packaging aka creating an Inkscape.app is broken since around the
time Snow Leopard had been released.
Currently there's a an on-going attempt to rewrite the bundling process
and improve the osx integration (menubar, shortcut modifier, clipboard,
drag&drop) if using the Quartz backend of GTK+ - there are however no
pushlished sources available yet for the latest RC packages of Inkscape
0.48.4 for OS X 10.7/10.8. You can find some details about the progress
in the archives of the developers mailing list 'inkscape-devel', e.g.
archived here:
<http://sourceforge.net/mailarchive/forum.php?forum_name=inkscape-devel>
<http://news.gmane.org/gmane.comp.graphics.inkscape.devel>
<http://inkscape.13.n6.nabble.com/Inkscape-Dev-f2781808.html>

3) MacPorts, Fink as well as Homebrew offer ports for the latest stable
Inkscape release (0.48.4), and MacPorts has a port for a recent version
of trunk, too (inkscape-devel). With MacPorts, you can also choose
whether you install the GTK+ stack with X11 or Quartz backend (AFAIK
neither Fink nor Homebrew offer this currently).
Note: none of these package management systems will create an app bundle
'Inkscape.app' (not a fully relocatable self-contained one, and as far
as I'm aware neither a fake one with just a basic skeleton).

> I've attempted the various building for mac os x guides that are
> sprinkled across the site / wiki / READMEs, but with no avail.

Without knowing what you tried to do, and what failed how, it is
difficult to provide any hints/tips.

> Any hints as to what I need to to do to make it possible to build
> Inkscape from source on a more recent version of Mac OS X?

Depends on what you need a more recent build than 0.48.2 for:
one "easy" way to get a fully working Inkscape 0.48.4 compiled from
source and installed on Mountain Lion is probably via MacPorts ('sudo
port install inkscape' should take care of all required dependencies,
and if you want to build with the Quartz backend, add the corresponding
variants to the global MacPorts configuration before installing any of
the dependencies).

Once you have the minimal dependencies installed in MacPorts (e.g. by
installing the 'inkscape' port, or the 'inkscape-devel' port), you could
also check out the current development version (trunk) from bzr (hosted
at launchpad.net), and compile it - outside of the MacPorts prefix -
either manually with the normal autools build system (you will need to
configure your shell env accordingly), or use
'src/packaging/macos/osx-build.sh'. The build script conventiently sets
up the build env for you - just make sure to _not_ build with
'--enable-osxapp' (i.e. remove it from $CONFFLAGS): the script is ok for
command line builds from source, but as mentioned earlier, creating an
app bundle will fail with the current scripts in the source code repository.

Great, thanks for all this, much appreciated.

I've actually wanted to try and get into inkscape's source for years, but every time I've tried it I've had to give up because I can never get a working development environment working :( None of the guides are ever up to date, anyways this is my progress so far, I've gotten to the configure step.

I've had to install automake and autoconf to get the autogen.sh script to work, used the following guide here:
http://jsdelfino.blogspot.com/2012/08/autoconf-and-automake-on-mac-os-x.html
That gets me a working ./configure,

So when I try to run ./configure I get errors like:
configure: error: Package requirements (gdkmm-2.4 glibmm-2.4 giomm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= 2.0.12 gthread-2.0 >= 2.0 libpng >= 1.2 gsl) were not met:

I guess I need to install all those packages too somehow? (macports wont cover it as im using homebrew, and homebrew doesnt have these packages, and i cant mix macports and homebrew without dangerous side-effects).

On 2013-03-19 12:51 +0100, Alek Slater wrote:
> I guess I need to install all those packages too somehow? (macports wont
> cover it as im using homebrew, and homebrew doesnt have these packages,
> and i cant mix macports and homebrew without dangerous side-effects).

Homebrew now has a formula for Inkscape 0.48.4, so I have to assume that
it covers the minimal requirements to build at least the stable version
of Inkscape [1]:

<https://github.com/mxcl/homebrew/blob/master/Library/Formula/inkscape.rb>

-----
[1] I'm not using Homebrew (relying on MacPorts myself), but based on
the feedback/comments in
<https://answers.launchpad.net/inkscape/+question/224539>
it seems that the current formula doesn't have full support for PDF
handling in Inkscape yet (that's though not an Inkscape problem, and
needs to be discussed with the author of the homwbrew formula), but
otherwise works ok.

On 2013-03-19 13:26 +0100, ~suv wrote:
> On 2013-03-19 12:51 +0100, Alek Slater wrote:
>> I guess I need to install all those packages too somehow? (macports wont
>> cover it as im using homebrew, and homebrew doesnt have these packages,
>> and i cant mix macports and homebrew without dangerous side-effects).
>
> Homebrew now has a formula for Inkscape 0.48.4, so I have to assume that
> it covers the minimal requirements to build at least the stable version
> of Inkscape [1]:
>
> <https://github.com/mxcl/homebrew/blob/master/Library/Formula/inkscape.rb>

Note that the build script(s) maintained in Inkscape's tree (which I had
mentioned earlier) rely on MacPorts for all dependencies
(src/packaging/macosx/osx-build.sh), and you might have to adjust some
paths if you want to use them with Homebrew (untested territory though).

Unfortunately <https://github.com/mxcl/homebrew/blob/master/Library/Formula/inkscape.rb> is completely broken when I try it, the end inkscape that i get from that is completely messed up, with most of the icons and buttons missing etc.

After I install it though I get a tiny bit further:

configure: error: Package requirements (gdkmm-2.4 glibmm-2.4 giomm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= 2.0.12 gthread-2.0 >= 2.0 libpng >= 1.2 gsl) were not met:

Package 'xcb-shm', required by 'cairo', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables INKSCAPE_CFLAGS
and INKSCAPE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

On 2013-03-19 15:51 +0100, Alek Slater wrote:
> Unfortunately
> <https://github.com/mxcl/homebrew/blob/master/Library/Formula/inkscape.rb>
> is completely broken when I try it, the end inkscape that i get from
> that is completely messed up, with most of the icons and buttons missing
> etc.

If icons etc. are missing, this is usually in indicator that you are
trying to run inkscape directly from the build dir, without having at
least once installed it (with 'make install'): Inkscape expects the
resources (like icons, templates, etc.) to be found in '$prefix/share'
("$prefix": whatever has been used when running configure, default is
'/usr/local' for $prefix if not specified explicitly when running
configure).

If 'make install' doesn't solve the issue with missing icons and other
resources not found, you probably should consider asking in
homebrew-related support resources about this... it then doesn't look
like a question about (compiling) Inkscape to me anymore, but more about
setting up and using homebrew (AFAIK the formula for Inkscape does work
ok, apart from the lack of full PDF support).

Unfortuntately, I can't help you with issues using homebrew itself nor
with questions about compiling inkscape with dependencies installed via
homebrew (since I don't use homebrew myself and have no plans to switch
form MacPorts to Homebrew either), and I don't know anyone from the
Inkscape team who might happen to use it to build e.g. inkscape trunk,
either.

Ah sorry let me rephrase that, the inkscape that I got working from homebrew was broken without icons, but I'm not too interested in getting a working Inkscape to work via homebrew or macports for that matter, I just want a working development environment on my Mac so I can delve into inkscape, see if I can change some stuff etc.

Back to the problem at hand, regardless if I'm using homebrew or not, I should be able to get this thing to build, I mean, you can't all rely on Macports? Wonder how the person who built the Inkscape.app I use did it, that app works really well, its a shame he/she did not check it in anywhere?

The problem that crops up when I do a ./configure may or may not be related to homebrew or not, but I'm sure its just a matter of passing something to ./configure to make it look at a different place, because I know for certain I have xcb-shm on my system.

On 2013-03-19 17:16 +0100, Alek Slater wrote:
> Back to the problem at hand, regardless if I'm using homebrew or not, I
> should be able to get this thing to build, I mean, you can't all rely on
> Macports? Wonder how the person who built the Inkscape.app I use did it,
> that app works really well, its a shame he/she did not check it in
> anywhere?

The package of Inkscape 0.48.2 was done (as 32bit Universial Intel + PPC
build) on Mac OS X 10.5.8, with the packaging scripts of the release
branch at the time - all available in public [1]. Packaging itself (more
specific, compiling the launcher app) doesn't work with more recent
versions of Xcode and OS X though (as mentioned earlier).

It's easy to shame someone without caring about the facts or doing
minimal research yourself about the details, but it's not how you will
make others eager to provide further help.

[1]
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_48_BRANCH/files/9819>

On 2013-03-19 17:16 +0100, Alek Slater wrote:
> Ah sorry let me rephrase that, the inkscape that I got working from
> homebrew was broken without icons, but I'm not too interested in getting
> a working Inkscape to work via homebrew or macports for that matter, I
> just want a working development environment on my Mac so I can delve
> into inkscape, see if I can change some stuff etc.

No matter how you compile Inkscape (stable or trunk), for which purpose
- you have it install the current build into its prefix at least _once_,
to have a fully working build (else inkscape is not able to find and
load the shared resources).

Just a friendly suggestion, but perhaps its an idea to make setting up a workable dev environment a bit easier than it currently is.
It may help you attract more developers to help you.

On 2013-03-19 18:01 +0100, Alek Slater wrote:
> Just a friendly suggestion, but perhaps its an idea to make setting
> up a workable dev environment a bit easier than it currently is. It
> may help you attract more developers to help you.

Inkscape is a volunteer based project - maybe, once everything has been
sorted out, you could be the one to help with instructions using
homebrew to install dependencies for Inkscape (trunk)?

Currently, there is no maintainer for Inkscape's OS X packages (besides
Valerio, who recently joined the project to work on getting updated
stable release OS X packages built & uploaded (see mailing list
'inkscape-devel'), but hasn't yet committed any code yet) - none (of the
few) active core developers could provide ad-hoc detailed assistance for
e.g. custom build environments based on Homebrew (OTOH, once you have
the required dependencies installed, you mainly need to set the basic
build env variables as e.g. described in the wiki [1], and for builds
from the stable release branch, you probably need to add one for aclocal
($ACLOCAL_FLAGS), too. This is basically identical to how
autotools-based build systems work on Linux-based systems, the main
platform used by Inkscape developers).

Please keep in mind that for the past few stable releases, MacPorts was
the recommended way for Inkscape packagers on OS X to get the required
dependencies installed, and the one to be used with the osx build &
packaging scripts which are maintained within the Inkscape source code
repository - at the time those scripts had been developed, homebrew
didn't even exist yet.

I'm off for today, but maybe we can restart the discussion later this
week...

[1]
<http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX#Setting_the_build_environment>

Thanks a lot mate, I'll def keep trying, will update it in here if I manage to sort it out. Or if I stumble into something I think you might know or be able to help with.

My dream scenario, albeit not likely due to the limited time i have available, is to create an XCode project that mac developers can use to help develop inkscape. But yeah even without that, getting it to work without relying on macports is also not a bad idea ;)

Thanks anyway.

On 2013-03-19 18:42 +0100, ~suv wrote:
> build env variables as e.g. described in the wiki [1], and for builds
> from the stable release branch, you probably need to add one for aclocal
> ($ACLOCAL_FLAGS), too. This is basically identical to how

Correction:

*) After searching old messages, here are the details about what I had
to set in addition to the variables listed in the wiki, if compiling
inkscape "manually" (i.e. if not using the scripts in 'packaging/macosx'):

On 28/8/09 20:10, ~suv wrote:
 > export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal"
 > export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"

where $LIBPREFIX is the MacPorts prefix, which in your case would have
to be the common prefix used by Homebrew.

[ Quote taken from a rather old thread on the mailing list:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/focus=31221>
]

AFAIK current trunk now has a proper check for libpng, and should be
able to detect libpng correctly based on its pkgconfig file:
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/12152>
(I haven't tested it explicitly on OS X, since above variables are still
defined in my custom builds script I use to update various branches of
Inkscape trunk on OS X Lion)

*) Another recent change to the build system in current trunk:
If not specified otherwise, autogen.sh will now run configure
automatically, which might not desired if one wants to build out-of-src,
or configure with a custom prefix - see these comments for details how
to handle this:
<https://bugs.launchpad.net/inkscape/+bug/992047/comments/9>
<https://bugs.launchpad.net/inkscape/+bug/992047/comments/21>

Ok, thanks to your fantastic advice and some poking around on my part, it's now building and I can make an executable I think.

This is what I had to resort to to get it working to this stage, note this was the trunk version:

curl -OL http://ftpmirror.gnu.org/autoconf/autoconf-2.68.tar.gz
tar xzf autoconf-2.68.tar.gz
cd autoconf-2.68
./configure
make
make install
cd ..

curl -OL http://ftpmirror.gnu.org/automake/automake-1.11.tar.gz
tar xzf automake-1.11.tar.gz
cd automake-1.11
./configure
make
make install
cd ..

curl -OL http://ftpmirror.gnu.org/libtool/libtool-2.4.tar.gz
tar xzf libtool-2.4.tar.gz
cd libtool-2.4
./configure
make
make install
cd ..

brew install libxslt
brew install inkscape

export PKG_CONFIG_PATH="/opt/X11/lib/pkgconfig/:/usr/local/opt/libxslt/lib/pkgconfig/:/usr/local/opt/libxml2/lib/pkgconfig/:$PKG_CONFIG_PATH"

sh autogen.sh

So my previous comment illustrates that I've managed to build it, seemingly without error,
however when I run the compiled binary:

skela@skelimac:~/Code/Inkscape/inkscape$ /usr/local/bin/inkscape

(inkscape:41688): Gtk-WARNING **: Could not find the icon 'object-visible'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
 http://icon-theme.freedesktop.org/releases
2013-03-24 02:52:43.660 inkscape[41688:707] CoreText: Invalid 'morx' Subtable In CTFont <name: ChalkboardSE-Regular, size: 13.333008, matrix: 0x0>
CTFontDescriptor <attributes: <CFBasicHash 0x7fcc4ec7bb60 [0x7fff79dcafd0]>{type = mutable dict, count = 1,
entries =>
 2 : <CFString 0x7fff79acaef0 [0x7fff79dcafd0]>{contents = "NSFontNameAttribute"} = <CFString 0x7fcc4ccaa2d0 [0x7fff79dcafd0]>{contents = "ChalkboardSE-Regular"}
}
>

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

hicolor is a GTK theme isn't it, so I reckon thats missing or something, but here's a print out of my configuration at this time:

Configuration:

        Source code location: .
        Destination path prefix: /usr/local
        Compiler: g++
        CPPFLAGS: -DG_DISABLE_DEPRECATED -DGLIBMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED -DGTK_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_DEPRECATED -DGTKMM_DISABLE_DEPRECATED -Werror=format-security -DGSEAL_ENABLE -DG_DISABLE_SINGLE_INCLUDES -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2
        CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -fopenmp
        CFLAGS: -Wno-pointer-sign -g -O2
        LDFLAGS:

        Use gnome-vfs: no
        Use openoffice files: yes
        Use relocation support: no
        Enable LittleCms: yes
        Enable DBUS: no
        Enable Poppler-Cairo: yes
        ImageMagick Magick++: no
        Libwpg: no
        Libvisio: no
        Libcdr: no
        Doing Local Install: no
        GTK+ backend target: x11

Are there any of these that are giving me the "no" that in reality needs to be "yes" for things to work?

> export PKG_CONFIG_PATH="/opt/X11/lib/pkgconfig/:/usr/local/opt/libxslt/lib/pkgconfig/:/usr/local/opt/libxml2/lib/pkgconfig/:$PKG_CONFIG_PATH"

Is mixing libraries installed by XQuartz with those installed by Homebrew how things are done with Homebrew? Can you verify which versions of pango, cairo, etc. the compiled inkscape binary (trunk) links to, and whether that matches your expectations (build inkscape trunk with newer dependencies installed with Homebrew, link to the same ones as e.g. the GTK+ dylibs do)?

Command to list all linked dylibs and shared libraries:
$ otool -L ~/Code/Inkscape/inkscape/src/inkscape

> (inkscape:41688): Gtk-WARNING **: Could not find the icon 'object-visible'.
> The 'hicolor' theme was not found either, perhaps you need to install it.

The warning about the missing hicolor icon theme is harmless, and does not produce the crash.

MacPorts for example has a package for it:
<http://www.macports.org/ports.php?by=name&substr=hicolor-icon-theme>
I don't know how homebrew handles details of GTK+ like icons and themes.

> 2013-03-24 02:52:43.660 inkscape[41688:707] CoreText:

This puzzles me: the 'CoreText' warning comes from the native OS X system - usually Inkscape does not trigger such warnings (since with X11-based dependencies, it bypasses Apple's font system completely, and uses fontconfig+freetype+pango). The warning possibly is triggered by pango / pangocairo using the native font backend on OS X (coretext) - odd though that via Homebrew you get a mix of dependencies installed with the X11 backend (GTK+), and dependencies with the Quartz backend (apparently pango)?

[ personally I never used a newer pango version than 1.32.5 myself (with GTK+/Quartz), and 1.30.1 (with GTK+/X11). Homebrew AFAIK already had upgraded pango to 1.32.6 (which without patch crashes Inkscape, and actually is an unstable version of pango - see also Inkscape bug #1114392). ]

In case the crash is triggered by an uncaught exception from the font backend - does inkscape still crash if you temporarily uninstall the affected font 'ChalkboardSE-Regular,' (move it out of the 'Fonts' folder - disabling via FontBook has no affect on Inkscape)? Based on e.g. <http://nisus.com/forum/viewtopic.php?f=18&t=5075> even Apple's own font services complain about it.

> Use gnome-vfs: no

This is less recommended, but likely not related to the crash. Via MacPorts, I have the port 'gnome-vfs' installed to satisfy this dependency:
<http://www.macports.org/ports.php?by=name&substr=gnome-vfs>

Otherwise, I can't see any additional details about where the crash actually happens: could you e.g. pastebin the crash report (search '~/Library/Logs/CrashReports/' for the latest one about inkscape) somewhere, and post the link to the pastebin here, or create a backtrace yourself with gdb, and pastebin that one? Possibly that problematic font in the end triggers the crash, or something else is wrong - myself, I could not tell based on the available information.

> (search '~/Library/Logs/CrashReports/' for the latest one about inkscape)

Sorry - that's an incorrect path, should be:
(search '~/Library/Logs/DiagnosticReports/' for the latest one about inkscape)

Homebrew doesn't have everything I need so I have to mix it a bit.
Here's the otool output:
skela@skelimac:~/Code/Inkscape/inkscape$ otool -L ~/Code/Inkscape/inkscape/src/inkscape
/Users/skela/Code/Inkscape/inkscape/src/inkscape:
 /usr/local/lib/libgc.1.dylib (compatibility version 2.0.0, current version 2.3.0)
 /usr/local/opt/libxslt/lib/libxslt.1.dylib (compatibility version 3.0.0, current version 3.28.0)
 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
 /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
 /usr/local/lib/libgthread-2.0.0.dylib (compatibility version 3401.0.0, current version 3401.3.0)
 /opt/X11/lib/libpng15.15.dylib (compatibility version 27.0.0, current version 27.0.0)
 /usr/local/lib/libgsl.0.dylib (compatibility version 17.0.0, current version 17.0.0)
 /usr/local/lib/libgslcblas.0.dylib (compatibility version 1.0.0, current version 1.0.0)
 /usr/local/lib/libgtkmm-2.4.1.dylib (compatibility version 3.0.0, current version 3.0.0)
 /usr/local/lib/libatkmm-1.6.1.dylib (compatibility version 3.0.0, current version 3.0.0)
 /usr/local/lib/libgdkmm-2.4.1.dylib (compatibility version 3.0.0, current version 3.0.0)
 /usr/local/lib/libgiomm-2.4.1.dylib (compatibility version 5.0.0, current version 5.0.0)
 /usr/local/lib/libpangomm-1.4.1.dylib (compatibility version 2.0.0, current version 2.30.0)
 /usr/local/lib/libglibmm-2.4.1.dylib (compatibility version 5.0.0, current version 5.0.0)
 /usr/local/lib/libcairomm-1.0.1.dylib (compatibility version 6.0.0, current version 6.0.0)
 /usr/local/lib/libsigc-2.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
 /usr/local/lib/libgtk-x11-2.0.0.dylib (compatibility version 2401.0.0, current version 2401.16.0)
 /usr/local/lib/libgdk-x11-2.0.0.dylib (compatibility version 2401.0.0, current version 2401.16.0)
 /usr/local/lib/libpangocairo-1.0.0.dylib (compatibility version 3201.0.0, current version 3201.6.0)
 /usr/local/lib/libatk-1.0.0.dylib (compatibility version 20610.0.0, current version 20610.1.0)
 /opt/X11/lib/libcairo.2.dylib (compatibility version 11203.0.0, current version 11203.2.0)
 /usr/local/lib/libgdk_pixbuf-2.0.0.dylib (compatibility version 2601.0.0, current version 2601.5.0)
 /usr/local/lib/libgio-2.0.0.dylib (compatibility version 3401.0.0, current version 3401.3.0)
 /usr/local/lib/libpangoft2-1.0.0.dylib (compatibility version 3201.0.0, current version 3201.6.0)
 /usr/local/lib/libpango-1.0.0.dylib (compatibility version 3201.0.0, current version 3201.6.0)
 /usr/local/lib/libgobject-2.0.0.dylib (compatibility version 3401.0.0, current version 3401.3.0)
 /usr/local/lib/libglib-2.0.0.dylib (compatibility version 3401.0.0, current version 3401.3.0)
 /usr/local/opt/gettext/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.2.0)
 /opt/X11/lib/libfontconfig.1.dylib (compatibility version 8.0.0, current version 8.2.0)
 /opt/X11/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0)
 /usr/local/opt/libxml2/lib/libxml2.2.dylib (compatibility version 12.0.0, current version 12.0.0)
 /usr/local/lib/libpopt.0.dylib (compatibility version 1.0.0, current version 1.0.0)
 /opt/X11/lib/libfreetype.6.dylib (compatibility version 15.0.0, current version 15.1.0)
 /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
 /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
 /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 155.0.0)
 /usr/local/lib/libjpeg.8.dylib (compatibility version 13.0.0, current version 13.0.0)
 /usr/local/lib/liblcms.1.0.19.dylib (compatibility version 2.0.0, current version 2.19.0)
 /usr/local/lib/libpoppler.26.dylib (compatibility version 27.0.0, current version 27.0.0)
 /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)

I've had a look at removing the font like you mentioned, but the fonts folder in share is empty.

And I've run the compiled binary a couple of times, but the Log folders (both that you mentioned) don't have an entry for inkscape. So is it possible its crashing before the logger manages to initialise or something like that? :P

Its worth mentioning that cairo was installed using homebrew, so it would appear homebrew will mix paths like this when possible.

In the process of installing macports, I've had it with homebrew, the only reason why I switched over to homebrew was the poor support for mountain lion in macports, which seems to have changed.

Ok, its all working now, flawlessly, out of the box using portage.
I did as you said, install inkscape using macports, to get all the dependancies added.
After that autogen / configure + make worked without fault.

For reference, to any who have similar issues to me, these are the commands I performed:
sudo port install inkscape
sh autogen.sh (if ./configure fails)
make
src/inkscape

Thanks suv for your patience and guidance here, homebrew is completely broken, so I guess there's a reason why you use macports. ;D

PS: the compiled build works much faster than the one I have installed. :D

Got it working in Xcode too now :)

> Got it working in Xcode too now :)

Any plans to share the Xcode project? ;)

(Glad you figured out a way to compile inkscape trunk on your system)

yeah i would like to share the xcode project, whats the best way do you think?

I've got it building and debugging from xcode now, so its all good, apart from the intellisense (that does not seem to work fully, but may not be needed).

If you have a mac, its just a matter of creating a new OSX External Build System XCode project, you then right click on the blue Inkscape project file inside XCode on the left (in the tree), right click to add the inkscape src folder.

You then Go to Targets, and make sure the directory (in the external build tool configuration is pointing to the inkscape src folder.

That will get you a project that builds.

If you also want to debug and run it, you can click Product -> Scheme -> Edit Scheme,
Make sure Debugger is set to GDB, and the Executable set to inkscape (which can be found in src/inkscape after a successful compile).

I would be happy to commit this, although I'm completely new to bzr, much more familiar with git.

I shall commit a branch within the week containing the xcode project that I made. Is it ok to place it in the packaging/macosx folder?

On 2013-03-25 09:41 +0100, Alek Slater wrote:
> I shall commit a branch within the week containing the xcode project
> that I made. Is it ok to place it in the packaging/macosx folder?

Should be ok, just keep it separate from existing files/sub-directories.

JFYI: I'll be off-line for the next two weeks (possibly checking for
emails, but not on a daily basis).

Cheers,
~suv

understood, and thx for yer help! :D

Struggled a lot with bzr, even with the guide at http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar
:(

Anyway I think finally I got a branch going:
https://code.launchpad.net/~slayte/inkscape/slayte

PS: Bzr sucks

On 2013-03-27 04:11 +0100, Alek Slater wrote:
> Anyway I think finally I got a branch going:
> https://code.launchpad.net/~slayte/inkscape/slayte

Great :) thx a lot!

Quick question: do you know why it requires to have the 'Mobile Device
Framework' («provides device connectivity necessary for iOS
development») installed [*]? Any chance you could reduce the project
file to the bare minimum needed to compile the inkscape binary itself?

-----
[*] I only just checked out the branch, and wanted to launch the Xcode
project (using Xcode 4.3.2 on Lion), and didn't have time yet to further
investigate how to work around this (I have no need for iOS devel
files/frameworks, and right now I can't imagine Inkscape requires
anything related to iOS either).

I can't see any reference to anything called "Mobile Device Framework', so I think this might be related to your old version of Xcode.

I'm using
Version 4.6.1 (4H512)
On Mountain Lion

Did you try to build the InkscapeApp project , or the Inkscape project?
InkscapeApp is just a placeholder, no where near completion and it doesn't reference anything with inkscape yet.

Inkscape is the project that uses the make build system, pretty much the same as the command line, except you also get easier debugging etc ;D

Let me know if you still have issues, but for the record, I doubt the XCode Projects I made are backwards compatible with 4.3.2.

>>Quick question: do you know why it requires to have the 'Mobile Device
Framework' («provides device connectivity necessary for iOS
development») installed [*]? Any chance you could reduce the project
file to the bare minimum needed to compile the inkscape binary itself?

If you are trying to build the InkscapeApp, it might be the Project's Base SDK settings.
Its set to Latest OS X on mine, but I remember older XCode versions didn't have this,
so it might be set as one of the iOS SDKs on your XCode.

Would be interesting to see if you change that to Current OS X (assuming thats visible), that it then builds for you?