I'm not on mac, so I can't help much beyond that, but a good start is probably the CI script we already have, see https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L43-74 which seems to compile nicely.

It's for master, so in order to compile for 0.92.x one would have to exchange some of the gtk3 dependecies with their gtk2 counterparts, but otherwise it might proove useful.

Regards, Patrick

Am 05.08.2018 um 09:36 schrieb Andrea Bogazzi:

I m a macos developer too and if we can find a definitve solution to have packages for macos, available as fast as windows/linux i would be happy to put my time on it

On Sun, 5 Aug 2018, 09:34 Shlomi Fish, <shlomif@...2985... mailto:shlomif@...2985...> wrote:

Hi Eric,

On Sat, 4 Aug 2018 15:53:11 -0400
Eric Roch <eric@...3668... <mailto:eric@...3668...>> wrote:

> Hello,
>
> I am trying to compile the 0.92.3 release from source on my Mac,
but I’m not
> really sure how to continue when I see errors.  The wiki page is
way out of
> date, and the Readme doesn’t have much detail.
>

Which errors are you getting? You can try using https://brew.sh/
or similar to
resolve dependencies. Make sure you are using cmake.

> Could anyone assist me with compiling from source?  If I can get
this
> working, I would also like to help get a DMG published, but I
don’t know how.
>
> I apologize if this is not the right place to post this. If not,
where
> should I go?
>
> Thanks,
> Eric



-- 
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
http://ccmixter.org/files/destinazione_altrove/49997 - “Paint The Sky”

http://en.wikipedia.org/wiki/Evil redirects to XSLT.
    — http://www.shlomifish.org/humour/bits/facts/XSLT/

Please reply to list if it's a mailing list post -
http://shlom.in/reply .

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
<mailto:Inkscape-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

---

Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

---

Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Am 17.08.2018 um 17:07 schrieb Dwain Alford:

hello, i am not a programmer. i use inkscape on mac sierra. i use the following build. this seems to be the answer for mac as this version seems to star quicker than the "official" build and since there is no one other than this lone developer attempting the feat of incorporating quartz rather than using it as a third party install. since you folks are wanting to help out with the development and compilation of inkscape for mac, why not try this build (gotta uninstall quartz though) and contact the developer and move on this version for mac. you might find this version of inkscape to your liking.

https://github.com/valerioa/Inkscape-MacOS-Curated-Build/releases

sure would like to see this version become the norm for mac; and maybe you folks might be able to bring 0.92.3 to the forefront.

hth, dwain

We contacted the developer, see https://github.com/valerioa/Inkscape-MacOS-Curated-Build/issues/14

Unfortunately they don't seem to be active anymore. If anybody has some development experience on Mac and wants to start from there / rebase the changes I'm sure we can work towards incorporating them into the codebase.

Regards, Patrick

For reference: https://github.com/valerioa/Inkscape-MacOS-Curated-Build/compare/beb53bb4b65... (hopefully full list of changes of this fork)

https://github.com/valerioa/Inkscape-MacOS-Curated-Build/commit/beb53bb4b652... is the first commit with unmodified Inkscape code, isn't it?

Am 17.08.2018 um 17:52 schrieb doctormo@...400...:

1. Most of the modifications are forks of Gtk and some other libraries

which are bundled into the distribution. For example to get the menu in the top bar has a patch against Gtk2.

Am I missing something? There only seems to be one patch against gtk2 (https://github.com/valerioa/Inkscape-MacOS-Curated-Build/tree/master/valerio...) which is related to copy & pasting / the cliboard.

2. The modifications are related to Gtk2, a new rebase would and

/should/ start from scratch. Simple because Gtk3 is going to be very different. So both the Gtk fork and the mods to Inkscape need to be re- done. Although I recommend using the ideas from this branch.

That's obviously true, but if there are not more changes I overlooked it shouldn't require too much effort. For gtk3 it's also much easier to upstream patches as there is active development and frequent releases (so there's a good chance to get patches accepted before the first release of an Inkscape version that actually depends on gtk3).

3. Modifications were specific to the mac build. There's some

modifications that we could take so long as we had good ifdefs for a Mac build. Things like folder locations and some other bits and bobs.

Most of the code seems properly ifdef'd already (WITH_CARBON_INTEGRATION).

The rest are changes to the build system and packaging. I guess getting all of this right is likely the largest piece of work, especially as everything is still based on the autotools buiöld (i.e. needs to be ported to CMake for master).

Overall I'm very impressed by the curated build, but I also understand exactly why this wasn't merged in. I'd probably support a new fork of Inkscape to replicate this work if it means getting a MacOSX release as high quality as this one for 1.0.

Well, the fork seems to be the result of the author trying to get the changes upstreamed but not succeeding, see Readme.md of the repository. I wasn't around back then, so I'm not sure if there was any serious effort. Either way the end result is now one outdated and likely dead fork, so I have a feeling actually incorporating the changes into the official repository might be a more solid foundation for future Mac releases (even if it might be a bit more work initially).