Inkscape Wiki - User contributions [en]

Tracking Dependencies

2020-07-30T12:33:10Z

LinkMauve: Remove EOL’d Ubuntu 19.10, unsupported since the 17th of July.

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.92
! v 1.0
! master
|-
| Boehm-GC
| 7.2
| 7.2
|
|-
| Cairo
| 1.14
| 1.14 (1.15.4 required for PDF links)
| 1.16*
|-
| double-conversion [https://github.com/google/double-conversion] ''(lib2geom dependency)''
| ''(not required)''
| any
|
|-
| GDL
| N/A (3.4)
| 3.4
| 3.6
|-
| Glib
| 2.28
| 2.48
| 2.56 or 2.62*
|-
| GTK+
| 2.24 (3.8)
| 3.22
| 3.24*
|-
| GNU Scientific Library
| ?
| ?
|
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| 2.10*
|-
| libSoup
| ''(not required)''
| (any)
|
|-
| libpotrace
| ''(not required)''
| (any)
|
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
|
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
|-
| LittleCMS
| 1.13
| 1.13
|
|-
| Pango
| 1.24
| 1.24 (1.41.1 required for variable fonts)
| 1.42*
|-
| Poppler
| 0.20.0
| 0.20.0
| 0.71*
|-
| [https://formulae.brew.sh/formula/gtk-mac-integration gtk-mac-integration] [https://www.macports.org/ports.php?by=library&substr=gtk-osx-application-gtk3 gtk-osx-application-gtk3]
| N/A
| 2.0.8 ([[CompilingMacOsX|macOS only]])
|
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

'''General rules:'''
* Support last Debian Stable
* Support last Ubuntu LTS
* Support last CentOS/Redhat (as best effort).
* Support last two Fedora releases.
* Don't break ''point'' releases.

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms2
! libsigc++
! libgc 
! libsoup
|-
| Windows MSYS2 (2018-11-08) ([https://github.com/Alexpux/MINGW-packages mingw-w64 packages] from MSYS2 project)

| -
| 8.2.0
| <abbr title="compiles but fails to link due to long path issue (help welcome)">(7.0.0)</abbr>
| 1.16.0
| 1.12.2
| 2.58.1
| 2.58.0
| 2.24.32 3.24.1
| 2.24.5 3.22.3
| 1.42.4
| 0.69.0
| 3.28.0
| 1.19 2.9
| 2.10.1
| 7.6.8
| 2.64.2
|-
| Debian 10 (Buster, stable) EOL 2024-06
| 0.92.4
| 8.3.0
| 7.0
| 1.16
| 1.12.2
| 2.58.3
| 2.58.0
| 2.24.32 3.24.5
| 2.24.5 3.24.0
| 1.42.4
| 0.71.0
| 3.28.0
| 2.9
| 2.10.1
| 7.6.4
| 2.64.2
|-
| style="background:Violet;"|(RHEL) / CentOS 8.1 EOFS 2024-05 Based on Centros 8.1 package list
| 0.92.3
| 8.3.1
| 8.0.1
| 1.15.12
| 1.12.0
| 2.56.4
| 2.56.0
| 2.24.32 3.22.30
| 2.24.5 3.22.2
| 1.42.4
| 0.66.0
| style="background:Violet;"|?
| 2.9
| 2.10.0
| 7.6.4
| 2.62.3
|-
| Ubuntu 18.04 LTS (Bionic) EOL 2023-04
| 0.92.3
| 7.3
| 6.0
| 1.15.10
| 1.12.2
| 2.56.1
| 2.56.0
| 2.24.32 3.22.30
| 2.24.5 3.22.2
| 1.40.14
| 0.62.0
| 3.28.0
| 2.9
| 2.10.0
| 7.4.2
| 2.62.1
|-
| Ubuntu 20.04 LTS (Focal Fossa) EOL 2025-04
| 0.92.5
| 10
| 10
| 1.16
| 1.12.2
| 2.64.1
| 2.64.2
| 2.24.32 3.24.17
| 2.24.5 3.24.2
| 1.44.7
| 0.86.1
| 3.34.0
| 2.9.4
| 2.10.2
| 10
| 2.70.0
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Orange;"| Inkscape 1.0.x unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

* Agreed to at Saarbrücken hackfest.

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Website: http://www.hboehm.info/gc/

GitHub Project: https://github.com/ivmai/bdwgc

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

== Optional Dependencies ==

Inkscape will still compile without these, but some features may be missing if they are absent during compilation:

{| class="wikitable"
|-
! scope="col"| Library
! scope="col"| Needed for
! scope="col"| Default
|-
|aspell
|Dictionaries for spell checking
|On
|-
|libcdr
|Open Corel Draw files
|On
|-
|gettext/msgformat
|Translation support
|On
|-
|gtest/gmock
|Automatted testing
|Off
|-
|gspell
|Spell checking
|On
|-
|imagemagick
|Bitmap editing extensions, bitmap import resolution
|On
|-
|jpeg
|jpeg import?
|On
|-
|lcms
|Color management
|On
|-
|OpenMP
|Multi-threaded filter rendering
|On
|-
|scour
|Save as Optimized SVG
|(not needed during compiling, Python)
|-
|libvisio
|Open Visio Files, use Visio stencils
|On
|-
|libwpg
|Open WordPerfect Graphics
|On
|-
|}

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Roadmap

2020-06-26T19:13:58Z

LinkMauve: /* 2Geom 1.0 */ Mark tasks as done.

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.92 ~ Infrastructure Focus ===
* (DONE) <s>Set up autogeneration of Inkscape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
** (DONE) <s>Put it publicly somewhere on the inkscape domain for "official" access.</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
* (DONE) <s>Build system: migrate away from Autotools (See [[Build system improvements]])</s>
** (DONE) <s>Decide between CMake and Waf</s>
*** (DONE) <s>Alex will be doing a "neutral party" review of the two</s> Decision to go with cmake for now.
** (DONE) <s>Get decided system working</s>
*** See [[CMake_Tasks]]
** (DONE) <s>Switch release tools to use new build system</s> Documented for now; will wait on mechanizing it until after switch to git.
** (DONE) <s>Switch packaging tools to use new build system</s>
** (DONE) <s>Retain Autotools support one final release (legacy support)</s>, then drop next release.
* (DONE) <s>Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)</s>

=== 2Geom 1.0 ===
* 2geom maintenance
** (DONE) <s>Stop embedding 2Geom in Inkscape's codebase; handle it as a regular dependency</s> (https://gitlab.com/inkscape/inkscape/-/merge_requests/2109)
** (DONE) <s>Move project to gitlab, from https://launchpad.net/lib2geom, http://lib2geom.sourceforge.net/, and https://github.com/inkscape/lib2geom [kk]</s> (https://gitlab.com/inkscape/lib2geom)
** Possibly start doing lib2geom releases in conjunction with Inkscape's releases? [bryce]
** Add to PPAs and other CI / autobuilds we already use for Inkscape [alex + bryce]

=== Inkscape 1.0alpha ~ Maintenance and Optimization Focus ===
* (DONE) <s>Migration to Git</s>
* (DONE) <s>Migration to GitLab</s>
* (DONE) <s>Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion July 2013 didn't get much traction])</s>
** Hackfest consensus is Google test.
* (DONE) <s>Set up continuous builds (e.g. Travis CI / Appveyor or gitlab)</s>
* (DONE) <s>Make C++11 compiler a hard requirement</s>
* (DONE) <s>Drop Autotools support (See [[Build system improvements]])</s>
* (DONE) <s>Migrate potrace to be an external dependency</s> Done for 0.92
* (DONE) <s>Gtk3/UI revamp</s> Down to bug fixing and follow-on work

* Split out less well maintained extensions to an 'extras' package
** Add a test suite that runs each extension against a collection of test documents
** Possibly start doing inkscape-extras releases in conjunction with Inkscape's releases?
** If we don't achieve this by this release, push it to 1.1 or later
* Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
** Need to investigate where we stand with this, and re-evaluate more precisely what we want to do this release
* Prepatory work for expanded testing
** Document how to do the tests
** Create or identify a good model test case
** Implement example unit tests for: SP objects, verbs, cmdline options, live effects, UI dialogs, UI widgets/tools, UI view, etc.
** Start collecting regression svg files in a testing repository somewhere
* Thorough testing of document recovery after crash. Make this more robust.
** Need to better define what we want to test
** How should the crash be triggered?
** What should the document be?
** Need to be careful about what cases we actually want to consider
* Improved performance
** with an empty start
** when starting up with an existing file
** peppering printfs in the startup logic shows that some routines that should get called one time only, actually get called multiple times
** need to investigate if there is existing instrumentation tools that could be used to identify recursion or other causes of slowness during startup
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.
** Consider also bringing lib2geom mailing lists?
** inkscape: We need postmaster@inkscape.org and abuse@inkscape.org set up. Maybe as part of a mailing list refresh?
* Set up effort to package selected branches and organize community testing around them
** Use this initially for changes planned for landing in 1.0
** Once we're feature-frozen for 1.0, use this mechanism for wider testing of new feature work
* Gtk+ 3 migration: Goal is a clean, deprecation-free build
** Stop using GtkActions. Migrate toolbars to use plain widgets, and GAction
** Turn Inkscape into a proper Gtk::Application. Stop using Gtk::Main
** GtkMM/C++ify and clean up toolbar code
** Remove unused GtkAction-based widgets

=== Inkscape 1.0beta ~ Test Case and Documentation Writing Focus ===
* Write unit test cases
** Core functions
* Better translations - keep track of % translations for all languages. Drive to 95% on all major languages.
* Cleanup website and wiki
** Move pages of value to users from wiki to the main website
** Trim down amount of legacy material presented in the wiki
* Coder stories
** different stories about how to do common development tasks, like hooking in a new widget or adding support of a new SVG tag
** have people sketch in what they know, then pass around for critique to optimize the description
** where to store the documentation? Where would someone look?

=== Inkscape 1.0 ===
* Strict bugfix focus, with all development targeted to feature branches
* This will be a long term stable release series

-----------------------------------
'''Following is a WIP draft of the post-1.0 release goals; this is not yet finalized, and should not be taken as official yet'''
-----------------------------------

=== Inkscape 1.1 ~ New Features ===
* Land feature branches held for post-1.0
* SVG Flowed Text
** Fix flowtext
** Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
** Ex. https://dl.dropboxusercontent.com/u/65084033/irc/ask-smart-questions.svg
* Externalize some (easy) dependencies for better modularization
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Switch to using libcroco as a regular dependency (not embedded in our codebase).
*** Contact maintainer to see if still actively maintaining, and if can roll a new release for us
*** Else, consider adopting maintenance of the library under the Inkscape project umbrella
*** Or consider replacement with libcss or other CSS parser.
*** See http://inkscape.13.x6.nabble.com/Should-inkscape-take-over-libcroco-td2784457.html
** Switch to using Adaptagrams (libvpsc, libcola & libavoid) as a regular dependency
*** Contact maintainer to see if still actively maintaining, and if can roll a new release for us
*** Else, consider adopting maintenance of the library under the Inkscape project umbrella
*** See https://bugs.launchpad.net/inkscape/+bug/1353833
* Complete conversion to GTK 3
** Drop use of libgdl in place of GtkNotebook
** Be smarter about toolbar layout so we never have invisible (but necessary) buttons off the screen.
** Rework panels so that they resize consistently and display contents better. Consider moving back to dialogs in some cases or moving more functionality to the canvas.
* Begin development of new plugin / extension system(s)
** C++ API with Python bindings
** Review the D-Bus scripting API GSoC work from 0.48 timeframe
** Easy to create
** Powerful enough to do LPEs, filters, etc.
** Probably need several different APIs for different levels in the codebase, such as atop the object model, one for canvas stuff, one atop the UI, etc.
*** For object layer will require better division from UI, so it doesn't require a selection for items to operate on
** Include a debug print of the loaded extensions/plugins/etc.
** Establish an Extensions Center for community-collaborative sharing/reviewing/maintaining extensions
*** Core extensions are shipped with Inkscape
*** User review ranking
*** Developer review ranking
*** Auto-QC ranking (mechanical testing, and checking for docs, test cases, etc.)
** Search the Extensions Center and install from within Inkscape
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
* [[GtkMMification]]
* Improved performance
** Working with large files
** Working with files with lots of filters
* Consider setting up workflow (passing tests, test coverage, code review) for getting code into trunk.
** Improve new contributor experience for getting patch reviews
** Switch patch review software from launchpad to something like mailing list + patchwork, or phabricator
* make msi Windows install multilingual
* Implement application-scope actions and "remixable" user interfaces:
** Replace "Verbs" with application-scope Gio::Action definitions.
** Define user-interface using Gtk::Builder XML files.
** Provide command-line "headless" access to application actions.
** Provide documentation for all actions, and tutorial for GUI customization

=== Inkscape 1.2 ~ Refactoring ===
* Split backend / GUI frontend
* Flip y-coordinate to match SVG.
** Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.

[[Category:Developer Documentation]]

Release notes/1.1

2020-05-05T14:37:00Z

LinkMauve: /* Important changes */ Add a mention about aspell too.

{{Other languages | en = {{FULLPAGENAME}}}}

== Release highlights ==

'''Definitely not released yet.'''

Inkscape 1.1 is a stability and bugfix release.

[For changes made even before the 1.0 release that aren't in 1.0, try to find out if the checked and not stroked ones here: https://gitlab.com/inkscape/inkscape/-/issues/1030 have really not been cherrypicked]

The most notable improvements are:

* Fill in

== Important changes ==

* For packagers: we do not depend on GtkSpell and ASpell but on GSpell for spelling checks.

== Improvements ==

* In Edit > Preferences > Imported images : Import, there is a new option that allows you to disable relative paths to linked files ("Store absolute file path for linked images", active by default).
* [https://en.wikipedia.org/wiki/XInclude XInclude] support
* Hidden dialogs stop receiving signals and release resources
* Shell mode: a history of commands is now remembered and can be accessed with the up and down arrow keys. [Tab ... autocompletion?]



== Notable bugfixes ==

* Fill in

== Crash fixes ==

Fix a crash …
* … when ... ([https://gitlab.com/inkscape/inkscape/issues/ #number])

== More bug fixes ==

There were even more issues fixed than those listed above, but these probably only affect a small portion of users, or are relevant for development and packaging only.

For a complete list, visit [https://gitlab.com/inkscape/inkscape/milestones/2 our GitLab issue tracker] and see the [https://gitlab.com/inkscape/inkscape/commits/1.0.x commit history] (all changes since DATE until release date).

== Translations ==

The following UI translations received updates:

* Language

The following documentation translations received updates:

* Language

=== Contributing to interface translations ===

Want to help with translations? [https://inkscape.org/contribute/translations/ Learn how to help!]

== Documentation ==

* Some missing options were added to the man page (command line help)
* Some missing keyboard shortcuts were added to the keyboard shortcut reference

=== Contributing to documentation and documentation translation ===
Contributions to the documentation translations, as well as improvements to its contents, are welcome at [https://gitlab.com/inkscape/inkscape-docs/documentation the inkscape-docs repository].

== Known issues ==

* Fill in
* Many of Inkscape's old bug reports still need to be [https://alpha.inkscape.org/bug-migration/ tested and migrated to the new bug and feature request reporting page]. While some progress has already been made, we still need your help with that task.
* All (migrated and new) open issues for the project are listed on [https://gitlab.com/groups/inkscape/-/issues GitLab]. If you have some time on your hands and can help fixing them, [https://chat.inkscape.org/channel/team_devel join us in the development chat] and let us tackle them together.

== Previous releases ==
* [[Release notes/0.92]]
* [[Release notes/0.92.1]]
* [[Release notes/0.92.2]]
* [[Release notes/0.92.3]]
* [[Release notes/0.92.4]]
* [[Release notes/0.92.5]]
* [[Release notes/1.0]]

C++17

2020-04-14T09:57:56Z

LinkMauve: Add move semantics

== Usage status ==
This table lists C++14 and C++17 features and whether they can be used in Inkscape or not (yet).
Add C++14 or C++17 features that you would like to use to the table, so that we know what to test for to increase the C++17 "allowance".

{| class="wikitable"
|-
! Feature !! Since !! Can use? !! Comment
|-
| <code>std::move</code> and rvalues || C++11 || style="background: lightgreen;" | from 1.0 || Allows passing ownership of internal resources between objects
|-
| <code>enum class</code> || C++11 || style="background: lightgreen;" | from 1.1 || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
|-
| <code>std::make_unique<Foo>(…)</code> || C++14 || style="background: lightgreen;" | from 1.1 || Replaces <code>std::unique_ptr<Foo>(new Foo(…))</code>
|-
| <code>constexpr</code> || C++14 || style="background: lightgreen;" | from 1.1 || Declares a variable as usable in a const expression
|-
| <code>if constexpr</code> || C++17 || style="background: lightgreen;" | from 1.1 || Guarantees the branches will be decided at compile-time
|-
| <code>std::variant<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Type-safe union, where the contained type is known at runtime
|-
| <code>std::optional<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Object type (not a pointer or reference) which can either exist or be <code>std::nullopt</code>
|-
| <code>auto [x, y] = foo();</code> || C++17 || style="background: lightgreen;" | from 1.1 || Structured binding, for returning more than a single value
|-
| <code>namespace A::B::C</code> || C++17 || style="background: lightgreen;" | from 1.1 || Nested namespaces
|-
| <code>inline static const int</code> || C++17 || style="background: lightgreen;" | from 1.1 || Inline variables (inside header files)
|-
| <code>std::filesystem<code> || C++17 || not yet || Filesystem library (may not be useful as we are using Gio::File). Also only supported from gcc 8, and Ubuntu 18.04 only has gcc 7.
|-
| toxic feature of doom || || style="background: red;" | NO || Never use this (in case we stumble upon C++14/C++17 features that we really don't like)
|}

== Platform status ==

We need to keep coordinated with the section on [[Tracking_Dependencies#Distros|Distro Dependencies]].

Also see this page:
* http://en.cppreference.com/w/cpp/compiler_support

Note that <code>__cplusplus</code> is always <code>1</code> for GCC 4.6 that is used on Windows. So <code>#if __cplusplus < 201103L</code> or variants does not work to choose between C++03 or C++11 code.

C++17 is well supported by all major compilers.

Compiler version when feature complete:

{| class="wikitable"
|-
! !! GCC !! Clang !! MSVC
|-
|C++17 || 7 (2017) || 4 (2017) (5 for constexpr lambda expressions) || 19.14 (2017)
|-
|C++20 || 10* || 10* || 19.22#
|}
'*' Mostly complete
'#' About half complete

C++17

2020-04-14T09:56:24Z

LinkMauve: Make std::filesystem not yet.

== Usage status ==
This table lists C++14 and C++17 features and whether they can be used in Inkscape or not (yet).
Add C++14 or C++17 features that you would like to use to the table, so that we know what to test for to increase the C++17 "allowance".

{| class="wikitable"
|-
! Feature !! Since !! Can use? !! Comment
|-
| <code>enum class</code> || C++11 || style="background: lightgreen;" | from 1.1 || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
|-
| <code>std::make_unique<Foo>(…)</code> || C++14 || style="background: lightgreen;" | from 1.1 || Replaces <code>std::unique_ptr<Foo>(new Foo(…))</code>
|-
| <code>constexpr</code> || C++14 || style="background: lightgreen;" | from 1.1 || Declares a variable as usable in a const expression
|-
| <code>if constexpr</code> || C++17 || style="background: lightgreen;" | from 1.1 || Guarantees the branches will be decided at compile-time
|-
| <code>std::variant<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Type-safe union, where the contained type is known at runtime
|-
| <code>std::optional<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Object type (not a pointer or reference) which can either exist or be <code>std::nullopt</code>
|-
| <code>auto [x, y] = foo();</code> || C++17 || style="background: lightgreen;" | from 1.1 || Structured binding, for returning more than a single value
|-
| <code>namespace A::B::C</code> || C++17 || style="background: lightgreen;" | from 1.1 || Nested namespaces
|-
| <code>inline static const int</code> || C++17 || style="background: lightgreen;" | from 1.1 || Inline variables (inside header files)
|-
| <code>std::filesystem<code> || C++17 || not yet || Filesystem library (may not be useful as we are using Gio::File). Also only supported from gcc 8, and Ubuntu 18.04 only has gcc 7.
|-
| toxic feature of doom || || style="background: red;" | NO || Never use this (in case we stumble upon C++14/C++17 features that we really don't like)
|}

== Platform status ==

We need to keep coordinated with the section on [[Tracking_Dependencies#Distros|Distro Dependencies]].

Also see this page:
* http://en.cppreference.com/w/cpp/compiler_support

Note that <code>__cplusplus</code> is always <code>1</code> for GCC 4.6 that is used on Windows. So <code>#if __cplusplus < 201103L</code> or variants does not work to choose between C++03 or C++11 code.

C++17 is well supported by all major compilers.

Compiler version when feature complete:

{| class="wikitable"
|-
! !! GCC !! Clang !! MSVC
|-
|C++17 || 7 (2017) || 4 (2017) (5 for constexpr lambda expressions) || 19.14 (2017)
|-
|C++20 || 10* || 10* || 19.22#
|}
'*' Mostly complete
'#' About half complete

C++17

2020-04-13T11:23:05Z

LinkMauve: Add enum class

== Usage status ==
This table lists C++14 and C++17 features and whether they can be used in Inkscape or not (yet).
Add C++14 or C++17 features that you would like to use to the table, so that we know what to test for to increase the C++17 "allowance".

{| class="wikitable"
|-
! Feature !! Since !! Can use? !! Comment
|-
| <code>enum class</code> || C++11 || style="background: lightgreen;" | from 1.1 || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
|-
| <code>std::make_unique<Foo>(…)</code> || C++14 || style="background: lightgreen;" | from 1.1 || Replaces <code>std::unique_ptr<Foo>(new Foo(…))</code>
|-
| <code>constexpr</code> || C++14 || style="background: lightgreen;" | from 1.1 || Declares a variable as usable in a const expression
|-
| <code>if constexpr</code> || C++17 || style="background: lightgreen;" | from 1.1 || Guarantees the branches will be decided at compile-time
|-
| <code>std::variant<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Type-safe union, where the contained type is known at runtime
|-
| <code>std::optional<…></code> || C++17 || style="background: lightgreen;" | from 1.1 || Object type (not a pointer or reference) which can either exist or be <code>std::nullopt</code>
|-
| <code>auto [x, y] = foo();</code> || C++17 || style="background: lightgreen;" | from 1.1 || Structured binding, for returning more than a single value
|-
| toxic feature of doom || || style="background: red;" | NO || Never use this (in case we stumble upon C++14/C++17 features that we really don't like)
|}

== Platform status ==

We need to keep coordinated with the section on [[Tracking_Dependencies#Distros|Distro Dependencies]].

Also see this page:
* http://en.cppreference.com/w/cpp/compiler_support

Note that <code>__cplusplus</code> is always <code>1</code> for GCC 4.6 that is used on Windows. So <code>#if __cplusplus < 201103L</code> or variants does not work to choose between C++03 or C++11 code.

C++17 is well supported by all major compilers.

Compiler version when feature complete:

{| class="wikitable"
|-
! !! GCC !! Clang !! MSVC
|-
|C++17 || 7 (2017) || 4 (2017) (5 for constexpr lambda expressions) || 19.14 (2017)
|-
|C++20 || 10* || 10* || 19.22#
|}
'*' Mostly complete
'#' About half complete

C++17

2020-04-13T11:18:50Z

LinkMauve: Add structured binding

C++17

2020-04-13T11:17:04Z

LinkMauve: Add std::variant and std::optional

C++17

2020-04-13T11:04:11Z

LinkMauve: Copy the C++11 page and update for C++17 to be the baseline.