Dear All,
I have completed the migration of Inkscape trunk to use CMake as its build system. This is already the preferred option for the 0.92.x release, and the PPA build has been using CMake successfully for the last couple of months.
You will still be able to use Autotools or btool builds as a fallback option for the forthcoming stable Inkscape 0.92.x releases (lp:inkscape/0.92.x) but you will need to use CMake for the latest trunk builds (lp:inkscape), and for all future stable releases (0.93 onwards).
This is part of a long-running plan to improve our build system, and will be much easier to maintain, and offer much better cross-platform support than our previous solutions.
This represents a change in workflow for many developers and maintainers, so please accept our apologies for any inconvenience. We will very gratefully receive any bug reports, or answer any queries about this transition and use them to improve the package.
Best wishes,
Alex
On Mon, 2016-08-08 at 14:27 +0100, Alex Valavanis wrote:
Dear All,
I have completed the migration of Inkscape trunk to use CMake as its build system. This is already the preferred option for the 0.92.x release, and the PPA build has been using CMake successfully for the last couple of months.
You will still be able to use Autotools or btool builds as a fallback option for the forthcoming stable Inkscape 0.92.x releases (lp:inkscape/0.92.x) but you will need to use CMake for the latest trunk builds (lp:inkscape), and for all future stable releases (0.93 onwards).
This is part of a long-running plan to improve our build system, and will be much easier to maintain, and offer much better cross-platform support than our previous solutions.
This represents a change in workflow for many developers and maintainers, so please accept our apologies for any inconvenience. We will very gratefully receive any bug reports, or answer any queries about this transition and use them to improve the package.
Excellent news!
Here's some info on how to do a CMake build:
http://wiki.inkscape.org/wiki/index.php/CMake
Note that trunk also requires Gtk3 and C++11.
Tav
On Mon, Aug 08, 2016 at 02:27:58PM +0100, Alex Valavanis wrote:
Dear All,
I have completed the migration of Inkscape trunk to use CMake as its build system. This is already the preferred option for the 0.92.x release, and the PPA build has been using CMake successfully for the last couple of months.
You will still be able to use Autotools or btool builds as a fallback option for the forthcoming stable Inkscape 0.92.x releases (lp:inkscape/0.92.x) but you will need to use CMake for the latest trunk builds (lp:inkscape), and for all future stable releases (0.93 onwards).
This is part of a long-running plan to improve our build system, and will be much easier to maintain, and offer much better cross-platform support than our previous solutions.
This represents a change in workflow for many developers and maintainers, so please accept our apologies for any inconvenience. We will very gratefully receive any bug reports, or answer any queries about this transition and use them to improve the package.
Best wishes,
Alex
Thanks Alex!
Bryce
Hi Alex,
Alex Valavanis <valavanisalex@...400...> a écrit :
We will very gratefully receive any bug reports, or answer any queries about this transition and use them to improve the package.
Thanks Alex!
Just tried with a new Inkscape checkout on Xubuntu 16.04 using the steps explained in the wiki. Cmake and make work as expected, but when I launch the application, it seems all the /usr/share/ content is ignored (icons, colors, external extensions and templates are missing). The console shows the following messages: ---- ** (process:19600): WARNING **: Units file /share/inkscape/ui/units.xml is missing: Failed to open file '/share/inkscape/ui/units.xml': No such file or directory
** (inkscape:19600): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-AigQBb9OF3: Connexion refusée sp_main_gui: Cannot find default style file: (/share/inkscape/ui/style.css)
** (inkscape:19600): WARNING **: Unable to open PowerPoint fontfix file: /share/inkscape/extensions/fontfix.conf PowerPoint ungrouping compensation in WMF/EMF export will not be available.
** (inkscape:19600): WARNING **: Can't open file: /share/inkscape/keys/default.xml (doesn't exist)
** (inkscape:19600): WARNING **: Unable to read keys file /share/inkscape/keys/default.xml Unable to find: org.inkscape.help.manual Unable to find: org.inkscape.help.keys Unable to find: org.inkscape.help.askaquestion Unable to find: org.inkscape.help.commandline Unable to find: org.inkscape.help.faq Unable to find: org.inkscape.help.relnotes Unable to find: org.inkscape.help.reportabug Unable to find: org.inkscape.help.svgspec
** (inkscape:19600): WARNING **: Null pixbuf for 0x1693e10 [/share/inkscape/icons/remove-color.png] ----
Again, it's with a new checkout and no change in the default cmake options.
Thanks for your help! -- Nicolas
Tried again with the latest revision, and this time it worked. I don't know what failed the first time, but consider it fixed. Regards, -- Nicolas
That's good to know. Let's keep an ear open for anyone else with similar issues though.
AV
On 9 Aug 2016 12:55 p.m., "Nicolas Dufour" <nicoduf@...48...> wrote:
Tried again with the latest revision, and this time it worked. I don't know what failed the first time, but consider it fixed. Regards, -- Nicolas
Am 08.08.2016 um 16:02 schrieb Tavmjong Bah:
Here's some info on how to do a CMake build:
Could somebody with CMake experience add some information (e.g. in the article mentioned above) on how to properly do things like
* Create the distribution directory * Build from scratch (i.e. "make clean") * Build without re-compiling unchanged files * Re-build after cmake files have changed (preferably without re-compiling unchanged files)
Also debugging techniques when using CMake would be welcome (e.g. how do I re-build in the shortest time possible when I'm only changing one single source file?).
Basically CMake builds have worked for me on Windows once after checking out the Bazaar repository but not a second time after that. So far I mostly found myself resetting the repository after one CMake build to start fresh after that... It seems to be a lot less straightforward then autotools-based builds or btool builds.
Regards, Eduard
participants (5)
-
Alex Valavanis -
Bryce Harrington -
Eduard Braun -
Nicolas Dufour -
Tavmjong Bah