[MacPorts] #56806: inkscape-devel : use CMake (and a few other improvements)
MacPorts
noreply at macports.org
Fri Jul 13 19:00:55 UTC 2018
#56806: inkscape-devel : use CMake (and a few other improvements)
-------------------------+----------------------------
Reporter: RJVB | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: haspatch | Port: inkscape-devel
-------------------------+----------------------------
Building Inkscape on Linux I noticed that it now uses CMake and preserves
the autoconf-based build only for "just in case".
The use of cmake has a few advantages:
- faster configure (no more autoreconf)
- faster build when using Ninja
- easier maintainability because of an out-of-source build directory
The attached patch converts the port to use cmake for building and as far
as I can tell it indeed makes the build faster and less resource-hungry
(thanks to using Ninja instead of make).
The only user-visible effect of this change is the loss of the +strict
variant which hasn't been ported to cmake. It was never entirely clear to
me what interest this variant had and apparently the Inkscape team wasn't
too convinced about this option either.
A few other (strongly) suggested improvements:
- use `git describe` instead of the date of the last commit (which isn't
guaranteed to be unique, nor even monotonically increasing )
- declare explicit dependencies on libomp and glibmm which I think were
missing
- define the +gtk3 variant so it can actually be used
And a maintainer convenience tweak I use all the time:
- make `worksrcdir` unversioned; I'm guessing the port maintainer doesn't
clone the entire 1.5Gb or so each time he builds a new version so why not
make it easy to reuse the source directory.
--
Ticket URL: <https://trac.macports.org/ticket/56806>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list