Inkscape Wiki - User contributions [en]

Template:Deleted

2023-03-13T14:51:38Z

Speleo3: nicer look

<div style="margin: 0 auto 1em; padding: 1.6em; width: 80%; border: 4px solid red; background: #FFCCCC; text-align: center;">
'''This page has been deleted'''

''This page is kept for historical reasons, e.g. to document specific decisions in Inkscape development.''
</div><includeonly>[[Category:Wiki Attic]]</includeonly><noinclude>
Usage: <pre>{{Deleted}}</pre>

[[Category:Wiki templates]]
</noinclude>

Hackfest2023 Bensberg

2023-02-21T21:00:12Z

Speleo3: Added speleo3 arrival+departure

[[File:Hackfest bensberg sticker.png|left|thumb|150x150px]]
This page '''<big>IS WORK IN PROGRESS</big>''' and details the planning of Inkscape's 2023 hackfest in Bensberg, Germany. The hackfest will take place on '''March 13-17, 2023'''. We are looking to bring together a group of '''10 attendees'''. <s>but do not let that number discourage you from throwing your hat in the ring in case we reach/go over it.</s> We are fully booked and the number of participants is final now.

This hackfest is a standalone event and not organized around any other event or FOSS conference.

Previous events: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 SCALE]], [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].
[[Category:Hackfest]]

=Description=
It's a hackfest! We will work on Inkscape bugs, new features, packaging, website issues, ... in fact anything that can benefit from us being physically in the same space. And let's not forget about the social component - we get to hang and talk and laugh in person since we usually only meet virtually :).
==Bensberg==
Bensberg is part of Bergisch Gladbach, a city in the western part of Germany, about 15 km east of Cologne. It is beautifully located in the countryside, surrounded by lush forests slightly elevated to give a great view depending on weather conditions. The nearest airport is Cologne Bonn (CGN) which is an international airport.
*[https://en.wikipedia.org/wiki/Bergisch_Gladbach Bergisch Gladbach on Wikipedia]
[[File:Bensberg.png|none|thumb|Bensberg (range indicated to Cologne's Cathedral). Screenshot from Google Maps.]]

==Venue==
Our host is the [https://www.akademie-generali.de/en/home Generali Akademie], the dedicated education and conference center of the Generali Group in Germany (it's an insurance company). The location's special appeal is its all-inclusive package: conference rooms, hotel rooms and full catering service are conveniently provided on-site.

''(full disclosure: as an employee, RdH has been there multiple times)''
{| class="wikitable"
|+
!official address
!for navigation systems
|-
|Generali Akademie
Am Schloss 1-3

51429 Bergisch-Gladbach

Germany
|Generali Akademie
Jan-Wellem-Straße

51429 Bergisch-Gladbach

Germany
|}

===Catering===
We have full catering on-site, i.e. breakfast, lunch and dinner including non-alcoholic drinks. Our meeting room also comes with coffee and beverages throughout the day.
===Facilities===
*Wireless networking (fast broadband), powered by [https://www.m3connect.de/ m3connect]
* No wired network available
*Europlug type F
** we should bring some power strips
*LCD projector, DVD player, VHS VCR (lol!)
*swimming pool, whirlpool, sauna
=== Vicinity===
Nature. A castle. A small city.

=== Arrival and Departure ===
All times UTC+1.

* earliest arrival on Monday: 8am
** hotel rooms available: 3pm
* latest departure on Friday: 5pm
** We have some flexibility here, but we need to tell our hosts in advance.

==Travel information==
Your main destination is Cologne.

=== from Cologne/Bonn airport (CGN) to central station ===
Take the tram [https://ekap-download.vrs.de/downloads/linien/mini-fahrplan/2023_1219_S19.pdf?1671001552 S19] to Cologne central station. Travel time is about 15 minutes. The tram is scheduled every 20 minutes for most of the day.

=== from Cologne central station to Bensberg (public transportation) ===
Take the bus [https://ekap-download.vrs.de/downloads/linien/mini-fahrplan/2023_40_SB40.pdf?1670826858 Schnellbus SB 40] that directly connects Cologne central station to Bensberg (final stop). Travel time is about 30 minutes. This bus is scheduled every half hour between 6am and 8pm.
[[File:Central station.png|none|thumb]]
Once you arrive at the [https://ekap-download.vrs.de/downloads/haltestellen/lageplan/u_Bergisch_Gladbach_Bensberg.pdf?1670243814 bus stop in Bensberg], you can either take a taxi or walk about 900m to our location.
[[File:Bus stop bensberg.png|none|thumb]]

=== from Cologne central station to Bensberg (cab) ===
Our hosts have special conditions with a local cab service (https://www.transfer-nurdogan.de/). I can't tell if that's cheaper compared to the others or just for a classy look:

* 45 € (standard)
* 50 € (large cab, suitable for sharing)

== Hotels ==
Hotel rooms are provided on-site and are part of our conference package, no dedicated booking necessary.

==Cost calculation==

=== per attendee ===

The fee for housing and catering per attendee is 837 € and is due on the last day of the event, payable via debit or credit card (VISA, Mastercard) by each individual themself. A billing address needs to be provided in advance.<syntaxhighlight lang="text">
hotel room incl. breakfast 127 € x 4 days = 508 €
catering service (days 1-4) 70 € x 4 days = 280 €
catering service (day 5) 49 € x 1 day = 49 €
-------------------------------------------- 837 €
</syntaxhighlight>

=== joint event ===
One attendee (RdH) needs to pay the additional fees for the joint event. This covers the meeting room (900 €) and all the alcoholic drinks (estimated 500 €) that have been consumed during the event. ''(Alcoholic drinks are not included in our otherwise "all inclusive" package and individual payment is not possible.)''<syntaxhighlight lang="text">
meeting room (days 1-5) 180 € x 5 days = 900 €
alcoholic drinks 500 € x 1 = 500 €
-------------------------------------------- 1,400 €
</syntaxhighlight>

=== Total ===

Using the interim results from above, this brings us to a total cost (excl. travel) of 9,770 €.<syntaxhighlight lang="text">
participants 837 € x 10 = 8,370 €
joint event 1400 € x 1 = 1,400 €
-------------------------------------------- 9,770 €
</syntaxhighlight>
=Attendance =

*Hackfest Bensberg 2023 takes place on '''March 13-17, 2023'''
*deadline to apply for attendance is '''February 01, 2023'''

== preface==
In an initial poll, 8 people expressed their interest/availability for this hackfest. Based on this number we are planning for 10 attendees. Should more people be interested, we'll try our best to expand - the earlier we know, the better! If we don't reach 10, we will try to scale down our booking. If you are interested, don't hold yourself back!

==I want to attend!==
That's great! Be aware of the following:

*You are making a commitment here which will produce expenses for the project. Please make sure that you will be able to honor this commitment! ''(Are you table to take the week off from your day job? Are you able to travel? etc.)''
* Every attendee will have to pay their fee of 837 € on the last day of the hackfest. There is something special about payment methods that we will have to talk about privately, I'll contact everyone. ''(After the hackfest you can follow the reimbursement procedure.)''
*You are eligible to apply no matter if you participated in the initial poll/"call for interest". ''(Only in case we end up being seriously overbooked and cannot accommodate for everybody we will take the initial poll into account.)''

Now go ahead and add yourself to this table (or ask in [https://gitlab.com/inkscape/inbox/-/issues/8109 this issue] and it will be done for you):

Join the Signal phone group to keep in touch with everyone during the event.
{| class="wikitable"
|+
!Name
!GitLab handle
!Inbound
!Outbound
|-
|Martin Owens
|@doctormo
|LH423 13T05:15 FRA
|UA8853 21T10:50 FRA
|-
|Jonathan Neuhauser
|@joneuhauser
|13.03. 9:55 (Bensberg)
|17.03. 16:08 (Bensberg)
|-
|Tavmjong Bah
|@Tavmjong
|13.03 13:15 Cologne
|17.03 18:43 Cologne
|-
|Marc Jeanmougin
|@marcjeanmougin
|12.03 13h15 Cologne Hbf
|19.03 13h42 Cologne Hbf
|-
|Chris Rogers
|@CRogers
|booked - ok!
|booked - ok!
|-
|René de Hesselle
|@dehesselle
|13.03. 9:00 (Bensberg)
|17.03. 17:00 (Bensberg)
|-
|Jabier Arraiza
|@jabiertxof
|
|
|-
|Thomas Holder
|@speleo3
|13.03. 12:05 Cologne Hbf
|17.03. 17:55 Cologne Hbf
|-
|Ted Gould
|@ted.gould
|
|
|-
|Nicco Kunzmann
|@niccokunzmann
|
|
|}

== I want SFC to pay for my flight/train ==

* @doctormo
* @jabiertxof
* @niccokunzmann
*@speleo3

== Hackfest Agenda ==

=== Add your ideas here! We'll make a tentative agenda at the start ===

* Organization
** Community: Vectors, Testers, Translators, etc.
*** Social video call with Vectors.
***Is there interest in merging communities? E.g. our user channel and Discord?
** Board election
** Financial status
** Paid development
**App Store
* Infrastructure
** Website, social media
** Resources for developers
* GSoC and Outreachy
* Development discussions
** Releases
** Dependencies
** Bug fixing
** GTK4
** Refactoring
**advancing C++ standard (depends on change in macOS pipeline)
***getting rid of boost
***using newer stuff from std
** etc.
* Hacking
** Code reviews
** Critical bugs for 1.3

Hackfest2023 Bensberg

2023-01-27T14:44:31Z

Speleo3: Added speleo3 to list of attendees

[[Category:Hackfest]]

This page '''<big>IS WORK IN PROGRESS</big>''' and details the planning of Inkscape's 2023 hackfest in Bensberg, Germany. The hackfest will take place on '''March 13-17, 2023'''. We are looking to bring together a group of '''10 attendees''', but do not let that number discourage you from throwing your hat in the ring in case we reach/go over it.

This hackfest is a standalone event and not organized around any other event or FOSS conference.

Previous events: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 SCALE]], [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].
=Description=
It's a hackfest! We will work on Inkscape bugs, new features, packaging, website issues, ... in fact anything that can benefit from us being physically in the same space. And let's not forget about the social component - we get to hang and talk and laugh in person since we usually only meet virtually :).
==Bensberg==
Bensberg is part of Bergisch Gladbach, a city in the western part of Germany, about 15 km east of Cologne. It is beautifully located in the countryside, surrounded by lush forests slightly elevated to give a great view depending on weather conditions. The nearest airport is Cologne Bonn (CGN) which is an international airport.
*[https://en.wikipedia.org/wiki/Bergisch_Gladbach Bergisch Gladbach on Wikipedia]
[[File:Bensberg.png|none|thumb|Bensberg (range indicated to Cologne's Cathedral). Screenshot from Google Maps.]]

==Venue==
Our host is the [https://www.akademie-generali.de/en/home Generali Akademie], the dedicated education and conference center of the Generali Group in Germany (it's an insurance company). The location's special appeal is its all-inclusive package: conference rooms, hotel rooms and full catering service are conveniently provided on-site.

''(full disclosure: as an employee, RdH has been there multiple times)''
{| class="wikitable"
|+
!official address
!for navigation systems
|-
|Generali Akademie
Am Schloss 1-3

51429 Bergisch-Gladbach

Germany
|Generali Akademie
Jan-Wellem-Straße

51429 Bergisch-Gladbach

Germany
|}

===Catering===
We have full catering on-site, i.e. breakfast, lunch and dinner including non-alcoholic drinks. Our meeting room also comes with coffee and beverages throughout the day.
===Facilities===
*Wireless networking (fast broadband), powered by [https://www.m3connect.de/ m3connect]
* No wired network available
*Europlug type F
** we should bring some power strips
*(TODO - not sure if we have that) LCD projector
*flip chart
*(TODO add additional info e.g. pool)
=== Vicinity===
tbd (we're not in a city, we're in the country)

===Travel information===
tbd

===Cost calculation===
The fee per attendee is 837 € and is due on the last day of the event, payable via debit or credit card (VISA, Mastercard). A billing address needs to be provided in advance.<syntaxhighlight lang="text">
hotel room incl. breakfast 127 € x 4 days = 508 €
catering service (days 1-4) 70 € x 4 days = 280 €
catering service (day 5) 49 € x 1 day = 49 €
-------------------------------------------- 837 €
</syntaxhighlight>One attendee (RdH) needs to pay the additional fee for the meeting room.<syntaxhighlight lang="text">
meeting room (days 1-5) 180 € x 5 days = 900 €
</syntaxhighlight>

==Hotels==
Hotel rooms are provided on-site and are part of our conference package, no dedicated booking necessary.

=Attendance =

*Hackfest Bensberg 2023 takes place on '''March 13-17, 2023'''
*deadline to apply for attendance is '''February 01, 2023'''

== preface==
In an initial poll, 8 people expressed their interest/availability for this hackfest. Based on this number we are planning for 10 attendees. Should more people be interested, we'll try our best to expand - the earlier we know, the better! If we don't reach 10, we will try to scale down our booking. If you are interested, don't hold yourself back!

==I want to attend!==
That's great! Be aware of the following:

*You are making a commitment here which will produce expenses for the project. Please make sure that you will be able to honor this commitment! ''(Are you table to take the week off from your day job? Are you able to travel? etc.)''
* Every attendee will have to pay their fee of 837 € on the last day of the hackfest. There is something special about payment methods that we will have to talk about privately, I'll contact everyone. ''(After the hackfest you can follow the reimbursement procedure.)''
*You are eligible to apply no matter if you participated in the initial poll/"call for interest". ''(Only in case we end up being seriously overbooked and cannot accommodate for everybody we will take the initial poll into account.)''

Now go ahead and add yourself to this table (or ask in [https://gitlab.com/inkscape/inbox/-/issues/8109 this issue] and it will be done for you):
{| class="wikitable"
|+
!Name
!GitLab handle
|-
|Martin Owens
|@doctormo
|-
|Jonathan Neuhauser
|@joneuhauser
|-
|Tavmjong Bah
|@Tavmjong
|-
|Marc Jeanmougin
|@marcjeanmougin
|-
|Chris Rogers
|@CRogers
|-
|René de Hesselle
|@dehesselle
|-
|Jabier Arraiza
|@jabiertxof
|-
|Thomas Holder
|@speleo3
|-
|9
|
|-
|10
|
|}

CompilingMacOsX

2022-04-10T19:18:34Z

Speleo3: libsoup@2 as pointed out by Meow Day in https://gitlab.com/inkscape/inkscape/-/issues/3317

__TOC__

= Using MacPorts =

<ol>
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port install \
adwaita-icon-theme \
boehmgc \
boost \
cairo \
ccache \
cmake \
double-conversion \
gdl3 \
gettext \
gsl \
gtkmm3 \
gtk-osx-application-gtk3 \
lcms2 \
libsoup \
libxslt \
ninja \
poppler \
potrace \
py-lxml \
py-numpy \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to install
PREFIX="$PWD/install-prefix"

# where to build
mkdir build
cd build

cmake \
-G Ninja \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_OPENMP=OFF \
../inkscape

ninja
ninja install
</syntaxhighlight>
''Note: Using [https://en.wikipedia.org/wiki/Ccache ccache] and [https://ninja-build.org/ ninja] is not required, but very common because it speeds up compilation.''
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

= Using Homebrew =

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.

List of '''packages''' to install with brew
(for Inkscape 1.1):

<syntaxhighlight lang="bash">
brew install \
adwaita-icon-theme \
bdw-gc \
boost \
cairomm \
ccache \
cmake \
double-conversion \
gettext \
gsl \
gspell \
gtk-mac-integration \
gtkmm3 \
imagemagick \
intltool \
lcms2 \
libomp \
libsoup@2 \
libxslt \
ninja \
poppler \
potrace
</syntaxhighlight>

You may substitute <code>imagemagick</code> with <code>graphicsmagick</code>.

<code>gtk-mac-integration</code> is not needed with latest <code>1.2-dev</code>.

Some keg-only libraries need to be added to <code>$PKG_CONFIG_PATH</code>

Some libraries can cause trouble if they are picked up from the SDK instead of Homebrew (observed with <code>libxslt</code> and <code>libxml2</code>). Adding them to <code>$PKG_CONFIG_PATH</code> should fix this.

This was tested on an M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev.

<syntaxhighlight lang="bash">
# use a clean Homebrew environment (optional)
LIBPREFIX="/opt/homebrew"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# keg-only libraries
export PKG_CONFIG_PATH="$LIBPREFIX/opt/icu4c/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libsoup@2/lib/pkgconfig"

# prevent picking up libxslt and libxml2 from the (wrong) SDK
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libxslt/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libxml2/lib/pkgconfig"

# where to install
PREFIX="$PWD/install-prefix"

mkdir -p build
cd build

cmake \
-G Ninja \
-DCMAKE_SHARED_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_EXE_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_INSTALL_PREFIX=$PREFIX \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_DBUS=OFF \
..

ninja
ninja install
</syntaxhighlight>

=See also=
* [[Tracking Dependencies]]
* [[Extension requirements]]
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build
* [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md ipatch's collection of notes] about building Inkscape using Homebrew

[[Category:Developer Documentation]]

CompilingMacOsX

2022-01-06T09:45:44Z

Speleo3: libxslt/libxml2 SDK fix

__TOC__

= Using MacPorts =

<ol>
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port install \
adwaita-icon-theme \
boehmgc \
boost \
cairo \
ccache \
cmake \
double-conversion \
gdl3 \
gettext \
gsl \
gtkmm3 \
gtk-osx-application-gtk3 \
lcms2 \
libsoup \
libxslt \
ninja \
poppler \
potrace \
py-lxml \
py-numpy \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to install
PREFIX="$PWD/install-prefix"

# where to build
mkdir build
cd build

cmake \
-G Ninja \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_OPENMP=OFF \
../inkscape

ninja
ninja install
</syntaxhighlight>
''Note: Using [https://en.wikipedia.org/wiki/Ccache ccache] and [https://ninja-build.org/ ninja] is not required, but very common because it speeds up compilation.''
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

= Using Homebrew =

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.

List of '''packages''' to install with brew
(for Inkscape 1.1):

<syntaxhighlight lang="bash">
brew install \
adwaita-icon-theme \
bdw-gc \
boost \
cairomm \
ccache \
cmake \
double-conversion \
gettext \
gsl \
gspell \
gtk-mac-integration \
gtkmm3 \
imagemagick \
intltool \
lcms2 \
libomp \
libsoup \
libxslt \
ninja \
poppler \
potrace
</syntaxhighlight>

You may substitute <code>imagemagick</code> with <code>graphicsmagick</code>.

<code>gtk-mac-integration</code> is not needed with latest <code>1.2-dev</code>.

Some keg-only libraries need to be added to <code>$PKG_CONFIG_PATH</code>

Some libraries can cause trouble if they are picked up from the SDK instead of Homebrew (observed with <code>libxslt</code> and <code>libxml2</code>). Adding them to <code>$PKG_CONFIG_PATH</code> should fix this.

This was tested on an M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev.

<syntaxhighlight lang="bash">
# use a clean Homebrew environment (optional)
LIBPREFIX="/opt/homebrew"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# keg-only libraries
export PKG_CONFIG_PATH="$LIBPREFIX/opt/icu4c/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libsoup@2/lib/pkgconfig"

# prevent picking up libxslt and libxml2 from the (wrong) SDK
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libxslt/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libxml2/lib/pkgconfig"

# where to install
PREFIX="$PWD/install-prefix"

mkdir -p build
cd build

cmake \
-G Ninja \
-DCMAKE_SHARED_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_EXE_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_INSTALL_PREFIX=$PREFIX \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_DBUS=OFF \
..

ninja
ninja install
</syntaxhighlight>

=See also=
* [[Tracking Dependencies]]
* [[Extension requirements]]
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build
* [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md ipatch's collection of notes] about building Inkscape using Homebrew

[[Category:Developer Documentation]]

CompilingMacOsX

2022-01-05T10:57:07Z

Speleo3: add table of contents

__TOC__

= Using MacPorts =

<ol>
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port install \
adwaita-icon-theme \
boehmgc \
boost \
cairo \
ccache \
cmake \
double-conversion \
gdl3 \
gettext \
gsl \
gtkmm3 \
gtk-osx-application-gtk3 \
lcms2 \
libsoup \
libxslt \
ninja \
poppler \
potrace \
py-lxml \
py-numpy \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to install
PREFIX="$PWD/install-prefix"

# where to build
mkdir build
cd build

cmake \
-G Ninja \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_OPENMP=OFF \
../inkscape

ninja
ninja install
</syntaxhighlight>
''Note: Using [https://en.wikipedia.org/wiki/Ccache ccache] and [https://ninja-build.org/ ninja] is not required, but very common because it speeds up compilation.''
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

= Using Homebrew =

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.

List of '''packages''' to install with brew
(for Inkscape 1.1):

<syntaxhighlight lang="bash">
brew install \
adwaita-icon-theme \
bdw-gc \
boost \
cairomm \
ccache \
cmake \
double-conversion \
gettext \
gsl \
gspell \
gtk-mac-integration \
gtkmm3 \
imagemagick \
intltool \
lcms2 \
libomp \
libsoup \
libxslt \
ninja \
poppler \
potrace
</syntaxhighlight>

You may substitute <code>imagemagick</code> with <code>graphicsmagick</code>.

<code>gtk-mac-integration</code> is not needed with latest <code>1.2-dev</code>.

Some keg-only libraries need to be added to <code>$PKG_CONFIG_PATH</code>

This was tested on an M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev. It only worked for me with the command line tools SDK and required `-isysroot $SDKROOT` and explicit linker flags (see below).

<syntaxhighlight lang="bash">
# use a clean Homebrew environment (optional)
LIBPREFIX="/opt/homebrew"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# use command line tools SDK (Xcode SDK didn't work for me)
export SDKROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk"

# keg-only libraries
export PKG_CONFIG_PATH="$LIBPREFIX/opt/icu4c/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libsoup@2/lib/pkgconfig"

# where to install
PREFIX="$PWD/install-prefix"

mkdir -p build
cd build

cmake \
-G Ninja \
-DCMAKE_CXX_FLAGS="-isysroot $SDKROOT" \
-DCMAKE_SHARED_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_EXE_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_INSTALL_PREFIX=$PREFIX \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_DBUS=OFF \
..

ninja
ninja install
</syntaxhighlight>

=See also=
* [[Tracking Dependencies]]
* [[Extension requirements]]
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build
* [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md ipatch's collection of notes] about building Inkscape using Homebrew

[[Category:Developer Documentation]]

CompilingMacOsX

2022-01-05T10:55:09Z

Speleo3: update Homebrew instructions

= Using MacPorts =

<ol>
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port install \
adwaita-icon-theme \
boehmgc \
boost \
cairo \
ccache \
cmake \
double-conversion \
gdl3 \
gettext \
gsl \
gtkmm3 \
gtk-osx-application-gtk3 \
lcms2 \
libsoup \
libxslt \
ninja \
poppler \
potrace \
py-lxml \
py-numpy \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to install
PREFIX="$PWD/install-prefix"

# where to build
mkdir build
cd build

cmake \
-G Ninja \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_OPENMP=OFF \
../inkscape

ninja
ninja install
</syntaxhighlight>
''Note: Using [https://en.wikipedia.org/wiki/Ccache ccache] and [https://ninja-build.org/ ninja] is not required, but very common because it speeds up compilation.''
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

= Using Homebrew =

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.

List of '''packages''' to install with brew
(for Inkscape 1.1):

<syntaxhighlight lang="bash">
brew install \
adwaita-icon-theme \
bdw-gc \
boost \
cairomm \
ccache \
cmake \
double-conversion \
gettext \
gsl \
gspell \
gtk-mac-integration \
gtkmm3 \
imagemagick \
intltool \
lcms2 \
libomp \
libsoup \
libxslt \
ninja \
poppler \
potrace
</syntaxhighlight>

You may substitute <code>imagemagick</code> with <code>graphicsmagick</code>.

<code>gtk-mac-integration</code> is not needed with latest <code>1.2-dev</code>.

Some keg-only libraries need to be added to <code>$PKG_CONFIG_PATH</code>

This was tested on an M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev. It only worked for me with the command line tools SDK and required `-isysroot $SDKROOT` and explicit linker flags (see below).

<syntaxhighlight lang="bash">
# use a clean Homebrew environment (optional)
LIBPREFIX="/opt/homebrew"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# use command line tools SDK (Xcode SDK didn't work for me)
export SDKROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk"

# keg-only libraries
export PKG_CONFIG_PATH="$LIBPREFIX/opt/icu4c/lib/pkgconfig"
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$LIBPREFIX/opt/libsoup@2/lib/pkgconfig"

# where to install
PREFIX="$PWD/install-prefix"

mkdir -p build
cd build

cmake \
-G Ninja \
-DCMAKE_CXX_FLAGS="-isysroot $SDKROOT" \
-DCMAKE_SHARED_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_EXE_LINKER_FLAGS="-L$LIBPREFIX/lib" \
-DCMAKE_INSTALL_PREFIX=$PREFIX \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_DBUS=OFF \
..

ninja
ninja install
</syntaxhighlight>

=See also=
* [[Tracking Dependencies]]
* [[Extension requirements]]
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build
* [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md ipatch's collection of notes] about building Inkscape using Homebrew

[[Category:Developer Documentation]]

Refactoring projects

2021-04-01T16:31:38Z

Speleo3: Attention in bold

{{DevDiscussion}}

A List of Refactoring Projects

See [[Development Project Ideas]] and [[Projects | Funded Project Ideas]] for more possible projects.

See [[Refactoring plan]] for guidelines on how to refactor.

= Little Projects =

'''''Attention: Some of these suggestions might not make sense''' or have better solutions. For example instead of moving some unused function to a different file, you should remove it. Apply the [[Refactoring plan#Principles|principles]] of adding unit tests and adding documentation (doxygen comments).''

* Derive SPStar from SPShape (not SPPolygon), update 'object/README'.
* Move sp-item-transform.h functions into SPItem.
* Move sp-item-update-cns.h function into SPItem.
* Move sp-item-rm-unsatisfied-cns.h function into SPItem.
* Remove config.h code (or document why it is needed). DOCUMENT/Autogenerated
* <strike>Remove macros.h (or document why it is needed). DELETE</strike>
* <strike>Remove dependence on Glib::object in ResourceManager().</strike>
* Simplify ResourceManager... it does only one thing: fix broken links.
* In SPObject one can write:
getRepr()->setAttribute("x", "y");
or
setKeyValue( sp_attribute_lookup("x"), "y");
These are redundant and neither is really convenient. SPObject perhaps should have it's own setAttribute() function.
* Rename helper-fns.h with a better discriptive name and move to util(?). MOVE/RENAME
* Remove dependence on object-set.h in files in src/livarot directory.
* Evaluate all the functions in io/sys.h/.cpp. See if we can't use standard glib functions.
* Remove helper/ucompose.hpp and it's use in src/event-log.cpp
* Move functionality of src/line-geometry.h/.cpp into lib2geom or elsewhere.
* Remove deprecated GDK_POINTER_MOTION_HINT_MASK (motion events are compressed since Gdk 3.8).
* Turn DrawAnchor into a proper class (or figure out how to get rid of it all together).
* Clean up constructors and signals in selcue.cpp.
* Remove need to write out and read back in a PNG file with createBitmapImage().

= Medium Projects =

* <strike>Remove god-awful SPWidget (only used for selection).</strike> Yeah!!!
* Move most files in 'src' to subdirectories, add ''README'' for each directory with description of contents. (Tav)
* In toolbars, use ''dataKludge'' or ''data'' or ''tbl'' or ''holder'' ... but not all four! (Side benefit of C++ify toolbars.) (Alex)
* Remove InkAction class. Normal GTK button actions should be able to handle SVG icons... no need for derived class. (Alex)
* Make data members private in SPI::Base and derived class. Add set() function. Default to SP_STYLE_UNSET in constructor, setting to SP_STYLE_SRC_PROP in set(). (Tav)
* Sort out URL/file handling. See [[URIs and Filenames]].
* Find all the ways we output error/status messages to users (this does not include developer focused error messages that use std::cerr). Pick one and use it everywhere. The goal should be to be able to build Inkscape without a GUI but if the GUI is used, the user will see the messages on the desktop.
* Look at Inkscape::URIReference and derived classes to see if they can't be simplified/templated/etc.
* Make sp_repr_set_svg_double etc. member functions of Inkscape::XML::Node. [sp_repr_set_svg_double() -> setAttributeSvgDouble()].
* Redo Save/Export separating Lossless vs Lossy formats. Create one path for all Exports that share processing so that all options (that make sense) are available to all output formats.
* Refactor toolbase and derived classes. The conversion from C to C++ seems to be only partially done.
* Move the functionality found in SPDesktop to SPCanvas or InkscapeWindow, then kill it as well as View!
* Divide display directory into:
** canvas: GUI related routines, move to ui/
** drawing: Generic rendering routines
* Clean-up Key events. Check to see if get_latin_keyval() can be moved to InkscapeWindow::on_key_press() and removed everywhere else. (Must make sure it doesn't interfere with typing text.)
* Get rid of all Glib::wrap's.
* Git rid of all gobj()'s.
* Make liblcms2 a hard dependency and git rid of 92 #ifdefs.
* Merge old knot code with "new" control-point code.

= Large Projects =

* C++ify toolbars. (Alex)
* Convert all GtkActions's and Gtk::Action's to Gio::Action's. See [[GtkAction migration]] (Alex)
* Add a one or two line description of what each file contains at the top of the file if it is missing. (Everyone)
* Remove livarot, moving any needed functionality into lib2geom or other files.
* Remove desktop dependence on reading and setting style on a document. In particular remove sp_desktop_set_style().
* C++ify SPCanvasItem and all its derived class. <strike>Use Gtk::Object as base so that it can be memory managed by Canvas widget.</strike>

= Super Large Projects =

* Convert verbs to Gio::Action's.
* Convert GUI to XML files. (Long term.)
* <strike>Invert 'y' coordinate system to match SVG. (Look at previous patch... link?)</strike>

Refactoring projects

2021-03-21T13:34:31Z

Speleo3: Attention

{{DevDiscussion}}

A List of Refactoring Projects

See [[Development Project Ideas]] and [[Projects | Funded Project Ideas]] for more possible projects.

See [[Refactoring plan]] for guidelines on how to refactor.

= Little Projects =

''Attention: Some of these suggestions might not make sense or have better solutions. For example instead of moving some unused function to a different file, you should remove it. Apply the [[Refactoring plan#Principles|principles]] of adding unit tests and adding documentation (doxygen comments).''

* Derive SPStar from SPShape (not SPPolygon), update 'object/README'.
* Move sp-item-transform.h functions into SPItem.
* Move sp-item-update-cns.h function into SPItem.
* Move sp-item-rm-unsatisfied-cns.h function into SPItem.
* Remove config.h code (or document why it is needed). DOCUMENT/Autogenerated
* <strike>Remove macros.h (or document why it is needed). DELETE</strike>
* <strike>Remove dependence on Glib::object in ResourceManager().</strike>
* Simplify ResourceManager... it does only one thing: fix broken links.
* In SPObject one can write:
getRepr()->setAttribute("x", "y");
or
setKeyValue( sp_attribute_lookup("x"), "y");
These are redundant and neither is really convenient. SPObject perhaps should have it's own setAttribute() function.
* Rename helper-fns.h with a better discriptive name and move to util(?). MOVE/RENAME
* Remove dependence on object-set.h in files in src/livarot directory.
* Evaluate all the functions in io/sys.h/.cpp. See if we can't use standard glib functions.
* Remove helper/ucompose.hpp and it's use in src/event-log.cpp
* Move functionality of src/line-geometry.h/.cpp into lib2geom or elsewhere.
* Remove deprecated GDK_POINTER_MOTION_HINT_MASK (motion events are compressed since Gdk 3.8).
* Turn DrawAnchor into a proper class (or figure out how to get rid of it all together).
* Clean up constructors and signals in selcue.cpp.
* Remove need to write out and read back in a PNG file with createBitmapImage().

= Medium Projects =

* <strike>Remove god-awful SPWidget (only used for selection).</strike> Yeah!!!
* Move most files in 'src' to subdirectories, add ''README'' for each directory with description of contents. (Tav)
* In toolbars, use ''dataKludge'' or ''data'' or ''tbl'' or ''holder'' ... but not all four! (Side benefit of C++ify toolbars.) (Alex)
* Remove InkAction class. Normal GTK button actions should be able to handle SVG icons... no need for derived class. (Alex)
* Make data members private in SPI::Base and derived class. Add set() function. Default to SP_STYLE_UNSET in constructor, setting to SP_STYLE_SRC_PROP in set(). (Tav)
* Sort out URL/file handling. See [[URIs and Filenames]].
* Find all the ways we output error/status messages to users (this does not include developer focused error messages that use std::cerr). Pick one and use it everywhere. The goal should be to be able to build Inkscape without a GUI but if the GUI is used, the user will see the messages on the desktop.
* Look at Inkscape::URIReference and derived classes to see if they can't be simplified/templated/etc.
* Make sp_repr_set_svg_double etc. member functions of Inkscape::XML::Node. [sp_repr_set_svg_double() -> setAttributeSvgDouble()].
* Redo Save/Export separating Lossless vs Lossy formats. Create one path for all Exports that share processing so that all options (that make sense) are available to all output formats.
* Refactor toolbase and derived classes. The conversion from C to C++ seems to be only partially done.
* Move the functionality found in SPDesktop to SPCanvas or InkscapeWindow, then kill it as well as View!
* Divide display directory into:
** canvas: GUI related routines, move to ui/
** drawing: Generic rendering routines
* Clean-up Key events. Check to see if get_latin_keyval() can be moved to InkscapeWindow::on_key_press() and removed everywhere else. (Must make sure it doesn't interfere with typing text.)
* Get rid of all Glib::wrap's.
* Git rid of all gobj()'s.
* Make liblcms2 a hard dependency and git rid of 92 #ifdefs.
* Merge old knot code with "new" control-point code.

= Large Projects =

* C++ify toolbars. (Alex)
* Convert all GtkActions's and Gtk::Action's to Gio::Action's. See [[GtkAction migration]] (Alex)
* Add a one or two line description of what each file contains at the top of the file if it is missing. (Everyone)
* Remove livarot, moving any needed functionality into lib2geom or other files.
* Remove desktop dependence on reading and setting style on a document. In particular remove sp_desktop_set_style().
* C++ify SPCanvasItem and all its derived class. <strike>Use Gtk::Object as base so that it can be memory managed by Canvas widget.</strike>

= Super Large Projects =

* Convert verbs to Gio::Action's.
* Convert GUI to XML files. (Long term.)
* <strike>Invert 'y' coordinate system to match SVG. (Look at previous patch... link?)</strike>

CompilingMacOsX

2021-03-20T16:19:03Z

Speleo3: homebrew dependencies for Inkscape 1.1

= Using MacPorts =

<ol>
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port install \
adwaita-icon-theme \
boehmgc \
boost \
cairo \
ccache \
cmake \
double-conversion \
gdl3 \
gettext \
gsl \
gtkmm3 \
gtk-osx-application-gtk3 \
lcms2 \
libsoup \
libxslt \
ninja \
poppler \
potrace \
py-lxml \
py-numpy \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to install
PREFIX="$PWD/install-prefix"

# where to build
mkdir build
cd build

cmake \
-G Ninja \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DWITH_OPENMP=OFF \
..

ninja
ninja install
</syntaxhighlight>
''Note: Using [https://en.wikipedia.org/wiki/Ccache ccache] and [https://ninja-build.org/ ninja] is not required, but very common because it speeds up compilation.''
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

= Using Homebrew =

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.

List of '''packages''' to install with brew
(for Inkscape 1.1):

<syntaxhighlight lang="bash">
brew install \
adwaita-icon-theme \
bdw-gc \
boost \
cairomm \
ccache \
cmake \
double-conversion \
gettext \
gsl \
gspell \
gtk-mac-integration \
gtkmm3 \
imagemagick \
intltool \
lcms2 \
libomp \
libsoup \
libxslt \
ninja \
poppler \
potrace
</syntaxhighlight>

You may substitute <code>imagemagick</code> with <code>graphicsmagick</code>.

Since '''Homebrew''' only offers <code>gettext</code> as a keg (not linked to <code>/usr/local</code>) an extra option needs to be passed on to <code>cmake</code>.

Modify the script in step 5 by changing <code>LIBPREFIX="/usr/local"</code> and adding the following line to the cmake arguments:

<syntaxhighlight lang="bash">
-DIntl_INCLUDE_DIR="$LIBPREFIX/opt/gettext/include" \
</syntaxhighlight>

=See also=
* [[Tracking Dependencies]]
* [[Extension requirements]]
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build
* [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md ipatch's collection of notes] about building Inkscape using Homebrew

[[Category:Developer Documentation]]

Community Development

2020-12-23T11:26:42Z

Speleo3:

'''Draft'''

== Book Campaign ==

In the past, the Inkscape board has allocated funds to buy books for active developers. We plan on doing another book campaign, but this time opening it up to all members of the Inkscape community. There are two conditions for receiving a book:

# You've been contributing to the Inkscape community for at least six months (and plan to continue!).
# The book will aid your contributions.

If you would like a book, please add your name to the following list:

{| class="wikitable" style="text-align: center;"
|-
! Name
! Active since
! Book
|-
| Tav
| 2007
| C++17 (Josuttis)
|-
| You!
| 201x
| Making Inkscape Awesome!
|}

At a later point, we'll need your contact information to send you the book.

Suggested books:
* Community development
** [https://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590 Producing Open Source Software (Fogel)]
** [https://www.amazon.com/Forge-Your-Future-Open-Source/dp/1680503014 Forge Your Future with Open Source (Brasseur)]
** ?
* Website development
** ?

* Design
**https://www.creativebloq.com/graphic-design/books-graphic-designers-11135231

* UX
**https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654
**Don't Make Me Think (Krug)
**https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/
**Gamestorming: A Playbook For Innovators, Rulebreakers, and Changemakers (Grey, Brown, Macanufo);

* Developer development
** [https://www.amazon.com/Expert-proficient-programmer-learning-practices/dp/1838552650 Expert C++ (Grigoryan, Wu)]
** [https://www.amazon.com/C-17-Complete-Guide-First/dp/396730017X C++17 - The Complete Guide (Josuttis)]
** [https://www.amazon.com/17-Detail-Exciting-Features-Standard/dp/1798834065 C++17 In Detail (Filipek)]
** [https://www.amazon.com/Professional-C-Marc-Gregoire-dp-1119695406/dp/1119695406 Professional C++ (Gregoire)]
** [https://www.amazon.com/Effective-Specific-Improve-Programs-Designs/dp/0321334876 Effective C++ 3rd Edition (Meyers)]
** [https://www.amazon.com/Effective-Modern-Specific-Ways-Improve/dp/1491903996 Effective Modern C++ (Meyers)]
** [https://www.amazon.com/Python-Crash-Course-2nd-Edition/dp/1593279280Python Crash Course (Matthes)]
** ?

== Developer Presentations ==

''(Developer development)''

Developers could share knowledge and experience with short presentations, followed by discussion.
This could be incorporated in the weekly developer meeting, or scheduled as a separate event (TBD).
If the presenter agrees, these presentations should be recorded.

Ideas for topics:

* Warnings and Assertions best practices (Thomas, Dec 22, 2020)
* std::move and other modern C++ features
* How does Inkscape's garbage collection work?
* How to properly use signals (libsigc++)
* Why is direct manipulation of the XML tree discouraged?
* What is a node observer?
* Text (Tav)
* Exceptions

Community Development

2020-12-14T17:30:11Z

Speleo3:

'''Draft'''

== Book Campaign ==

In the past, the Inkscape board has allocated funds to buy books for active developers. We plan on doing another book campaign, but this time opening it up to all members of the Inkscape community. There are two conditions for receiving a book:

# You've been contributing to the Inkscape community for at least six months (and plan to continue!).
# The book will aid your contributions.

If you would like a book, please add your name to the following list:

{| class="wikitable" style="text-align: center;"
|-
! Name
! Active since
! Book
|-
| Tav
| 2007
| C++17 (Josuttis)
|-
| You!
| 201x
| Making Inkscape Awesome!
|}

At a later point, we'll need your contact information to send you the book.

Suggested books:
* Community development
** [https://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590 Producing Open Source Software (Fogel)]
** [https://www.amazon.com/Forge-Your-Future-Open-Source/dp/1680503014 Forge Your Future with Open Source (Brasseur)]
** ?
* Website development
** ?

* Design
**https://www.creativebloq.com/graphic-design/books-graphic-designers-11135231

* UX
**https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654
**Don't Make Me Think (Krug)
**https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/
**Gamestorming: A Playbook For Innovators, Rulebreakers, and Changemakers (Grey, Brown, Macanufo);

* Developer development
** [https://www.amazon.com/Expert-proficient-programmer-learning-practices/dp/1838552650 Expert C++ (Grigoryan, Wu)]
** [https://www.amazon.com/C-17-Complete-Guide-First/dp/396730017X C++17 - The Complete Guide (Josuttis)]
** [https://www.amazon.com/17-Detail-Exciting-Features-Standard/dp/1798834065 C++17 In Detail (Filipek)]
** [https://www.amazon.com/Professional-C-Marc-Gregoire-dp-1119695406/dp/1119695406 Professional C++ (Gregoire)]
** [https://www.amazon.com/Effective-Specific-Improve-Programs-Designs/dp/0321334876 Effective C++ 3rd Edition (Meyers)]
** [https://www.amazon.com/Effective-Modern-Specific-Ways-Improve/dp/1491903996 Effective Modern C++ (Meyers)]
** [https://www.amazon.com/Python-Crash-Course-2nd-Edition/dp/1593279280Python Crash Course (Matthes)]
** ?

== Developer Presentations ==

''(Developer development)''

Developers could share knowledge and experience with short presentations, followed by discussion.
This could be incorporated in the weekly developer meeting, or scheduled as a separate event (TBD).
If the presenter agrees, these presentations should be recorded.

Ideas for topics:

* Warnings and Assertions best practices (Thomas)
* std::move and other modern C++ features
* How does Inkscape's garbage collection work?
* How to properly use signals (libsigc++)
* Why is direct manipulation of the XML tree discouraged?
* What is a node observer?
* Text (Tav)

Community Development

2020-12-06T18:40:19Z

Speleo3: Developer Presentations

'''Draft'''

== Book Campaign ==

In the past, the Inkscape board has allocated funds to buy books for active developers. We plan on doing another book campaign, but this time opening it up to all members of the Inkscape community. There are two conditions for receiving a book:

# You've been contributing to the Inkscape community for at least six months (and plan to continue!).
# The book will aid your contributions.

If you would like a book, please add your name to the following list:

{| class="wikitable" style="text-align: center;"
|-
! Name
! Active since
! Book
|-
| Tav
| 2007
| C++17 (Josuttis)
|-
| You!
| 201x
| Making Inkscape Awesome!
|}

At a later point, we'll need your contact information to send you the book.

Suggested books:
* Community development
** [https://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590 Producing Open Source Software (Fogel)]
** [https://www.amazon.com/Forge-Your-Future-Open-Source/dp/1680503014 Forge Your Future with Open Source (Brasseur)]
** ?
* Website development
** ?

* Design
**https://www.creativebloq.com/graphic-design/books-graphic-designers-11135231

* UX
**https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654
**Don't Make Me Think (Krug)
**https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/
**Gamestorming: A Playbook For Innovators, Rulebreakers, and Changemakers (Grey, Brown, Macanufo);

* Developer development
** [https://www.amazon.com/Expert-proficient-programmer-learning-practices/dp/1838552650 Expert C++ (Grigoryan, Wu)]
** [https://www.amazon.com/C-17-Complete-Guide-First/dp/396730017X C++17 - The Complete Guide (Josuttis)]
** [https://www.amazon.com/17-Detail-Exciting-Features-Standard/dp/1798834065 C++17 In Detail (Filipek)]
** [https://www.amazon.com/Professional-C-Marc-Gregoire-dp-1119695406/dp/1119695406 Professional C++ (Gregoire)]
** [https://www.amazon.com/Effective-Specific-Improve-Programs-Designs/dp/0321334876 Effective C++ 3rd Edition (Meyers)]
** [https://www.amazon.com/Effective-Modern-Specific-Ways-Improve/dp/1491903996 Effective Modern C++ (Meyers)]
** [https://www.amazon.com/Python-Crash-Course-2nd-Edition/dp/1593279280Python Crash Course (Matthes)]
** ?

== Developer Presentations ==

''(Developer development)''

Developers could share knowledge and experience with short presentations, followed by discussion.
This could be incorporated in the weekly developer meeting, or scheduled as a separate event (TBD).
If the presenter agrees, these presentations should be recorded.

Ideas for topics:

* Warnings and Assertions best practices
* std::move and other modern C++ features
* How does Inkscape's garbage collection work?
* How to properly use signals (libsigc++)
* Why is direct manipulation of the XML tree discouraged?
* What is a node observer?

Release notes/1.1

2020-11-19T09:05:39Z

Speleo3: hidden dialogs

{{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 no longer depend on GtkSpell and ASpell but on GSpell for spell checking.
* lib2geom has been moved into its own git submodule (like the extensions).

== Improvements ==

* [https://en.wikipedia.org/wiki/XInclude XInclude] support (see [https://gitlab.com/inkscape/inkscape/-/merge_requests/1150 !1150]) ''TODO: Move to a "technical" or "advanced" section?''
* <del>Hidden dialogs stop receiving signals and release resources</del> <ins>Closing a dialog will destroy it</ins>
* Shell mode: a history of commands is now remembered and can be accessed with the up and down arrow keys. [Tab ... autocompletion?]
* Recognize layers in SVG files exported from CorelDraw (see [https://gitlab.com/inkscape/inkscape/-/merge_requests/2046 !2046])

=== General user interface ===

* Dock layouts are now saved in an xml file (<code>docklayout.xml</code>) in the user preferences directory, making them transferable.
* The legacy gradient editor (a dialog that could previously be enabled in the preferences for the gradient tool) has been removed.

=== Canvas ===
==== Rotation lock ====

A new menu item has been added to allow the user to prevent the rotation of the canvas with key bindings commonly associated with zooming in other applications. This setting can be toggled on a per-window basis. In addition, a new preference option has been added to allow users to set the mode to be on when a new window is opened.

<gallery mode="packed" heights=250px>
File:Canvas rotation lock toggle.png|New "Rotation lock" menu item
File:Default rotation lock toggle.png|Configuration option to lock the rotation by default
</gallery>

==== Themeable cursors ====

A set of SVG-based, themeable mouse cursors with HiDPI support were added.
These new cursors are coupled with the icon themes. The default set (hicolor theme) is stored in <code>~inkscape\share\inkscape\icons\hicolor\cursors</code>.

More information can be found on the [[SVG Cursors]] page.

<gallery mode="packed" heights=350px>
File:Coursers.png|New cursor theme
</gallery>

==== 'Outline Overlay' display mode ====

In this mode, a toned down view of the drawing (not click-sensitive) is shown behind the (click-sensitive) object outlines. The opacity of the original drawing in this view mode can be set in Edit > Preferences > Rendering > Outline overlay opacity.

=== Tools ===

==== Node tool ====

The node tool now allows to copy, cut and paste a selection of nodes. These nodes can be inserted into the original path, into a different path or they can be pasted as a completely new path.

<gallery mode="packed" heights=500px>
File:Copy paste nodes.gif| Copy, cut and paste just parts of the paths
</gallery>

==== Connector tool ====

* Connection lines now update in real time while objects are moved
* New sub-point connections for clones and groups, allowing users to use Inkscape to connect diagrams together like in other drafting tools:

<gallery mode="packed" heights=250px>
File:Sub connector points.gif|New sub-connector points
</gallery>

==== Calligraphy Tool ====

* The tool now supports units for the width, with a much increased precision (up to three digits after the decimal separator, e.g. 0.005). The old, zoom-dependent width behavior is accessible with the unit '%'.

=== Dialogs ===
==== Preferences dialog ====

* Added new search bar in the preferences dialogue that performs a recursive search over all the nested categories of settings
<gallery mode="packed" heights=650px>

File:A search bar in the preferences dialogue.gif|search bar in the preferences

</gallery>
* press '''<code>F3</code>''' or '''<code>Ctrl+G</code>''' for next result
* press '''<code>Shit+F3</code>''' or '''<code>Ctrl+Shift+G</code>''' for previous result
New preferences:
* 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).
* In Edit > Preferences > Rendering > there is a new option to <code>Redraw while editing</code> that improves performance of redrawing with some faster CPUs ("Responsive", active by default)
* In Edit > Preferences > Interface > Keyboard, in the new '''Modifiers''' tab, you can customize keyboard shortcut modifiers for on-canvas mouse actions (for example holding Ctrl for scaling while keeping the object's aspect ratio can be changed to Shift) [Known issue: doesn't survive a restart]

==== 'About Inkscape' dialog ====

The Help > About Inkscape dialog has been rebuilt from scratch with a larger window (and image) and a tabbed interface.
* The user-contributed About Screen artwork is now displayed much larger, as it should be!
* Authors and translators are now featured on separate tabs.
* A new license tab offers a brief explanation of Inkscape licensing.
* All the tabs include calls to action or links to the official website for more information.
* The current version of Inkscape is displayed on a button. When clicked, the full version information is copied to the clipboard, so it can be used in bug reports, for example.

[[File:New about dialog.gif]]

=== Live path effects ===

==== Automatic fill preservation for path effects ====

LPEs which render strokes as fills (<code>Join Type</code>, <code>Power Stroke</code>, and <code>Taper Stroke</code>) have been modified to automatically preserve the previous fill by creating a linked path when applied to an object.

<gallery mode="packed" heights=250px>
File:Sadchrys original drawing with fill.png|Original drawing
File:Sadchrys after applying LPE previous versions.png|Previous versions of Inkscape would preserve the stroke settings but remove the fill when applied.
File:Sadchrys after applying LPE 1.1 original path.png|Now, Inkscape will automatically preserve the fill by creating a linked path underneath.
File:Sadchrys after applying LPE 1.1 linked fill.png|LPE options for the linked fill
</gallery>

==== "Taper Stroke" LPE ====

The Taper stroke LPE has been updated to include taper direction options (allowing the taper to run to one side of the path, instead of to the middle) and smoothing options for both ends of the path, allowing more interesting paths to be made in the effect. In addition, using the keybind '''Shift+click''' on the on-canvas knots allows quickly alternating between the different possible taper shapes.

<gallery mode="packed" heights=250px>
File:Taper stroke direction control.png|Direction control options
File:Taper stroke new parameter list.png|New parameter list
</gallery>

==== "Fill between many" LPE ====

A new shortcut has been added under the Path menu to automatically create a linked fill path using the '''Fill between many''' path effect. The effect is created beneath the selected paths and automatically selected to faciliate moving the path into the correct z-order and styling it as intended. For greater efficiency, the shortcut can also be bound to a hotkey using the '''Preferences''' dialog.

<gallery mode="packed" heights=250px>
File:Fill between many shortcut menuitem.png|Previously, using this effect required tediously copying every path to the clipboard and pasting it into the parameter list of a new path.
File:Fill between many result.png|Now, Inkscape can perform this task automatically, without any tedium.
</gallery>

==== "Offset" LPE ====

Offset calculation works faster now. Open paths can now have an offset that is not automatically closed [Known issue: when they don't self-intersect].

==== "Slice" LPE (new) ====

This new path effect allows you to split an object into two without destroying the original (or more by stacking multiple LPEs).
It works with groups, shapes, and paths. If you want to use it on Text, you need to use the 'Clone' LPE and apply the 'Slice' LPE on this clone.
[Known issue: crashes when one tries to edit the path]

[[File:Slice LPE 1.gif|800px|frameless]]

=== Extensions ===

== Notable bugfixes ==

=== Crash fixes ===

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

=== Other bug fixes ===

* The color selector's color wheel looks better now on HiDPI screens [https://gitlab.com/inkscape/inkscape/-/merge_requests/2416 MR #2416]
* The color indicator field in the bottom left corner of the window now uses a constant width and has been cleaned up a bit [https://gitlab.com/inkscape/inkscape/-/merge_requests/2400 MR #2400]
* The size of the double-arrow handles in the color sliders has been increased [https://gitlab.com/inkscape/inkscape/-/merge_requests/2427 MR #2427]
* Fix of multiple regressions and bugs with '''Stroke to path''' [https://gitlab.com/inkscape/inkscape/-/merge_requests/2410 MR #2410]
* Fix of feColorMatrix filter primitive default rendering [https://gitlab.com/inkscape/inkscape/-/merge_requests/2424 MR #2424]
* You can now just click in the color wheel to select a color [https://gitlab.com/inkscape/inkscape/-/merge_requests/2428 MR #2428]

=== Even 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).

== Breaking changes / Action required ==

=== Extensions ===

Element selections API has been improved, the API in 10 of using <code>self.svg.selected</code> is deprecated in favour of the new <code>self.svg.selection</code> interface. The previous API will continue to work for the time being but should be updated to the new API. Selection is now a type of ElementList which provides filtering, ordering and other generalised functionality, if you need an element list for example to make a bounding box, this is the way to do it.

== 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/1.0]] ([[Release_notes/1.0.1 |1.0.1]])
* [[Release notes/0.92]] ([[Release_notes/0.92.1 |0.92.1]], [[Release_notes/0.92.2 |0.92.2]], [[Release_notes/0.92.3 |0.92.3]], [[Release_notes/0.92.4 |0.92.4]], [[Release_notes/0.92.5 |0.92.5]])
* [[Release notes/0.91]]
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]], [[Release notes/0.48.4 | 0.48.4]], [[Release notes/0.48.5 | 0.48.5]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

Merge Requests

2020-11-07T14:12:08Z

Speleo3: title + description

This page is about [https://gitlab.com/inkscape/inkscape/ gitlab] merge request configuration.

== CI Timeout ==

Set the CI Timeout to 3h in your fork's settings at <pre>https://gitlab.com/<your_username>/inkscape/-/settings/ci_cd</pre> under the first heading 'General pipelines'.

[[File:Gitlab-ci-timeout.png]]

== Allow Rebasing ==
Enable "Allow commits from members who can merge to the target branch", this allows us to rebase your branch before merging.

[[File:Allow commits from members marked.png]]

== Title ==

Give your merge request a meaningful title. Not too long, details can go in the description.

== Description ==

Give your merge request a meaningful description which helps other developers to review and approve your code. In particular, "what" and "how" should be addressed.

If the MR fixes bug <code>#1234</code>, include this line (automatically closes the issue):

<source>
Fixes https://gitlab.com/inkscape/inkscape/-/issues/1234
</source>

If the MR is not fixing a bug but e.g. implementing a feature request with corresponding issue <code>#1234</code>, include:

<source>
Closes https://gitlab.com/inkscape/inkscape/-/issues/1234
</source>

[[Category:Developer Documentation]]

Dialog Manager

2020-06-30T18:20:46Z

Speleo3: comments

A page to discuss what a dialog manager should do (motivated by 2020 GSoC dialog work).

= Functions of Dialog Manager (or equivalent) =

# Keep a list of open dialogs (those attached to a notebook).
# Hide/show dialogs (notebooks).
# Update
## Floating dialogs when active window changes.
## Dialogs when document swapped.
## Dialogs when document changes(?).
# Delete (or hide) dialogs
## When closed directly.
## When notebook removed.
## When window is closed.
## When Inkscape closes (also save configuration).
# Track dialog meta-preferences. (Are there any?)

= Observations/Questions =

# The main code is in "ui/dialog/dialog-manager.h" and ...cpp.
# Dialogs, once created are not deleted (just hidden). (Verify)
:: ''They are deleted when the window closes (since [https://gitlab.com/inkscape/inkscape/-/merge_requests/1325 !1325]) --[[User:Speleo3|Speleo3]] ([[User talk:Speleo3|talk]])''
# "Behavior"
## Floating dialogs are those that cannot be docked. The Preference dialog is currently always floating.
## Docking dialogs are those that can be docked, either in an Inkscape Window or in a floating Dialog Window.
## There is a preference to set which to use.
## Using Gtk::Notebooks, we should support only "dock" dialogs. (And remove an unnecessary layer of abstraction.)
# The use of GQuark identify dialogs should be unnecessary. Use a std::map<std::string> where the string is the dialog name. (GQuark can be used for efficient look-ups but thats not needed for dialogs.)
# In desktop.cpp there are two variables "_dlg_mgr" and "_dlg_mgr_owned". It's not clear why. I could not get "Inkscape::UI::Dialog::DialogManager::getInstance() to return an instance.
:: ''I introduced <code>_dlg_mgr_owned</code> to distinguish between floating dialogs which are shared between multiple windows (like the Preferences Dialog) and those which are owned by a main window and should be destroyed along with it. --[[User:Speleo3|Speleo3]] ([[User talk:Speleo3|talk]])''
# The "PanelDialog" class handles linking dialogs to documents. It shouldn't be necessary, as we have a new (simpler) method of doing that.

Merge Requests

2020-06-20T07:35:57Z

Speleo3: created

This page is about [https://gitlab.com/inkscape/inkscape/ gitlab] merge request configuration.

== CI Timeout ==
Set the CI Timeout to 3h in your fork's settings.

[[File:Gitlab-ci-timeout.png]]

== Allow Rebasing ==
Enable "Allow commits from members who can merge to the target branch", this allows us to rebase your branch before merging.

[[File:Allow commits from members marked.png]]

[[Category:Developer Documentation]]

File:Allow commits from members marked.png

2020-06-20T07:31:59Z

Speleo3:

Gitlab merge request configuration

File:Gitlab-ci-timeout.png

2020-06-20T07:25:53Z

Speleo3:

Gitlab CI timeout configuration

Release notes/1.0.1

2020-06-04T19:15:36Z

Speleo3: milestone links

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

== Release highlights ==

'''Definitely not released yet.'''

Inkscape 1.0.1 is a stability and bugfix release.

<div style="padding: 20px; background-color: #9f9">
TODO: Collect from the '''Inkscape 1.0.1''' Milestone on gitlab:
* [https://gitlab.com/groups/inkscape/-/milestones/4 issues]
* [https://gitlab.com/groups/inkscape/-/milestones/4#tab-merge-requests merge requests]
</div>

The most notable improvements are:

* Fill in

== Important changes ==

=== For packagers ===

* Fill in

== Improvements ==

=== General User Interface ===

* Fill in

=== Canvas ===

* Fill in

=== Live Path Effects ===

* Fill in

=== Extensions ===

* Fill in

== Breaking changes / Action required ==

* 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/4 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:

* Fill in
* Language

The following documentation translations received updates:

* Fill in
* Language

=== Contributing to interface translations ===

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

== Documentation ==

* Fill in

=== 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]]

Release notes/1.1

2020-06-01T18:38:41Z

Speleo3: CorelDraw layers

Tracking Dependencies

2020-05-11T08:32:31Z

Speleo3: master GDL 3.6

== 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 19.10 (Eoan) EOL 2020-07
| 0.92.4
| 9.2.1
| 9.0
| 1.16
| 1.12.2
| 2.62.1
| 2.60.0
| 2.24.32 3.24.12
| 2.24.5 3.24.1
| 1.42.4
| 0.80
| 3.34.0
| 2.9.4
| 2.10.2
| 7.6.4
| 2.68.2
|-
| 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
|-
|libyaml
|[[Using_xverbs|xverbs command line options]]
|On
|-
|}

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

CustomGtk

2020-04-25T06:06:03Z

Speleo3: created

This page describes how to install a patched Gtk for development.

= On macOS with MacPorts =

# Install everything as usual, see [[CompilingMacOsX]]
# <code>sudo port install meson</code>
# Get Gtk source from stable branch <syntaxhighlight lang="bash">
git clone https://gitlab.gnome.org/GNOME/gtk.git
cd gtk
git checkout gtk-3-24
</syntaxhighlight>
# Optional: Apply patches
# Build and install directly into MacPorts tree, overwriting the system package <syntaxhighlight lang="bash">
mkdir -p build-meson
cd build-meson

PREFIX=/opt/local
export PATH="$PREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

meson \
--buildtype=release \
--prefix=$PREFIX \
..

ninja
sudo ninja install
sudo chown -R $USER .
</syntaxhighlight>

[[Category:Developer Documentation]]

Release notes/1.1

2020-04-18T14:54:48Z

Speleo3: XInclude support, dialogs

Compiling Inkscape on Windows with MSYS2

2020-04-05T11:01:54Z

Speleo3: syntaxhighlight

This page explains how to compile Inkscape on Windows using [http://www.msys2.org/ '''MSYS2'''].

MSYS2 does not only offer a convenient build environment for compiling Inkscape but also provides all necessary build tools and dependencies making it extremely simple to get started with Inkscape development.

== Installing MSYS2 ==

[[File:MSYS2 installer labelled.png|600px|thumb|Install MSYS2 '''64'''-bit (aka '''''x86_64'''''). Only use MSYS2 32-bit (aka ''i686'') if you have a 32-bit OS]]

[[File:MSYS2 shells.png|600px|thumb|
<div>Always use the proper shell
<ul>
<li>"MinGW 32-bit" for compiling 32-bit Inkscape</li>
<li>"MinGW 64-bit" for compiling 64-bit Inkscape</li>
<li>'''Never''' use the "MSYS" shell for compiling Inkscape, only use it for updating MSYS2 itself.</li>
</ul>
 
You can identify the different shells according to the the purple text string in the console window (<tt>MINGW32</tt>, <tt>MINGW64</tt> or <tt>MSYS</tt> respectively).
</div>]]

To set-up MSYS2 and download the necessary dependencies only two steps are required:
* '''Step 1''' — Install MSYS2
** Download the installer from the [http://www.msys2.org/ MSYS2 homepage] (The MSYS2 64-bit version is recommended on a 64-bit OS, see screenshot to the right. Both versions can compile 32-bit and 64-bit versions of Inkscape). Start the installation and follow the instructions on screen.
**After installation finished start an MSYS2 MSYS shell (you can work with the one launched by the installer, use the "MSYS2 MSYS" shortcut in the start menu or launch "msys2.exe" in the installation directory).
**Execute the command <code>pacman -Syuu</code>. This will start a full system upgrade and ensures that you have the latest versions of all core libraries (make sure to repeat this step until no new updates are found).
* '''Step 2''' — Download dependencies
** Start an MSYS2 MinGW shell (use the "MSYS2 MinGW 32/64-bit" shortcut in the start menu or launch "mingw32/64.exe" in the installation directory). Choose the shell in this step (32-bit or 64-bit) according to whether you want to build a 32-bit or 64-bit version of Inkscape later.
** Execute the script [https://gitlab.com/inkscape/inkscape/blob/master/buildtools/msys2installdeps.sh msys2installdeps.sh] by either copy-and-pasting it into the console or by downloading it and (after changing to the folder containing the file) typing <code>./msys2installdeps.sh</code>. If you already have a copy of the Inkscape source it should also be included in the "buildtools" folder.
Step 2 will take some time to complete (approx. 10 minutes depending on the speed of your internet connection and the load of the download servers), so relax and get a cup of coffee...

⚠️ ''Warning: Always make sure to use the proper MSYS2 shell (see screenshot to the right). Dependencies are separate for 32-bit and 64-bit Inkscape.''

 

== Obtaining Inkscape Source ==

''Note: For general instructions on how to use Git see [[Working with Git]].''

As MSYS2 provides the revision control software Git you do not need to download it separately. Simply open the MSYS2 MinGW shell and run the command
<pre>git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git master</pre>
This creates a folder called "master" in the current working directory (usually the home folder located at "C:\msys64\home\Your_Username" or similar) in which the clone of the source repository is created.

You can later update it with:
<pre>
git pull --recurse-submodules
</pre>

== Building Inkscape with MSYS2 ==

To compile Inkscape open the MSYS2 MinGW shell (remember to use the correct shell, i.e. 32-bit or 64-bit, matching the dependencies you downloaded above and the version of Inkscape you want to build).

Then execute the following commands:
<syntaxhighlight lang="bash">
# change to the directory containing your Inkscape source checkout (has to be adjusted to match your system)
cd master

# create a directory for the build (could also be another folder, but we'll assume 'build' being used for the rest of the article)
mkdir build
cd build

# create build files with CMake (we generate rules for "Ninja" as it's significantly faster then "MinGW Makefiles" which uses mingw32-make)
# note the source path '..' (which in this case is the parent directory) and should always point to the root folder of your copy of the Inkscape source
cmake -G Ninja ..

# start the compilation
ninja

# install compiled files and all dependencies required to run Inkscape into the folder 'build/inkscape/'
ninja install

# The last two steps can be combined (i.e. run 'ninja install' immediately) if you want to save time in future, as the "install" target also includes the default target
</syntaxhighlight>

'''''That's it!''''' 
Afterwards you should have a complete binary distribution of Inkscape in the folder "build/inkscape/" that can be run on any machine running Windows 7 or later.

== Packaging ==

If you only want to run Inkscape you do ''not'' need to follow these instructions. Simply execute <code>inkscape.exe</code> from the "build/inkscape/" directory created in the previous step, the <code>ninja install</code> command takes care of copying all required files into this directory.

To package those files for distribution (this should only concern package maintainers or people who want to improve the installer code) we offer a set of CMake convenience targets that can be executed as follows:
* <code>ninja dist-win-7z</code> – generate binary 7z archive. You'll need to install [http://www.7-zip.org/ 7-Zip].
* <code>ninja dist-win-exe</code> – generate .exe installer. You'll need to install [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)] version 3 or later.
* <code>ninja dist-win-msi</code> – generate .msi installer. You'll need to install [http://wixtoolset.org/ Windows Installer XML (WiX Toolset)].
* Additionally there's a <code>dist-win-all</code> target (executes all of the above in parallel) and for each of the three there's also a <code>dist-win-*-fast</code> target (which is identical in functionality but will use a faster compression method which will increase package size but will also significantly reduce packaging time which can be useful for debugging/development purposes).

For some additional details which have not been incorporated into this page yet see the previous instructions at [[Compiling Inkscape on Windows 32-bit#Creating an installer]] (might be partially oudated).

Hackfest2020 Rennes Attendees

2020-02-19T18:19:18Z

Speleo3:

Other pages: [[Hackfest2020 Rennes]], [[Hackfest2020 Rennes Topics]].

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Tavmjong Bah
| TBD
| Per SFC Rules
|
| By car
|
| By car
|
|-
| Cédric Gémy
| 
| Per SFC rules
| 
| 
| 
| 
|  Local
|-
| Elisa de Castro Guerra
| 
| Per SFC rules
| 
| 
| 
| 
|  Local
|-
| Thomas Holder (speleo3)
| TBD
| TBD
| 
| Train
| 
| Train
| 
|-
| Sample Person
| 
| TBD
| 
| 
| 
| 
| 
|-! Total
!
!
! $ TBD
!
!
!
!
!
|}

TBD: "To Be Determined"



Separate allocations for:
* Inkscape dinner, participants and guests (300€).
* Snacks, etc. (100€).
* Venue: Free.

1 Requires formality of board vote.

== Unconfirmed but Likely Attendees ==
== Maybe ==

== People to Invite ==

CompilingMacOsX

2020-01-02T10:14:23Z

Speleo3: remove outdated stuff

Notes on Packaging for OS X

2020-01-02T10:05:11Z

Speleo3: outdated

{{Needs_update}}

= Current Status =

; Available download
: Inkscape 0.91 [http://inkscape.org/en/download/mac-os/]

; Requirements
: XQuartz >= 2.5.1
: Mac OS X >= 10.5.8 (32bit app for Leopard and Snow Leopard, 64bit app for Lion and later)
: Python >= 2.5 (32bit) (provided by OS X) for extensions

; Known issues
: clipboard conflict with XQuartz (pastes as bitmap) - [https://bugs.launchpad.net/inkscape/+bug/307005 Bug #307005]
: language detection is faulty - [https://bugs.launchpad.net/inkscape/+bug/617079 #617079], [https://bugs.launchpad.net/inkscape/+bug/476678 #476678]
: missing: ps2pdf for Postscript input - [https://bugs.launchpad.net/inkscape/+bug/642522 Bug #642522](osx, win32)
: partial: spellchecker limited to English dictionary - [https://bugs.launchpad.net/inkscape/+bug/396322 Bug #396322]
: GIO-based clip art import not supported - [https://bugs.launchpad.net/inkscape/+bug/943148 Bug #943148]

; Known issues on specific versions of OS X
: Leopard: requires XQuartz >= 2.5.1 - [https://bugs.launchpad.net/inkscape/+bug/878368 Bug #878368]
: Lion and later: no support for Retina/HiDPI displays - [https://bugs.launchpad.net/inkscape/+bug/1216795 Bug #1216795]
: Mavericks and later: XQuartz conflict with multi-monitor setups - [https://bugs.launchpad.net/inkscape/+bug/1244397 Bug #1244397]
: Mavericks and later: embedding bitmap images on import or paste from clipboard may crash Inkscape - [https://bugs.launchpad.net/inkscape/+bug/1398521 Bug #1398521], [https://bugs.launchpad.net/inkscape/+bug/1410793 Bug #1410793]
: Mavericks and later: application bundle is not signed [https://bugs.launchpad.net/inkscape/+bug/1363305 Bug #1363305]

; Scripts & Resources in 'packaging/macosx' ([http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/files/head:/packaging/macosx/ stable], [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/packaging/macosx/ trunk])

= Roadmap =

; Provide packages built with GTK+/Quartz
: no requirement for X11/XQuartz
: OS integration (menubar, shortcuts, dock menu, proxy icon)
: improve language detection
: improve CLI usage
: include dbus (without launchd support), gvfs (clipart import, GTK3 file chooser)

; Extensions
: include ps2pdf (Ghostscript)
: offer packages (installer) for additional extensions and required dependencies

; User data (OS X guidelines <-> XDG spec)
: inkscape profile folder in "$HOME/Library/Application Support/"
: caches in "$HOME/Library/Caches"

= Future =

; Packages based on GTK3/Quartz
: OS X integration based on native GTK3 features
: support for HiDPI resolutions
: multi-threading (OpenMP support in future version of clang)
: 

= Recent efforts =

== 2012: Gellule Xg  ==

* Based on trunk (lp:inkscape r11619)
* dependencies via MacPorts
* ige-mac-integration for osx menubar
* ige-mac-bundler for osx app
* osx-build.sh updated, osx-app.sh obsolete, osx-dmg.sh new

; Status
: experimental, abandoned

; +
: simplified bundle structure
: easier bundling (script is developed & maintained upstream)
; -
: extensions not working in app bundle
: themeing not yet included

; Related blueprint
: [https://blueprints.launchpad.net/inkscape/+spec/inkscape-quartz A quartz version for OS X ]

; Related branch
: [https://code.launchpad.net/~inkscape.dev/inkscape/dev-osx lp:~inkscape.dev/inkscape/dev-osx]

; Related threads
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/36136 Subject: Some progress on OSX/aqua, and how to go further?]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/38933 Subject: Packaging for OSX]
: [http://inkscape.13.x6.nabble.com/Verbs-SPAction-versus-GtkAction-tt2806978.html Subject: Verbs+SPAction versus GtkAction]

; Related reports
: [https://bugs.launchpad.net/inkscape/+bug/738973 Bug #738973: Issues with inkscape-quartz blueprint]
: [https://bugs.launchpad.net/inkscape/+bug/1042597 Bug #1042597: gtk-mac-bundler: include python modules (and runtime) for extensions]
: [https://bugs.launchpad.net/inkscape/+bug/1043266 Bug #1043266: gtk-mac-integration support]
: [https://bugs.launchpad.net/inkscape/+bug/1043279 Bug #1043279: gtk-mac-bundler issues]
: [https://bugs.launchpad.net/inkscape/+bug/1045959 Bug #1045959: add DnD, 'Open with…' support for Dock & Finder icon]
: [https://bugs.launchpad.net/inkscape/+bug/1045963 Bug #1045963: add gtk-themes support]

== 2013: Valerio Aimale  ==

* Based on stable (lp:inkscape/0.48.x r9943)
* dependencies via MacPorts
* gtk-mac-integration for osx menubar, shortcuts, callbacks
* osx-build.sh, osx-app.sh updated
* script-based launcher (new)

; Status
: Release Candidate (RC5), abandoned

; +
: feature complete (including extensions, themeing)
: extensions: includes ps2pdf and UniConvertor, uses system Python
; -
: based on stable, not ported to trunk
: no source code available (RC builds cannot be recreated)
: gtk-mac-integration uses Quartz handlers (-> conflicts with keyboard input)
: depends on patched GTK+/Quartz stack for clipboard support
: no pasting of text in GUI widgets (XML Editor crashes on paste)

; Related threads
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39602 Subject: Mac OS X Mountain Lion x86_64 packaging of 0.48.4]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39602/focus=39631 Subject: Rejuvenated build system for Mac OS X]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39642 Subject: Inkscape and Mac OSX menu integration]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39644 Subject: Patch that allows use of Meta key on Mac OS X and all platforms]

; Related reports
: [https://bugs.launchpad.net/inkscape/+bug/1096996 Bug #1096996 Refreshed build system for Mac OS X ]
: [https://bugs.launchpad.net/inkscape/+bug/1097009 Bug #1097009 Better integration with Mac OS X OS ]
: [https://bugs.launchpad.net/inkscape/+bug/1097539 Bug #1097539 Actiavte the use of Meta|Command|WinFlag key for Mac Menu Accelerators ]

; RC build threads
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39667 Subject: Mac OS X Build 0.48.4 RC1]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39694 Subject: Mac OSX 0.48.4 RC2]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39707 Subject: Mac OSX 0.48.4 RC3]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39756 Subject: Mac OSX 0.48.4 RC4]
: [http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/39799 Subject: Mac OS X 0.48.4 RC5]

== 2014: osxmenu (~suv)  ==

* Based on (or cherry-picked from) Gellule's and Valerio's work
* Uses GTK+/Quartz backend in app bundle
* Supports gtk-mac-integration for integration with OS X global menu bar
* Supports dbus session bus
* New dark theme
* OS X friendly key bindings use Cmd instead of Ctrl
* … (TODO: more changes?)

; Status
: experimental, abandoned

; Known issues
: canvas redraws with Quartz backend are delayed (Screen recording [https://dl.dropboxusercontent.com/u/65084033/irc/Screen%20Recording%208.mp4 1],[https://dl.dropboxusercontent.com/u/65084033/irc/Screen%20Recording%209.mp4 2])
: exchanging drawing content with native apps via clipboard fails ([https://bugs.launchpad.net/inkscape/+bug/546934 lp:546934], [https://bugzilla.gnome.org/show_bug.cgi?id=692123 gtk:692123])

; Related branch
: [https://code.launchpad.net/~suv-lp/inkscape/osxmenu lp:~suv-lp/inkscape/osxmenu]

; Available download
: current link to available downloads on the [https://code.launchpad.net/~suv-lp/inkscape/osxmenu branch page] under 'Testing'

== 2014: osx-packaging-update (Liam P. White, ~suv)  ==

* Based on current scripts in 'packaging/macosx' (X11-based)
* Works with latest version of dependencies
* Allows creating bundle with quartz
* Supports compiling Platypus launcher on newer versions of OS X
* Uses modern Adwaita theme instead of Clearlooks-Quicksilver theme in stable bundles
* Fixes library rewriting
* Uses Python bundles from MacPorts prefix
* Adds wrapper script for GIMP.app

; Status
: [https://code.launchpad.net/~inkscape.dev/inkscape/osx-packaging-update/+merge/233846 Proposal] merged into trunk in revision [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/13620 13620]
: Update is included in the stable release branch [http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/files/head:/packaging/macosx/ 0.91.x].

; Related branch
: <strike>[https://code.launchpad.net/~inkscape.dev/inkscape/osx-packaging-update osx-packaging-update]</strike> (merged)

; Available download:
: Stable release packages: [https://inkscape.org/en/download/mac-os/ 0.91] (requires 10.5.8 or later)
: Unstable trunk packages: [https://www.dropbox.com/sh/2n7aim2wcrn6l3h/AADjQQ_484Z_Po1X3RSqa29na?dl=0 0.91+devel (DropBox)] (requires 10.7 or later)

Debugging Inkscape

2019-11-25T07:47:33Z

Speleo3: G_DEBUG=fatal-warnings

* If you're hunting down a GTK warning, run <code>G_DEBUG=fatal-warnings gdb inkscape</code> so you can capture a backtrace. ("run", "bt")

* If you're hunting down a g_assert, you can set a breakpoint in gdb for "g_assertion_message_expr" (or "g_assertion_message" maybe) to stop execution and make a backtrace.

* gdb can catch throwing of an exception. Type: "catch throw" and gdb will stop execution at the point of where the exception is thrown, without unwinding the stack, so you can get a backtrace!

* Bug list
- w32 version asks for (that crappy) Verdana typeface (which is not the most usual w32 typeface, also some users have deleted it to save disk space)

== Debugging Tips for OS X ==

When running the .app package for OS X, it can be difficult to get a backtrace because the application binary is launched through another application and 2 scripts. One way to get a backtrace is:
* Add '-g' to $CFLAGS in your build script before building.
* Remove the signal() calls (<code>segv_handler = signal (SIGSEGV,... </code>) ) in inkscape_application_init() in src/inkscape.cpp.
* In the Resources/bin/inkscpe script, change the last line from:
<code>exec "$CWD/inkscape-bin" "$@"</code>
to:
<code>exec "/usr/bin/gdb" "stuff/inkscape-bin"</code>
* Build and package the app (see [[CompilingMacOsX]]).
* Run the application in Terminal:
<code>
$ cd packaging/macosx
$ Inkscape.app/Contents/MacOS/Inkscape
...
(gdb) run
</code>

== Debugging Tips for Windows ==

First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Second, make use of the '''View > Messages...''' dialog from within the program. Capturing the log here will show you messages printed with g_message(), g_warning(), and g_error()..

Finally, look into [http://wiki.inkscape.org/wiki/index.php/FAQ#I.27m_on_Windows.2C_and_command_line_parameters_don.27t_seem_to_work.21 how to compile Inkscape as a command line app] so you can capture debug messages at the prompt, more like you would do in Linux.

===How Johan works===
Of course I am always compiling with [http://wiki.inkscape.org/wiki/index.php/FAQ#I.27m_on_Windows.2C_and_command_line_parameters_don.27t_seem_to_work.21 -mconsole, instead of -mwindows]. I don't compile with -g or any other extra flags. This is unnecessary and reduces build times significantly.

For example for crashes, usually I add g_message("blah") to the code to see where the execution of code goes and to see on which line things break:

g_message("1");
some_piece_of_code1();
g_message("2");
some_piece_of_code2();
g_message("3");
some_piece_of_code3();
g_message("4");
some_piece_of_code4();
g_message("5");

If I see the message "2" but not "3" I know the crash happened in some_piece_of_code2.

I also use GDB to get backtraces. Again, don't compile with -g. Not necessary at all! One of the problems with running Inkscape in gdb is that you cannot open a file with the file dialog: Inkscape will hang. I don't know the reason, but I do know a solution! Open the file through Inkscape's cmdline parameters:

D:\Inkscape\inkscape>gdb
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
(gdb) file inkscape.exe inkscape.dbg
Reading symbols from D:\Inkscape\inkscape/inkscape.exe...(no debugging symbols found)...done.
Reading symbols from D:\Inkscape\inkscape/inkscape.dbg...done.
(gdb) run Tekening.svg
Starting program: D:\Inkscape\inkscape/inkscape.exe Tekening.svg

===Example of how to fix a bug===
See this bugreport:
https://bugs.launchpad.net/inkscape/+bug/169135

I started gdb like above. And then I saw this:
Program received signal SIGSEGV, Segmentation fault.
0x005c94ec in Inkscape::UI::Widget::Scalar::setValue ()
(gdb) bt
#0 0x005c94ec in Inkscape::UI::Widget::Scalar::setValue ()
#1 0x0044fc11 in Inkscape::CanvasXYGrid::readRepr ()
#2 0x0044de22 in Inkscape::CanvasXYGrid::onReprAttrChanged ()

The crashing piece of code looked like this:

void Scalar::setValue(double value)
{
g_assert(_widget != NULL);
setProgrammatically = true; // callback is supposed to reset back, if it cares
static_cast<Gtk::SpinButton*>(_widget)->set_value(value);
}

Nothing much can crash there, the assert checks that _widget is not NULL, and then the cast is valid aswell. So what crashed? What happens is that the setValue method is called for an object that does not exist. _widget is not NULL, but "this" is! this->_widget would crash. g_assert (this != NULL) would give an assertion message. (checked by adding " if (this==NULL) g_message("ja hoor"); " )

It is absurd to check for "this" to be non-NULL at the start of every method, so the bug is not in this method but in the function calling it! That's why we turn our attention to Inkscape::CanvasXYGrid::readRepr ().

readRepr is long, but we only have to look where it does something with a Scalar widget. It's the validateScalar functions. When we comment those out, the bug is solved. (it causes another bug with the specific SVG file, where Inkscape hangs when the grid spacing equals zero. validateScalar used to check for that...)
The strange thing is that the widgets are all created and initialized in the constructor of CanvasXYGrid. So perhaps readRepr is being called *during* construction of CanvasXYGrid, while the Scalar widget is still invalid? Using the g_message tip above I found out that the problem code was:
sutemp = _rsu_sx.getSU();
g_message("CanvasXYGrid 1");
sutemp->setDigits(4);
g_message("CanvasXYGrid 2");

Researching the setDigits path, I could not find a bug. Then it hit me: _rsu_sx is initialized, then readRepr is called, but this is before _rsu_sy is initialized. Then

void RegisteredScalarUnit::setValue (double val)
{
_widget->setValue (val);
}

is called, but _widget is still NULL, hence the crash.
As usual, the fix is easy:
void RegisteredScalarUnit::setValue (double val)
{
if (_widget)
_widget->setValue (val);
}

Don't forget to fix the setValue methods of the other Registered widgets!!!

The fix can be seen in [http://inkscape.svn.sourceforge.net/viewvc/inkscape?view=rev&revision=16544 SVN revision 16544].

===Problems running GDB===
From an inexperienced user of GDB just trying to get backtraces, here is a tip I found running gdb.

I simply downloaded the latest version of Inkscape Dev full debug, extracted to a directory and ran gdb exactly as above from within the directory, only changing the name of the svg file.

Everything went exactly as above for "file inkscape.exe inkscape.dbg", however after executing the "run {filename.svg}" command, I received the following message;
Program received signal SIGSEV, Segmentation fault.
0x03de8cf1 in xslDebugStatus ()

This has stumped me once before, but this time I checked out the help menus, and found under "help running" that I could simply type "continue". I figured that xslDebugStatus was nothing to do with the Inkscape program itself, but more to do with gdb, and after typing "continue" it seems to run Inkscape under gdb as normal, allowing backtraces.

===guard32.dll error===
If you try to run gdb but it halts, complaining about guard32.dll, your Comodo Firewall installation is blocking gdb. Easiest way around this is to '''disable the Defense+ module completely''' -- open up Comodo Firewall, click on Defense+, Defense+ settings, set Security Level to "Disabled", and check "Deactivate the Defense+ permanently". Reboot.

== Debugging Tips for Linux ==

Debugging Inkscape on Linux is most easily done using Eclipse (or any other IDE). When however a breakpoint is reached while Inkscape is in a pointer grab (for example when dragging a control point or drawing a path), then X will stop responding. If you want to debug in such a case then you'll have to use gdb from the console. In Fedora 10 you'll get to the console when pressing ctrl-alt-F5. Now enter
declare -x DISPLAY=":0"
and startup gdb to load Inkscape and the debugging symbols, set your breakpoints, and start Inkscape. Now you can switch back to X (ctrl-alt-F1) and interact with Inkscape. When Inkscape stops responding because it hit a breakpoint, switch back to the console and do your debugging.

If you happen to run into some issues with one of the Gtk+ libraries and want to step through its code using the debugger, you will have to install its debugging symbols. For Fedora 10 you can simply enable the fedora-debuginfo repository in /etc/yum.repos.d/fedora.repo and then use yum to install for example the "gtk2-debuginfo" and "glib-debuginfo" package. For other distros you'll find some usefull information here:
http://live.gnome.org/GettingTraces/DistroSpecificInstructions

[[Category:Developer Documentation]]

MacOS alpha

2019-09-05T18:08:57Z

Speleo3: fix link

{| cellspacing="0" cellpadding="3" style="float: right; width: 30em; border: 1px solid #99f; background-color: #eee; text-align: left"
|-
!colspan="2" style="text-align:center; background-color: #99f"| Quick Links
|-
!style="vertical-align: top"| Download:
| Artifacts from latest "inkscape:mac" CI job: https://gitlab.com/inkscape/inkscape/-/jobs
|-
!style="vertical-align: top"| Issues:
| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS::macOS Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
|-
! Chat
| https://chat.inkscape.org/channel/team_devel_mac
|}

==Introduction==
So you have been (t)asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Thank you for your interest and the time you will be spending helping us out. Let me give you "the tour" about what's up ahead so you know what you'll be getting yourself into.

===Out with the old, in with the new===
Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase ([[Release_notes/1.0 |see release notes draft]]), there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing... I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!

==Testing==
There are many ways to approach this and you are free to do what you like (and we encourage you to do so), but let me give you some possibilities in case you are unsure how to get started.
* Use Inkscape 1.0 alpha as if it was the final release. Do your drawings and what you regularly do, but use the alpha version for it. This way you will notice if something is different/broken/slower/... than you are used to because you are in familiar territory. But don't forget that this release is not production-ready, so save your work more often to not have your day ruined if something unexpected happens.
* Just play around. Do things for fun, click through all the menus, go search for things that are new or that you have never used before. Make a copy of your most complex drawing you have ever done and open that copy in Inkscape alpha. Does it look like you would expect?
* ...whatever you can think of!

Generally speaking, the more you use and spend time with the alpha, the better. No one alone can and will find every bug, it's the joint effort of different people with different usage scenarios and different needs that will allow us to cover as much (testing-) ground as possible.

===Early testing group===
If you are part of the early testing group (you know if you are because you'll have been told), you are now crew members of the starship Enterprise: "to boldly go where noone has gone before". The releases you are about to test have not undergone any previous testing besides "draw a circle, a rectangle, add some text, save file". So not only are you probably going to see more bugs, you'll also (hopefully) encounter all the remaining foundational issues that would make Picard do the facepalm. For example, nobody has tested if printing still works. And these are the things we need to find out and fix before we announce any kind of public testing, or else we would get swamped with issues and complaints. Do not let it discourage you if you find major issues like that, it is important that you do. So be brave, put on your red shirt and join the away team! (Enough with the Star Trek references already!)

===Regular testing group===
If you are part of the regular testing group (you know if you are because you have not been told to put on a red shirt...), some brave men and women have <s>sacrificed their sanity</s> already been testing the alpha releases before you. That does not mean that you won't find any bugs, but hopefully there won't be any major blockers left that would stop you from testing after 5 minutes. But still, no guarantees.

==Downloading==
You can access and download the alpha builds directly from the CI pipeline. To do that, first go to https://gitlab.com/inkscape/inkscape. On the sidebar on the left you'll find a small rocket icon to access the <code>CI /CD</code> menu. Click on that and select <code>Pipelines</code>.

[[File:macos_alpha_ci_menu.png]]

Now choose the latest pipeline from the <code>master</code> branch (unless otherwise instructed). Take note of the version information besides the branch name, <code>5f7a1b48</code> in this example.

[[File:macos_alpha_ci_pipeline.png]]

Click on the download icon to the right to access the artifacts it has produced. Select the <code>Inkscape:mac</code> artifact to download.
(There are different kinds of build pipelines, not all of them produce a <code>Inkscape:mac</code> artifact.)

[[File:macos_alpha_ci_pipeline_artifacts.png]]

This will download a file named <code>artifacts.zip</code> to your computer. It includes <code>build/artifacts/Inkscape.app</code>. If you quicklook on the app you can confirm the version information.

[[File:macos_alpha_quicklook_version.png]]

===About Inkscape.app===
* The app is not signed. You have to <code>[right-click][Open]</code> the app due to Gatekeeper complaining about an unverified developer. (We're working on it!)
* Inkscape no longer requires X11, but proper macOS integration like the menubar is still on the todo list.

==Reporting issues==
Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one. There's also an introductory [https://inkscape.org/news/2019/02/02/step-step-video-launched-how-report-issue-inkscape/ video] to help you through the process.

Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):
* What macOS and Inkscape version are you using?
* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)
* Is it reproducible and can you list the steps in order to reproduce it?
* Can you supply a <code>demo.svg</code> to demonstrate the issue if necessary (i.e. not easily reproducible by other means)?
* What else do you find worth mentioning in context of the issue?

Your feedback and the time you put into it is greatly appreciated. It helps making Inkscape better for everyone. Every issue will be read and answered, but it might take us some time to get around. So please be patient if you don't get a response immediately and rest assured that your work is valuable and that you will hear from us.

Thank you!

==Contact==
If you have further questions about the macOS alpha test, there's https://chat.inkscape.org where we regularly hang out in <code>#team_devel_mac</code>.

CompilingMacOsX

2019-08-22T16:51:23Z

Speleo3: potrace, remove outdated troubleshooting

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc gettext libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
double-conversion \
gtk-osx-application-gtk3 \
potrace \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

= Using Homebrew =

[https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md See] for a collection of notes using homebrew infrastructure 🛣 to build Inkscape 1.x from master using CMake + Ninja

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* [github.com/ipatch] | A recent '''2019''' collection of notes about building Inkscape from master using CMake + Ninja | [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md Notes]
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

MacOS alpha

2019-07-11T21:26:57Z

Speleo3: scoped label

{| cellspacing="0" cellpadding="3" style="float: right; width: 30em; border: 1px solid #99f; background-color: #eee; text-align: left"
|-
!colspan="2" style="text-align:center; background-color: #99f"| Quick Links
|-
!style="vertical-align: top"| Download:
| Artifacts from latest "inkscape:mac" CI job: https://gitlab.com/inkscape/inkscape/-/jobs
|-
!style="vertical-align: top"| Issues:
| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS::Mac Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
|-
! Chat
| https://chat.inkscape.org/channel/team_devel_mac
|}

==Introduction==
So you have been (t)asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Thank you for your interest and the time you will be spending helping us out. Let me give you "the tour" about what's up ahead so you know what you'll be getting yourself into.

===Out with the old, in with the new===
Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase ([[Release_notes/1.0 |see release notes draft]]), there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing... I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!

==Testing==
There are many ways to approach this and you are free to do what you like (and we encourage you to do so), but let me give you some possibilities in case you are unsure how to get started.
* Use Inkscape 1.0 alpha as if it was the final release. Do your drawings and what you regularly do, but use the alpha version for it. This way you will notice if something is different/broken/slower/... than you are used to because you are in familiar territory. But don't forget that this release is not production-ready, so save your work more often to not have your day ruined if something unexpected happens.
* Just play around. Do things for fun, click through all the menus, go search for things that are new or that you have never used before. Make a copy of your most complex drawing you have ever done and open that copy in Inkscape alpha. Does it look like you would expect?
* ...whatever you can think of!

Generally speaking, the more you use and spend time with the alpha, the better. No one alone can and will find every bug, it's the joint effort of different people with different usage scenarios and different needs that will allow us to cover as much (testing-) ground as possible.

===Early testing group===
If you are part of the early testing group (you know if you are because you'll have been told), you are now crew members of the starship Enterprise: "to boldly go where noone has gone before". The releases you are about to test have not undergone any previous testing besides "draw a circle, a rectangle, add some text, save file". So not only are you probably going to see more bugs, you'll also (hopefully) encounter all the remaining foundational issues that would make Picard do the facepalm. For example, nobody has tested if printing still works. And these are the things we need to find out and fix before we announce any kind of public testing, or else we would get swamped with issues and complaints. Do not let it discourage you if you find major issues like that, it is important that you do. So be brave, put on your red shirt and join the away team! (Enough with the Star Trek references already!)

===Regular testing group===
If you are part of the regular testing group (you know if you are because you have not been told to put on a red shirt...), some brave men and women have <s>sacrificed their sanity</s> already been testing the alpha releases before you. That does not mean that you won't find any bugs, but hopefully there won't be any major blockers left that would stop you from testing after 5 minutes. But still, no guarantees.

==Downloading==
You can access and download the alpha builds directly from the CI pipeline. To do that, first go to https://gitlab.com/inkscape/inkscape. On the sidebar on the left you'll find a small rocket icon to access the <code>CI /CD</code> menu. Click on that and select <code>Pipelines</code>.

[[File:macos_alpha_ci_menu.png]]

Now choose the latest pipeline from the <code>master</code> branch (unless otherwise instructed). Take note of the version information besides the branch name, <code>5f7a1b48</code> in this example.

[[File:macos_alpha_ci_pipeline.png]]

Click on the download icon to the right to access the artifacts it has produced. Select the <code>Inkscape:mac</code> artifact to download.
(There are different kinds of build pipelines, not all of them produce a <code>Inkscape:mac</code> artifact.)

[[File:macos_alpha_ci_pipeline_artifacts.png]]

This will download a file named <code>artifacts.zip</code> to your computer. It includes <code>build/artifacts/Inkscape.app</code>. If you quicklook on the app you can confirm the version information.

[[File:macos_alpha_quicklook_version.png]]

===About Inkscape.app===
* The app is not signed. You have to <code>[right-click][Open]</code> the app due to Gatekeeper complaining about an unverified developer. (We're working on it!)
* Inkscape no longer requires X11, but proper macOS integration like the menubar is still on the todo list.

==Reporting issues==
Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one. There's also an introductory [https://inkscape.org/news/2019/02/02/step-step-video-launched-how-report-issue-inkscape/ video] to help you through the process.

Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):
* What macOS and Inkscape version are you using?
* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)
* Is it reproducible and can you list the steps in order to reproduce it?
* Can you supply a <code>demo.svg</code> to demonstrate the issue if necessary (i.e. not easily reproducible by other means)?
* What else do you find worth mentioning in context of the issue?

Your feedback and the time you put into it is greatly appreciated. It helps making Inkscape better for everyone. Every issue will be read and answered, but it might take us some time to get around. So please be patient if you don't get a response immediately and rest assured that your work is valuable and that you will hear from us.

Thank you!

==Contact==
If you have further questions about the macOS alpha test, there's https://chat.inkscape.org where we regularly hang out in <code>#team_devel_mac</code>.

C++11

2019-06-08T08:13:59Z

Speleo3: constexpr

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

{| class="wikitable"
|-
! Feature !! Can use? !! Comment
|-
| std::unique_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::scoped_ptr<> and std::auto_ptr<>
|-
| std::shared_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::shared_ptr<>
|-
| std::unordered_*<> || style="background: lightgreen;" | from 0.93|| Replaces the hack in util/unordered-containers.h
|-
| auto (type inference) || style="background: lightgreen;" | from 0.93 ||
|-
| enum class || not yet || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
|-
| range-based for || style="background: lightgreen;" | from 0.93 || Concise for loops with containers (Python alike)
|-
| lambda functions || not yet || In-place definitions for small functions
|-
| constructor delegation || not yet || Reduces boilerplate when an object has many constructors
|-
| right angle brackets in templates || not yet || Fixes coding style oddity
|-
| async, futures || not yet || Allows easy multithreading
|-
| std::initializer_list || not yet || Easier container initialization/assignation and implicit constructor calls
|-
| [https://en.cppreference.com/w/cpp/language/constexpr constexpr] || | ? || Additional meanings in C++14/C++17
|-
| toxic feature of doom || style="background: red;" | NO || Never use this (in case we stumble upon C++11 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 these pages:
* http://wiki.apache.org/stdcxx/C++0xCompilerSupport
* 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.

The table lists C++11 features and whether they work in trunk on a certain platform as advertised. If all lights are green ⇒ set the light to green in the Usage status section (taking current trunk version into account).

{| class="wikitable"
|-
! rowspan="2" | Feature !! Windows !! Mac 10.? !! macOS 10.14, Xcode 10 !! Fedora 20 !! Red Hat 7.0 !! Red Hat 6.5 !! rowspan="2" | Comment
|-
! TDM-GCC 4.6/4.9 (x64) !! ? !! Clang 10 !! GCC 4.8.2 !! GCC 4.8.2 !! GCC 4.4.7
|-
| unique_ptr<> || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || || Defined in <memory>
|-
| shared_ptr<> || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || || Defined in <memory>
|-
| auto || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|-
| enum class || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|-
| range-based for || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|-
| constexpr || | || || style="background: lightgreen;" | || | || | || ||
|}

Tracking Dependencies

2019-05-30T21:21:28Z

Speleo3: CompilingMacOsX link

== 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. Versions in parentheses refer to the dependencies for experimental Gtk+ 3 builds.

{| class="wikitable"
|-
! Library
! v 0.92
! trunk
|-
| Boehm-GC
| 7.2
| 7.2
|-
| Cairo
| 1.10
| 1.10
|-
| double-conversion [https://github.com/google/double-conversion] ''(lib2geom dependency)''
| ''(not required)''
| ?
|-
| GDL
| N/A (3.4)
| 3.4
|-
| Glib
| 2.28
| 2.48
|-
| GTK+
| 2.24 (3.8)
| 3.22
|-
| GNU Scientific Library
| ?
| ?
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
|-
| libSoup
| ''(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)
|-
| Poppler
| 0.20.0
| 0.20.0
|-
| [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 Debian Stable
* Support 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
! lcms
! 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
|-
| style="background:Orange; | Debian 8 (Jessie, oldstable) EOL 2020-05
| 0.48.5
| 4.9.2
| 3.5
| 1.14.0
| 1.10.0
| 2.42.1
| 2.42.0
| style="background:Orange; | 2.24.25 3.14.5
| style="background:Orange; | 2.24.4 3.14.0
| 1.36.8
| 0.26.5
| 3.14.0
| 2.6
| 2.4.0
| 7.2d
| 2.48.0
|-
| Debian 9 (Stretch, stable)
| 0.92.1
| 6.3.0
| 3.8
| 1.14.8
| 1.12.0
| 2.50.3
| 2.50.0
| 2.24.31 3.22.11
| 2.24.5 3.22.0
| 1.40.5
| 0.48.0
| 3.22.0
| 2.8
| 2.10.0
| 7.4.2
| 2.56.0
|-
| style="background:Violet;"|RHEL / CentOS 7.4
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.22.10
| 2.24.2 3.22.0
| 1.34.1
| 0.22.5
| style="background:Violet;"|X
| 2.5.4
| 2.3.1
| 7.2d
|-
| style="background:Orange; | Ubuntu 14.04 LTS (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| style="background:Orange; | 2.24.23 3.10.8
| style="background:Orange; | 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
| 2.44.2
|-
| style="background:Orange; | Ubuntu 16.04 LTS (Xenial) EOL 2021-04
| 0.91.0
| 5.3.1
| 3.8
| 1.14.6
| 1.12.0
| 2.48.0
| 2.46.3
| style="background:Orange; | 2.24.30 3.18.9
| style="background:Orange; | 2.24.4 3.18.0
| 1.38.1
| 0.41.0
| 3.18.0
| 2.6
| 2.6.2
| 7.4.2
| 2.52.2
|-
| Ubuntu 18.04 (Bionic) EOL 2023-04
| -
| 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.26.0?
| 2.9
| 2.10.0
| 7.4.2
| 2.62.1
|-
| Ubuntu 18.10 (Cosmic) EOL 2019-07
| -
| 8.2
| 6.0?
| 1.15.12
| 1.12.2
| 2.58.1
| 2.56.0
| 2.24.31 3.24.1
| 2.24.5 3.24.1
| 1.42.4
| 0.68.0
| 3.26.0?
| 2.9
| 2.10.0
| 7.6.4
| 2.64.1
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk 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 ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

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
|-
|gtkspell
|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
|-
|libpotrace
|Bucket fill, Trace bitmap
|On
|-
|scour
|Save as Optimized SVG
|(not needed during compiling, Python)
|-
|libvisio
|Open Visio Files, use Visio stencils
|On
|-
|libwpg
|Open WordPerfect Graphics
|On
|-
|libyaml
|[[Using_xverbs|xverbs command line options]]
|On
|-
|}

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

Tracking Dependencies

2019-05-30T21:19:53Z

Speleo3: gtk-mac-integration

== 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. Versions in parentheses refer to the dependencies for experimental Gtk+ 3 builds.

{| class="wikitable"
|-
! Library
! v 0.92
! trunk
|-
| Boehm-GC
| 7.2
| 7.2
|-
| Cairo
| 1.10
| 1.10
|-
| double-conversion [https://github.com/google/double-conversion] ''(lib2geom dependency)''
| ''(not required)''
| ?
|-
| GDL
| N/A (3.4)
| 3.4
|-
| Glib
| 2.28
| 2.48
|-
| GTK+
| 2.24 (3.8)
| 3.22
|-
| GNU Scientific Library
| ?
| ?
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
|-
| libSoup
| ''(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)
|-
| Poppler
| 0.20.0
| 0.20.0
|-
| [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 (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 Debian Stable
* Support 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
! lcms
! 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
|-
| style="background:Orange; | Debian 8 (Jessie, oldstable) EOL 2020-05
| 0.48.5
| 4.9.2
| 3.5
| 1.14.0
| 1.10.0
| 2.42.1
| 2.42.0
| style="background:Orange; | 2.24.25 3.14.5
| style="background:Orange; | 2.24.4 3.14.0
| 1.36.8
| 0.26.5
| 3.14.0
| 2.6
| 2.4.0
| 7.2d
| 2.48.0
|-
| Debian 9 (Stretch, stable)
| 0.92.1
| 6.3.0
| 3.8
| 1.14.8
| 1.12.0
| 2.50.3
| 2.50.0
| 2.24.31 3.22.11
| 2.24.5 3.22.0
| 1.40.5
| 0.48.0
| 3.22.0
| 2.8
| 2.10.0
| 7.4.2
| 2.56.0
|-
| style="background:Violet;"|RHEL / CentOS 7.4
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.22.10
| 2.24.2 3.22.0
| 1.34.1
| 0.22.5
| style="background:Violet;"|X
| 2.5.4
| 2.3.1
| 7.2d
|-
| style="background:Orange; | Ubuntu 14.04 LTS (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| style="background:Orange; | 2.24.23 3.10.8
| style="background:Orange; | 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
| 2.44.2
|-
| style="background:Orange; | Ubuntu 16.04 LTS (Xenial) EOL 2021-04
| 0.91.0
| 5.3.1
| 3.8
| 1.14.6
| 1.12.0
| 2.48.0
| 2.46.3
| style="background:Orange; | 2.24.30 3.18.9
| style="background:Orange; | 2.24.4 3.18.0
| 1.38.1
| 0.41.0
| 3.18.0
| 2.6
| 2.6.2
| 7.4.2
| 2.52.2
|-
| Ubuntu 18.04 (Bionic) EOL 2023-04
| -
| 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.26.0?
| 2.9
| 2.10.0
| 7.4.2
| 2.62.1
|-
| Ubuntu 18.10 (Cosmic) EOL 2019-07
| -
| 8.2
| 6.0?
| 1.15.12
| 1.12.2
| 2.58.1
| 2.56.0
| 2.24.31 3.24.1
| 2.24.5 3.24.1
| 1.42.4
| 0.68.0
| 3.26.0?
| 2.9
| 2.10.0
| 7.6.4
| 2.64.1
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk 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 ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

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
|-
|gtkspell
|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
|-
|libpotrace
|Bucket fill, Trace bitmap
|On
|-
|scour
|Save as Optimized SVG
|(not needed during compiling, Python)
|-
|libvisio
|Open Visio Files, use Visio stencils
|On
|-
|libwpg
|Open WordPerfect Graphics
|On
|-
|libyaml
|[[Using_xverbs|xverbs command line options]]
|On
|-
|}

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

MacOS alpha

2019-05-30T20:30:07Z

Speleo3: quick links

{| cellspacing="0" cellpadding="3" style="float: right; width: 30em; border: 1px solid #99f; background-color: #eee; text-align: left"
|-
!colspan="2" style="text-align:center; background-color: #99f"| Quick Links
|-
!style="vertical-align: top"| Download:
| Artifacts from latest "inkscape:mac" CI job: https://gitlab.com/inkscape/inkscape/-/jobs
|-
!style="vertical-align: top"| Issues:
| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS%2FMac Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
|-
! Chat
| https://chat.inkscape.org/channel/team_devel_mac
|}

==Introduction==
So you have been (t)asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Thank you for your interest and the time you will be spending helping us out. Let me give you "the tour" about what's up ahead so you know what you'll be getting yourself into.

===Out with the old, in with the new===
Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase ([[Release_notes/1.0 |see release notes draft]]), there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing... I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!

==Testing==
There are many ways to approach this and you are free to do what you like (and we encourage you to do so), but let me give you some possibilities in case you are unsure how to get started.
* Use Inkscape 1.0 alpha as if it was the final release. Do your drawings and what you regularly do, but use the alpha version for it. This way you will notice if something is different/broken/slower/... than you are used to because you are in familiar territory. But don't forget that this release is not production-ready, so save your work more often to not have your day ruined if something unexpected happens.
* Just play around. Do things for fun, click through all the menus, go search for things that are new or that you have never used before. Make a copy of your most complex drawing you have ever done and open that copy in Inkscape alpha. Does it look like you would expect?
* ...whatever you can think of!

Generally speaking, the more you use and spend time with the alpha, the better. No one alone can and will find every bug, it's the joint effort of different people with different usage scenarios and different needs that will allow us to cover as much (testing-) ground as possible.

===Early testing group===
If you are part of the early testing group (you know if you are because you'll have been told), you are now crew members of the starship Enterprise: "to boldly go where noone has gone before". The releases you are about to test have not undergone any previous testing besides "draw a circle, a rectangle, add some text, save file". So not only are you probably going to see more bugs, you'll also (hopefully) encounter all the remaining foundational issues that would make Picard do the facepalm. For example, nobody has tested if printing still works. And these are the things we need to find out and fix before we announce any kind of public testing, or else we would get swamped with issues and complaints. Do not let it discourage you if you find major issues like that, it is important that you do. So be brave, put on your red shirt and join the away team! (Enough with the Star Trek references already!)

===Regular testing group===
If you are part of the regular testing group (you know if you are because you have not been told to put on a red shirt...), some brave men and women have <s>sacrificed their sanity</s> already been testing the alpha releases before you. That does not mean that you won't find any bugs, but hopefully there won't be any major blockers left that would stop you from testing after 5 minutes. But still, no guarantees.

==Downloading==
You can access and download the alpha builds directly from the CI pipeline. To do that, first go to https://gitlab.com/inkscape/inkscape. On the sidebar on the left you'll find a small rocket icon to access the <code>CI /CD</code> menu. Click on that and select <code>Pipelines</code>.

[[File:macos_alpha_ci_menu.png]]

Now choose the latest pipeline from the <code>master</code> branch (unless otherwise instructed). Take note of the version information besides the branch name, <code>5f7a1b48</code> in this example.

[[File:macos_alpha_ci_pipeline.png]]

Click on the download icon to the right to access the artifacts it has produced. Select the <code>Inkscape:mac</code> artifact to download.
(There are different kinds of build pipelines, not all of them produce a <code>Inkscape:mac</code> artifact.)

[[File:macos_alpha_ci_pipeline_artifacts.png]]

This will download a file named <code>artifacts.zip</code> to your computer. It includes <code>build/artifacts/Inkscape.app</code>. If you quicklook on the app you can confirm the version information.

[[File:macos_alpha_quicklook_version.png]]

===About Inkscape.app===
* The app is not signed. You have to <code>[right-click][Open]</code> the app due to Gatekeeper complaining about an unverified developer. (We're working on it!)
* Inkscape no longer requires X11, but proper macOS integration like the menubar is still on the todo list.

==Reporting issues==
Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.

Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):
* What macOS and Inkscape version are you using?
* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)
* Is it reproducible and can you list the steps in order to reproduce it?
* Can you supply a <code>demo.svg</code> to demonstrate the issue if necessary (i.e. not easily reproducible by other means)?
* What else do you find worth mentioning in context of the issue?

Your feedback and the time you put into it is greatly appreciated. It helps making Inkscape better for everyone. Every issue will be read and answered, but it might take us some time to get around. So please be patient if you don't get a response immediately and rest assured that your work is valuable and that you will hear from us.

Thank you!

==Contact==
If you have further questions about the macOS alpha test, there's https://chat.inkscape.org where we regularly hang out in <code>#team_devel_mac</code>.

CompilingMacOsX

2019-05-30T18:05:26Z

Speleo3: intltool -> gettext

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc gettext libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
double-conversion \
gtk-osx-application-gtk3 \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

== Troubleshooting ==

Linking fails with:

ld: framework not found -lCocoa

A patch like this should help (reverts part of
[https://gitlab.com/inkscape/inkscape/commit/48e6c2ea4fc0245afc35cbbc6563804abf421ccd 48e6c2ea4f], see also
[https://gitlab.com/inkscape/inkscape/merge_requests/397 !397]):

<syntaxhighlight lang="diff">
diff --git a/CMakeScripts/DefineDependsandFlags.cmake b/CMakeScripts/DefineDependsandFlags.cmake
index 4cb63aae80..7a0b5cbc75 100644
--- a/CMakeScripts/DefineDependsandFlags.cmake
+++ b/CMakeScripts/DefineDependsandFlags.cmake
@@ -253,7 +253,7 @@ pkg_check_modules(GTKSPELL3 gtkspell3-3.0)
if("${GTKSPELL3_FOUND}")
message(STATUS "Using GtkSpell 3")
list(APPEND INKSCAPE_INCS_SYS ${GTKSPELL3_INCLUDE_DIRS})
- list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LDFLAGS})
+ list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LIBRARIES})
set(WITH_GTKSPELL ON)
else()
set(WITH_GTKSPELL OFF)
</syntaxhighlight>

= Using Homebrew =

[https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md See] for a collection of notes using homebrew infrastructure 🛣 to build Inkscape 1.x from master using CMake + Ninja

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* [github.com/ipatch] | A recent '''2019''' collection of notes about building Inkscape from master using CMake + Ninja | [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md Notes]
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

CompilingMacOsX

2019-05-30T09:46:48Z

Speleo3: gitlab CI no longer uses homebrew

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
double-conversion \
gtk-osx-application-gtk3 \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

== Troubleshooting ==

Linking fails with:

ld: framework not found -lCocoa

A patch like this should help (reverts part of
[https://gitlab.com/inkscape/inkscape/commit/48e6c2ea4fc0245afc35cbbc6563804abf421ccd 48e6c2ea4f], see also
[https://gitlab.com/inkscape/inkscape/merge_requests/397 !397]):

<syntaxhighlight lang="diff">
diff --git a/CMakeScripts/DefineDependsandFlags.cmake b/CMakeScripts/DefineDependsandFlags.cmake
index 4cb63aae80..7a0b5cbc75 100644
--- a/CMakeScripts/DefineDependsandFlags.cmake
+++ b/CMakeScripts/DefineDependsandFlags.cmake
@@ -253,7 +253,7 @@ pkg_check_modules(GTKSPELL3 gtkspell3-3.0)
if("${GTKSPELL3_FOUND}")
message(STATUS "Using GtkSpell 3")
list(APPEND INKSCAPE_INCS_SYS ${GTKSPELL3_INCLUDE_DIRS})
- list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LDFLAGS})
+ list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LIBRARIES})
set(WITH_GTKSPELL ON)
else()
set(WITH_GTKSPELL OFF)
</syntaxhighlight>

= Using Homebrew =

[https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md See] for a collection of notes using homebrew infrastructure 🛣 to build Inkscape 1.x from master using CMake + Ninja

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* [github.com/ipatch] | A recent '''2019''' collection of notes about building Inkscape from master using CMake + Ninja | [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md Notes]
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

CompilingMacOsX

2019-05-30T09:45:02Z

Speleo3: gtk-osx-application-gtk3

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
double-conversion \
gtk-osx-application-gtk3 \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

== Troubleshooting ==

Linking fails with:

ld: framework not found -lCocoa

A patch like this should help (reverts part of
[https://gitlab.com/inkscape/inkscape/commit/48e6c2ea4fc0245afc35cbbc6563804abf421ccd 48e6c2ea4f], see also
[https://gitlab.com/inkscape/inkscape/merge_requests/397 !397]):

<syntaxhighlight lang="diff">
diff --git a/CMakeScripts/DefineDependsandFlags.cmake b/CMakeScripts/DefineDependsandFlags.cmake
index 4cb63aae80..7a0b5cbc75 100644
--- a/CMakeScripts/DefineDependsandFlags.cmake
+++ b/CMakeScripts/DefineDependsandFlags.cmake
@@ -253,7 +253,7 @@ pkg_check_modules(GTKSPELL3 gtkspell3-3.0)
if("${GTKSPELL3_FOUND}")
message(STATUS "Using GtkSpell 3")
list(APPEND INKSCAPE_INCS_SYS ${GTKSPELL3_INCLUDE_DIRS})
- list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LDFLAGS})
+ list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LIBRARIES})
set(WITH_GTKSPELL ON)
else()
set(WITH_GTKSPELL OFF)
</syntaxhighlight>

= Using Homebrew =

The Inkscape CI job uses homebrew, see [https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L51-71 .gitlab-ci.yml]

[https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md See] for a collection of notes using homebrew infrastructure 🛣 to build Inkscape 1.x from master using CMake + Ninja

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* [github.com/ipatch] | A recent '''2019''' collection of notes about building Inkscape from master using CMake + Ninja | [https://github.com/ipatch/homebrew-us-05/blob/master/inkscape/inkscape-building-for-macOS.md Notes]
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

C++11

2019-05-27T06:35:26Z

Speleo3: macOS

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

{| class="wikitable"
|-
! Feature !! Can use? !! Comment
|-
| std::unique_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::scoped_ptr<> and std::auto_ptr<>
|-
| std::shared_ptr<> || style="background: lightgreen;" | from 0.93 || Replaces boost::shared_ptr<>
|-
| std::unordered_*<> || style="background: lightgreen;" | from 0.93|| Replaces the hack in util/unordered-containers.h
|-
| auto (type inference) || style="background: lightgreen;" | from 0.93 ||
|-
| enum class || not yet || Strong enum constants (take the name of the enum, can't be implicitly converted to <code>int</code>)
|-
| range-based for || style="background: lightgreen;" | from 0.93 || Concise for loops with containers (Python alike)
|-
| lambda functions || not yet || In-place definitions for small functions
|-
| constructor delegation || not yet || Reduces boilerplate when an object has many constructors
|-
| right angle brackets in templates || not yet || Fixes coding style oddity
|-
| async, futures || not yet || Allows easy multithreading
|-
| std::initializer_list || not yet || Easier container initialization/assignation and implicit constructor calls
|-
| toxic feature of doom || style="background: red;" | NO || Never use this (in case we stumble upon C++11 features that we really don't like)
|-
| supported feature || style="background: lightgreen;" | from 0.93 ||
|}

== Platform status ==

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

Also see these pages:
* http://wiki.apache.org/stdcxx/C++0xCompilerSupport
* 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.

The table lists C++11 features and whether they work in trunk on a certain platform as advertised. If all lights are green ⇒ set the light to green in the Usage status section (taking current trunk version into account).

{| class="wikitable"
|-
! rowspan="2" | Feature !! Windows !! Mac 10.? !! macOS 10.14, Xcode 10 !! Fedora 20 !! Red Hat 7.0 !! Red Hat 6.5 !! rowspan="2" | Comment
|-
! TDM-GCC 4.6/4.9 (x64) !! ? !! Clang 10 !! GCC 4.8.2 !! GCC 4.8.2 !! GCC 4.4.7
|-
| unique_ptr<> || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || || Defined in <memory>
|-
| shared_ptr<> || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || || Defined in <memory>
|-
| auto || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|-
| enum class || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|-
| range-based for || style="background: lightgreen;" | || || style="background: lightgreen;" | || style="background: lightgreen;" | || style="background: lightgreen;" | || ||
|}

Hackfest2019 Saarbrücken Attendees

2019-05-01T08:24:38Z

Speleo3: fix train number

Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]].

Note:

For the 27th and 28th, there can be no more than 20 persons in k8's office! If there are more, they would need to find a different place to meet (e.g. in a hotel room, or ask someone local).

On 29th, those persons that staff the booth in the Open Source event can be discounted from the cap (currently 3).

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Tavmjong Bah
| 5/27, 5/28, 5/29, 5/30, 6/1, (6/2)
| TBD
| 
| 
| 
| 
| 
|-
| Thomas Holder
| 5/27, 5/28, 5/29
| TBD
| 5/26 16:15
| RE 4127 (train)
| 5/29 18:59
| ICE 9555 (train)
| Airbnb
|-
| Jabier Arraiza
| 5/27, 5/28, 5/29, 5/30, 6/1, 6/2
| TBD
| 
| 
| 
| 
| 
|-
| Mihaela Jurković
| 5/28 (?), 5/29, 5/30, 6/1, 6/2
| TBD
| 
| 
| 
| 
| 
|-
| Marc Jeanmougin
| 
| TBD
| 
| 
| 
| 
| 
|-
| Jürgen Weigert
| 5/27, ?
| TBD
|  5/26
| 
| 
| 
| 
|-
| Tobias Ellinghaus
| 
| (no travel or accomodation assistance is needed)
| local
| 
| local
| 
| local
|-
| Cédric Gémy
| 
| TBD
|  5/28 (evening)
| 
| 
| 
| 
|-
| Elisa de Castro Guerra
| 
| TBD
|  5/28 (evening)
| 
| 
| 
| 
|-
| Boudewijn Rempt
| 
| (no travel or accomodation assistance is needed)
| 
| 
| 
| 
| 
|-
| René de Hesselle
| 5/27, 5/28, 5/29
| TBD
| 
| 
| 
| 
| 
|-
| Max Gaukler
| probably: 5/27, 5/28, 5/29
| (no travel or accomodation assistance is needed)
| 
| 
| 
| 
| 
|-
| Alex Valavanis
| 5/27, 5/28, 5/29
| TBD
| 5/26 1400 (Frankfurt)
| LH943 (Manchester to Frankfurt)
| 5/30 1650 (Frankfurt)
| LH946 (Frankfurt to Manchester)
| Motel One
|-
| Sample Person
| 
| TBD
| 
| 
| 
| 
| 
|-! Total
!
!
! $ TBD
!
!
!
!
!
|}

TBD: "To Be Determined"

The Inkscape board has approved travel reimbursements of up to $2000 per person. Note: participants require the formality of a board vote.

Separate allocations for:
* Inkscape dinner, participants and guests (300€).
* Snacks, etc. (100€).
* Venue: Free.

1 Requires formality of board vote.

== Unconfirmed but Likely Attendees ==

* Alexandre Prokoudine (during LGM as visitor/guest)

== Maybe ==

* ede123 (Patrick)
* Thomas Wiesner (@wiesi on gitlab, python console, attendence very unlikely)
* Maren Hachmann

== People to Invite ==

* Shlomi Fish
* Anatoly (@techtonik on gitlab)
* Olli (https://gitlab.com/ollip)
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)
* Khaled Hosny (font expert)
* Antonio Hospite (https://gitlab.com/ao2)
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)
* Simon Wells (https://gitlab.com/xzcvczx)
* Nicolas

* Juan Duarte (see chat.inkscape.org) - invited for LGM via chat
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/) - invited via email

* probono - invited via chat
* Markus Schwienbacher - invited via gitlab
* su_v - invited via email

* <s>Sven Ebert (aka Dillerkind) - invited via forum</s>
* <s>Johan Engelen - invited via email, can't attend</s>
* <s>Martin Owens: can't attend</s>
* <s>Bryce Harrington: can't attend</s>

Possible others?
* people on the mac-devel channel

== Organizational info ==

We need to report the rough number of attendees to k8 by mid
May.

Hackfest2019 Saarbrücken Attendees

2019-05-01T08:22:42Z

Speleo3: travel details

Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]].

Note:

For the 27th and 28th, there can be no more than 20 persons in k8's office! If there are more, they would need to find a different place to meet (e.g. in a hotel room, or ask someone local).

On 29th, those persons that staff the booth in the Open Source event can be discounted from the cap (currently 3).

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Tavmjong Bah
| 5/27, 5/28, 5/29, 5/30, 6/1, (6/2)
| TBD
| 
| 
| 
| 
| 
|-
| Thomas Holder
| 5/27, 5/28, 5/29
| TBD
| 5/26 16:15
| RE 4127 (train)
| 5/29 18:59
| ICE 4127 (train)
| Airbnb
|-
| Jabier Arraiza
| 5/27, 5/28, 5/29, 5/30, 6/1, 6/2
| TBD
| 
| 
| 
| 
| 
|-
| Mihaela Jurković
| 5/28 (?), 5/29, 5/30, 6/1, 6/2
| TBD
| 
| 
| 
| 
| 
|-
| Marc Jeanmougin
| 
| TBD
| 
| 
| 
| 
| 
|-
| Jürgen Weigert
| 5/27, ?
| TBD
|  5/26
| 
| 
| 
| 
|-
| Tobias Ellinghaus
| 
| (no travel or accomodation assistance is needed)
| local
| 
| local
| 
| local
|-
| Cédric Gémy
| 
| TBD
|  5/28 (evening)
| 
| 
| 
| 
|-
| Elisa de Castro Guerra
| 
| TBD
|  5/28 (evening)
| 
| 
| 
| 
|-
| Boudewijn Rempt
| 
| (no travel or accomodation assistance is needed)
| 
| 
| 
| 
| 
|-
| René de Hesselle
| 5/27, 5/28, 5/29
| TBD
| 
| 
| 
| 
| 
|-
| Max Gaukler
| probably: 5/27, 5/28, 5/29
| (no travel or accomodation assistance is needed)
| 
| 
| 
| 
| 
|-
| Alex Valavanis
| 5/27, 5/28, 5/29
| TBD
| 5/26 1400 (Frankfurt)
| LH943 (Manchester to Frankfurt)
| 5/30 1650 (Frankfurt)
| LH946 (Frankfurt to Manchester)
| Motel One
|-
| Sample Person
| 
| TBD
| 
| 
| 
| 
| 
|-! Total
!
!
! $ TBD
!
!
!
!
!
|}

TBD: "To Be Determined"

The Inkscape board has approved travel reimbursements of up to $2000 per person. Note: participants require the formality of a board vote.

Separate allocations for:
* Inkscape dinner, participants and guests (300€).
* Snacks, etc. (100€).
* Venue: Free.

1 Requires formality of board vote.

== Unconfirmed but Likely Attendees ==

* Alexandre Prokoudine (during LGM as visitor/guest)

== Maybe ==

* ede123 (Patrick)
* Thomas Wiesner (@wiesi on gitlab, python console, attendence very unlikely)
* Maren Hachmann

== People to Invite ==

* Shlomi Fish
* Anatoly (@techtonik on gitlab)
* Olli (https://gitlab.com/ollip)
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)
* Khaled Hosny (font expert)
* Antonio Hospite (https://gitlab.com/ao2)
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)
* Simon Wells (https://gitlab.com/xzcvczx)
* Nicolas

* Juan Duarte (see chat.inkscape.org) - invited for LGM via chat
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/) - invited via email

* probono - invited via chat
* Markus Schwienbacher - invited via gitlab
* su_v - invited via email

* <s>Sven Ebert (aka Dillerkind) - invited via forum</s>
* <s>Johan Engelen - invited via email, can't attend</s>
* <s>Martin Owens: can't attend</s>
* <s>Bryce Harrington: can't attend</s>

Possible others?
* people on the mac-devel channel

== Organizational info ==

We need to report the rough number of attendees to k8 by mid
May.

CompilingMacOsX

2019-04-03T17:41:08Z

Speleo3: double-conversion

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
double-conversion \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

== Troubleshooting ==

Linking fails with:

ld: framework not found -lCocoa

A patch like this should help (reverts part of
[https://gitlab.com/inkscape/inkscape/commit/48e6c2ea4fc0245afc35cbbc6563804abf421ccd 48e6c2ea4f], see also
[https://gitlab.com/inkscape/inkscape/merge_requests/397 !397]):

<syntaxhighlight lang="diff">
diff --git a/CMakeScripts/DefineDependsandFlags.cmake b/CMakeScripts/DefineDependsandFlags.cmake
index 4cb63aae80..7a0b5cbc75 100644
--- a/CMakeScripts/DefineDependsandFlags.cmake
+++ b/CMakeScripts/DefineDependsandFlags.cmake
@@ -253,7 +253,7 @@ pkg_check_modules(GTKSPELL3 gtkspell3-3.0)
if("${GTKSPELL3_FOUND}")
message(STATUS "Using GtkSpell 3")
list(APPEND INKSCAPE_INCS_SYS ${GTKSPELL3_INCLUDE_DIRS})
- list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LDFLAGS})
+ list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LIBRARIES})
set(WITH_GTKSPELL ON)
else()
set(WITH_GTKSPELL OFF)
</syntaxhighlight>

= Using Homebrew =

The Inkscape CI job uses homebrew, see [https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L51-71 .gitlab-ci.yml]

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

Hackfest2019 Saarbrücken Attendees

2019-03-20T17:47:16Z

Speleo3: confirmed

Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]].

== Confirmed Attendees ==

* Boudewijn Rempt (no travel or accomodation assistance is needed)
* Cedric and Elisa (arrival 28th evening)
* Tavmjong Bah (27th-2nd, may need to leave on 1st)
* Thomas Holder (27-29)

== Unconfirmed but Likely Attendees ==

* Marc Jeanmougin
* Jürgen Weigert (arrival May-29th afternoon)
* Max Gaukler
* Tobias Ellinghaus (houz) - local
* Maren Hachmann
* Mihaela Jurković (prkos) (Tue 28? - Sun 02)

== Maybe ==

== People to Invite ==

* ede123 (Patrick)
* prkos (Mihaela)
* Shlomi Fish
* Jabier
* Martin Owens
* Anatoly (@techtonik on gitlab)
* Thomas Wiesner (@wiesi on gitlab)
* Juan Duarte (see chat.inkscape.org)
* Olli (https://gitlab.com/ollip)
* Alex Valavanis
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/)
* Alexandre Prokoudine (as guest? Might be there anyway.)
* Khaled Hosny (font expert)
* Antonio Hospite (https://gitlab.com/ao2)
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)
* Simon Wells (https://gitlab.com/xzcvczx)
* probono
* Nicolas
* su_v
* Johan Engelen
* Bryce Harrington

Possible others?
* people on the mac-devel channel

Hackfest2019 Saarbrücken Attendees

2019-03-07T21:42:45Z

Speleo3: speleo3

Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]].

== Confirmed Attendees ==

== Unconfirmed but Likely Attendees ==

* Marc Jeanmougin
* Tavmjong Bah
* Jürgen Weigert (arrival May-29th afternoon)
* Max Gaukler
* Tobias Ellinghaus (houz) - local
* Maren Hachmann
* Thomas Holder (speleo3)

== Maybe ==

== People to Invite ==

* ede123 (Patrick)
* prkos (Mihaela)
* Shlomi Fish
* Jabier
* Martin Owens
* Anatoly (@techtonik on gitlab)
* Thomas Wiesner (@wiesi on gitlab)
* Juan Duarte (see chat.inkscape.org)
* Olli (https://gitlab.com/ollip)
* Alex Valavanis
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/)
* Alexandre Prokoudine (as guest? Might be there anyway.)
* Khaled Hosny (font expert)
* Antonio Hospite (https://gitlab.com/ao2)
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)
* Simon Wells (https://gitlab.com/xzcvczx)
* probono
* Nicolas
* su_v
* Johan Engelen
* Bryce Harrington

Possible others?
* people on the mac-devel channel

CompilingMacOsX

2019-02-15T09:37:30Z

Speleo3: Troubleshooting framework not found -lCocoa

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

== Troubleshooting ==

Linking fails with:

ld: framework not found -lCocoa

A patch like this should help (reverts part of
[https://gitlab.com/inkscape/inkscape/commit/48e6c2ea4fc0245afc35cbbc6563804abf421ccd 48e6c2ea4f], see also
[https://gitlab.com/inkscape/inkscape/merge_requests/397 !397]):

<syntaxhighlight lang="diff">
diff --git a/CMakeScripts/DefineDependsandFlags.cmake b/CMakeScripts/DefineDependsandFlags.cmake
index 4cb63aae80..7a0b5cbc75 100644
--- a/CMakeScripts/DefineDependsandFlags.cmake
+++ b/CMakeScripts/DefineDependsandFlags.cmake
@@ -253,7 +253,7 @@ pkg_check_modules(GTKSPELL3 gtkspell3-3.0)
if("${GTKSPELL3_FOUND}")
message(STATUS "Using GtkSpell 3")
list(APPEND INKSCAPE_INCS_SYS ${GTKSPELL3_INCLUDE_DIRS})
- list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LDFLAGS})
+ list(APPEND INKSCAPE_LIBS ${GTKSPELL3_LIBRARIES})
set(WITH_GTKSPELL ON)
else()
set(WITH_GTKSPELL OFF)
</syntaxhighlight>

= Using Homebrew =

The Inkscape CI job uses homebrew, see [https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L51-71 .gitlab-ci.yml]

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

CompilingMacOsX

2019-01-15T18:10:47Z

Speleo3: remove popt

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

= Using Homebrew =

The Inkscape CI job uses homebrew, see [https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L51-71 .gitlab-ci.yml]

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]

Release notes/1.0

2018-12-25T09:08:42Z

Speleo3: Pinch-to-zoom

{{Other languages|en=Release_notes/1.0}}

== Inkscape 1.0 ==

'''(definitely not released yet - [[AnnouncePlanning1.0]])'''

== Release highlights ==

Released on '''«YYYY-MM-DD»'''.

[Please fill in

* Themeing support
* Origin in top left corner (optional)
* Canvas rotation and mirroring
* Better hidpi screen support
* Control width of PowerStroke with pressure sensitive graphics tablet
* Fillet/chamfer LPE
* New PNG export options]

== Important changes ==

=== For users ===

==== Custom Icon Sets ====

Icon sets do no longer consist of a single file that contains all icons, but of single files for each icon. The directory structure must follow the standard structure for gnome icons.

If you would like to create or convert your own icon set to the new format, please see the 'hicolor' and 'Tango' icon theme folders in your Inkscape installation 'share' directory for suitable examples.

As a side effect of a bug fix to the icon preview dialog (see below), custom UI icon SVG files need to be updated to have their background color alpha channel set to 0 so that they display correctly (see Bug #[https://bugs.launchpad.net/inkscape/+bug/1661989 1661989]).

==== Third-party extensions ====

Third-party extensions need to be updated to work with this version of Inkscape.

=== For extension writers ===

''[TBC - not final]''
Extensions have undergone some fundamental changes.
Inkscape's stock extensions have been moved to [https://gitlab.com/inkscape/extensions their own repository] and were updated for compatibility with Python 3. Internally, extensions have been reorganized and many functions have been deprecated.

''[Extension manager? How-to-guide for updating? New API elements? Documentation?]''

Instructions for updating old extensions are available at [[Updating your Extension for 1.0]]

Also note the changed [[#Command Line|command line options]].

=== For packagers and those who compile Inkscape ===

* autotools builds have been dropped. Please use CMake for building Inkscape from now on. More info is available [https://inkscape.org/develop/getting-started/#092-onwards on our website].
* libsoup dependency added: we use libsoup for making http requests without the need for dbus and gvfs.
* Inkscape now uses a git submodule for the extensions directory. If you have cloned the repository and are not building from the release source code tarball, please note the [https://inkscape.org/en/develop/getting-started/ updated build instructions]]
* On Ubuntu 18.04, Gnome's fallback icon set (package 'adwaita-icon-theme-full'), that is needed to display Inkscape's default icons completely, is no longer automatically installed. It has been added as a 'recommends' level dependency.
* lib2geom: [insert up-to-date info here]

== General User Interface ==

The user interface has been changed to using a more recent version of GTK+, the widget toolkit that Inkscape uses to draw the user interface on the screen. This new version brings a lot of improvements, especially for users of hidpi screens. Updating Inkscape for using it has been a large effort that has been anticipated eagerly for a long time, and was a focus of the [https://inkscape.org/en/news/2018/05/22/2018-boston-inkscape-hackfest/ Boston Hackfest].

=== Window position / size ===

Improvements and fixes to the code for handling/restoring window size and position [https://gitlab.com/inkscape/inkscape/merge_requests/180]
. The window manager handles most of the job now which should make it much more robust. If you still encounter problems with this, please report those to our bug tracker.

=== HiDPI ===

==== Icons ====
[Please fill in]

=== Y Axis Inversion ===

During the [https://inkscape.org/en/news/2018/09/20/inkscape-hackfest-kiel-2018-what-happened/ Inkscape Hackfest in Kiel], a large change by Thomas Holder was integrated into the Inkscape codebase. It allows you to optionally set the origin of your document to the top left corner of the page. This finally makes the coordinates that you can see in the interface match the ones that are saved in the SVG data (unit conversions/transformations may be required), and makes working in Inkscape more comfortable for people who are used to this more standard behavior.

<gallery>
File:Origin in upper left.png|''Option in the preferences' 'Interface' section''|alt=Option in the preferences' 'Interface' section
File:Origin in upper left page.png|''Effect of the option (left upper page corner at 0/0)''|alt=Effect of the option (left upper page corner at 0/0)
</gallery>

== Canvas ==

=== Canvas Rotation ===

With <kbd>Ctrl+Shift+Scroll wheel</kbd> the drawing area can be rotated and viewed from different angles. In the bottom right corner of the Window, the viewing angle can be entered manually. Right-click to select between a set of preset values. Keyboard shortcuts for clockwise/counter-clockwise/no rotation can be set in the preferences.

[[File:Canvas rotation.gif]]

=== Canvas Mirroring ===

The canvas can now be flipped, to ensure that the drawing does not lean to one side, and looks good either way.
The vertical/horizontal flipping is available from the menu View > Canvas orientation > Flip horizontally / Flip vertically. Keyboard shortcuts for flipping the canvas can be set in the preferences (Edit > Preferences > Interface > Keyboard shortcuts).

[[File:Flip canvas 300px.gif]]

=== Pinch-to-zoom ===

On supported hardware (trackpad, touchpad, multi-touch screen), the canvas can be zoomed with the two-finger pinch gesture.

== Visible Hairlines Display Mode ==

This new display mode is available under the "View->Display mode" menu. It ensures that all lines are visible, regardless of zoom level, while still drawing everything else normally.

This is especially useful for some CNC machines like laser cutters and vinyl cutters which use hairlines to denote cut lines.

[[File:visible_hairlines.gif]]

== Paths ==

=== Changed behavior of Stroke to Path ===

The 'Stroke to Path' command now not only converts the stroke of a shape to path, but effectively splits it into its components.

In the case of applying it to a path that only has a stroke, the behavior is unchanged.

For paths that don't only have a stroke, but also a fill and/or markers, the result will be a group consisting of:
* Stroke outline turned to path
* Fill (if there was one)
* A group of all markers (if applicable; one group per marker, consisting of its outline and its fill turned into a path)

[[File:Stroke to path.gif]]

=== Unlinking Clones for Path Operations ===

Clones and Symbols are now automatically unlinked, before a Boolean operation (union, difference, etc.), or one of the Path operations 'Combine', 'Break apart', or 'Stroke to Path' is performed.

A setting in the preferences at ''Behavior → Clones → Unlink Clones'' allows to disable the automatic unlinking.

== Tools ==

=== Calligraphy Tool ===

A new option to add dots has been added to the tool. Click in place without moving the mouse to create a dot, Shift+Click to create a larger dot ''[needs documentation in keyboard shortcut list]''.

=== Circle Tool ===

The circle tool can now also create closed ("filleted") circle shapes (closed arcs) with the click of a button.

<gallery>
File:Circle chord.png|''Circle tool shapes in this release''|alt=Circle tool shapes in this release
</gallery>

=== Eraser ===

New option to erase as clip, which allows to non-destructively erase (parts of) all kinds of elements, including raster images and clones.

[[File:Erase with clip.gif]]

=== Measurement Tool ===

Hovering over a path with the tool now displays the length, height, width and position of the path. If you hover over a group, it will show the width, height and position of the group. Holding Shift switches to showing info about the constituents of the group.

The tool also has a new option to only measure selected objects when using click-and-drag.

<gallery>
File:Measure tool info.png|''New info text from measurement tool (for a group)''|alt=New info text from measurement tool (for a group)
File:Measure tool info group shift.png|''Measurement tool info text for a single path (in a group with Shift)''|alt=Measurement tool info text for a single path (in a group with Shift)
File:Measure selected.png|''Measuring only the selected object (the ice cap)''|alt=Measuring only the selected object (the ice cap)
</gallery>

=== Pencil Tool ===

==== PowerPencil ====

Pressure sensitivity can now be enabled for the Pencil tool. This feature makes use of the PowerStroke Live Path Effect (LPE).

New settings for the tool are available for tweaking the behavior of the PowerStroke LPE when it is being created with the Pencil tool (and a graphics tablet/stylus):
* '''Use pressure input''' (in the tool controls bar): activates the PowerStroke feature, if a pressure sensitive device is available.
* '''Min/Max''' (in the tool controls bar): determines the minimal and maximal stroke width (0 to 100%). This does not change the number of available pressure levels, but spreads them out in the available line width interval.
* Additionally, the PowerStroke LPE itself has been improved, to better work when used in this new way, see [[#PowerStroke_LPE_Improvements|the section about LPE updates]].
* '''Pressure change for new knot''' (in the global Inkscape preferences, Edit > Preferences > Tools > Pencil): adds a PowerStroke Knot when the stylus pressure changes by this percentage.

''[needs video/gif]''

== Clipping / Masking ==

Clip paths and masks now have an inverse mode in the menu, using the PowerClip and PowerMask LPEs.

[[File:Inverse clip 400.gif]]

== Live Path Effects ==

Live Path Effects received a major overhaul, with lots of improvements and new features. The main changes are:

* '''Set default parameters''': default values for any LPE can be set in the respective LPE's dialog, when it is applied to an object
(''Note: we have the 'multiple desktop preferences' problem here: If you have multiple Inkscape windows open, the last one will determine what will be saved to the preferences file, as preferences changes are only saved when Inkscape is closed, and the settings are only loaded from file when a new window is opened.'')
* '''Clip and Mask''': improved handling
* '''Fix multiple LPE BBox''': a problem with the size of the bounding box when applying multiple LPEs to an object has been fixed
* '''Knots on shapes''': show edit knots in LPE shapes
* '''Switch knots''': change the handles to the correct LPE handles when one selects an LPE in the list of active LPEs for the selected object.

In addition to this, the LPE list now features an icon for each LPE (TBC).

<gallery>
File:LPE set defaults.png|''Set default values for Mirror LPE''|alt=Set default values for Mirror LPE
</gallery>

=== Boolean Operations LPE ===

''[The Boolean Operations LPE finally makes non-destructive boolean operations available in Inkscape. It works by adding the LPE to a path, then linking a copied path to it by clicking on the 'link to path' button. That way, two [more?] paths can be combined to a single shape, and both are still editable. Available options:

* union
* symmetric difference
* intersection
* division
* difference
* cut outside
* cut inside
* cut
''] functionality incomplete currently, does not hide linked operand, see https://gitlab.com/inkscape/inkscape/merge_requests/20#note_100799480''

<gallery>
File:Boolops LPE.png|''Boolean Operations LPE''|alt=Boolean Operations LPE
</gallery>

=== BSPline and Spiro ===

Improvements in Pen/Pencil mode. With "Alt", you can move the previous node.

=== 'Clone Original' Improvements ===

This path effect now allows various objects instead of only paths and is even more powerful.

[https://www.youtube.com/watch?v=JAJAxKNY8lA Demo Video]

[https://ia601501.us.archive.org/34/items/00003303/0000-3303.ogv Demo Video]

=== Dash Stroke LPE ===

This new LPE creates uniformly dashed paths, optionally by subdividing the path's segments, or including dashes that are symmetrically wrapped around corners.

<gallery>
File:Dash stroke LPE.png|''Rectangles with dash stroke LPE with various settings''|alt=Rectangles with dash stroke LPE with various settings
</gallery>

[https://archive.org/details/dash-stroke-lpe Demo Video]

=== Ellipse from Points ===

This new LPE creates an optimally fitted ellipse from a path's nodes.

In contrast to the already existing LPE "Ellipse by 5 points" this LPE is more flexible (since, depending on the number of points available, it can fit both circles and ellipses) and has more features. Especially technical illustrators can benefit from these features.

See [[LPE:_Ellipse_from_Points]] for a documentation.

<gallery>
File:Ellipse from points LPE.png|''Ellipse (5 nodes), circle (3 nodes), circle segment (3 nodes), isometric circle (3 nodes), isometric circle with frame (3 nodes)''|alt=Ellipse (5 nodes), circle (3 nodes), circle segment (3 nodes), isometric circle (3 nodes), isometric circle with frame (3 nodes)
</gallery>

=== Embroidery Stitch LPE ===

This new LPE can add nodes to your paths and create jump stitches, to create data that can be converted for use with a stitching machine.
To view the stitches that you added, activate the 'Show stitches' checkbox, and, if necessary, adjust the 'Show stitch gap' value, so you can see the single stitches.

There are various options for calculating the order of the stitching, for connecting the parts of the drawing and 3 different stitch patterns available. It is suggested to play around with these until you like the result.

For exporting your data, you can, for example, use the HPGL file format and go from there.

<gallery>
File:Embroidery stitch lpe.png|''Inkscape Logo with Embroidery LPE (stitches made visible)''|alt=Inkscape Logo with Embroidery LPE (stitches made visible)
File:Embroidery stitch lpe options.png|''Available options: left: methods to order subpaths, right: methods to connect end points of subpaths''|alt=Options: left: methods to order subpaths, right: methods to connect end points of subpaths
</gallery>

=== Fill Between Many / Fill Between Strokes LPE ===

New options added:

* Fuse coincident points: [describe]
* Join subpaths: [describe]
* Close: [describe]
* LPEs on linked: [describe] (Fill Between Many only)

=== Fillet/Chamfer LPE ===

This new LPE adds fillet and chamfer to paths. Also adds a new internal class that allows to handle extra info per node, the LPE itself is an example of use the new classes.

[https://www.youtube.com/watch?v=wJKzGhJULfc Demo video]

<gallery>
File:Chamfer lpe.png|''Chamfer with LPE''|alt=Chamfer by LPE
File:Chamfer with steps.png|''Chamfer with 2 steps''|alt=Chamfer with 2 steps
File:Inverse chamfer with steps.png|''Inverse Chamfer with 2 steps''|alt=Inverse Chamfer with 2 steps
File:Fillet lpe.png|''Fillet with LPE''|alt=Fillet with LPE
File:Inverse fillet lpe.png|''Inverse fillet with LPE''|alt=Inverse fillet with LPE
</gallery>

=== Knot LPE ===

New options added:

* Inverse: use the stroke width of the other path as basis for calculating the gap length
* Add stroke width: make the gap wider by adding the width of the stroke to the value for the gap length
* Add bottom (other?) stroke width: make the gap wider by adding the width of the bottom (other?) stroke to the value for the gap length
* Crossing signs: [not final]

=== Measure Segments LPE ===

This new path effect adds DIN and custom style measuring lines to "straight" segments in a path.

[https://www.youtube.com/watch?v=ppgt2GPm1IY Demo video]

<gallery>
File:Measure segment LPE.png|''Measure Segments LPE''|alt=Measure Segments LPE
</gallery>

=== Mirror Symmetry and Rotate Copies LPE===

* Split feature: This new feature allows custom styles for each part of the resulting drawing without unlinking the LPE. [https://www.youtube.com/watch?v=mIzrQ2lpzuw Demo Video]
* The LPE display now updates accordingly when there are objects added or removed.

<gallery>
File:Rotate copies LPE with style split.png|''Separate styles for rotated copies''|alt=Separate styles for rotated copies
</gallery>

=== Power Clip and Power Mask LPE ===

This new LPE adds options to clips and masks.

=== PowerStroke LPE Improvements ===

* '''Width scale''' setting added: adjust the overall width of the stroke after it has been drawn.
* '''Closed paths''': PowerStroke now works much better on closed paths.

== Import / Export ==

=== Linking and embedding SVG files ===

On import of an SVG file, there is now a dialog that asks if the user would like to link to the SVG file, to embed it (base64 encoded) into an <img> tag, or if the objects in the SVG file should be imported into the document (which was how Inkscape handled importing SVG files previously).

''[ TBC: The dpi value for displaying embedded SVG files can be set in the import dialog.]''

This makes importing SVG files work (almost) the same as importing raster images.

The 'Embed' and 'Extract' options in the context menu for linked SVG files work the same as they do for raster images. The 'Edit externally' option will open the linked SVG file with Inkscape per default. This setting can be changed in the preferences' 'Imported Images' section.

The displaying of the dialog can be disabled by checking the 'Don't ask me again' option.

Linked and embedded SVG images are displayed as their raster representations.

The resolution used for displaying them ''[TBC: can be set per image? can be set in the xxx dialog for the selected image]'' is the default image import resolution set in the preferences' 'Imported Images' section. A change in this option will take effect upon closing and reopening the file, and will affect all linked SVG images in the file.

=== Export PNG images ===

The export dialog has received several new options which are available when you expand the 'Advanced' section.

* Enable interlacing (ADAM7): when loading images, they will be displayed faster
* Bit depth: set the number of bits that code for the color of a pixel, supports grayscale and up to 16bit
* Compression type: choose strength of lossless compression
* pHYs dpi: force-set a dpi value for the image
* Antialiasing: choose type of antialiasing or disable it

<gallery>
File:Png-export-options 1.0.png|''PNG export options''|alt=PNG export options
File:Bit depth options 1.0.png|''PNG bit depth options''|alt=PNG bit depth options
File:Compression options 1.0.png|''PNG compression options''|alt=PNG compression options
File:Antialiasing options 1.0.png|''PNG antialiasing options''|alt=PNG antialiasing options
</gallery>

== Extensions ==

=== Extension development ===

* All [[INX Parameters]] now have the common attribute <code>indent="n"</code> where <code>n</code> specifies the level of indentation in the extension UI.
* Add <code>appearance="url"</code> for [[INX Parameters]] of type "description". You can now add clickable links to your extension UI.

=== Plot extension ===

The new option 'Convert objects to paths' will take care of converting everything to a path non-destructively before the data is sent to the plotter. [''gives wrong error message, maybe not working? https://gitlab.com/inkscape/inkscape/commit/dd3b6aa099175e2244e1e04dde45bf21a966425e#note_100908512'']

== Palettes ==

The Munsell palette has been added to Inkscape's set of stock palettes.

<gallery>
File:Munsell palette.png|''Munsell palette''|alt=Munsell palette
</gallery>

== Templates ==

* The '''Desktop''' template has new options for 4k, 5k and 8k screens.
* A new template for an A4 3-fold roll flyer was added.

<gallery>
File:Desktop templates.png|''New template options for 'Desktop' template''|alt=New template options for 'Desktop' template
File:A4 3fold roll template.png|''New A4 3-fold roll flyer template''|alt=New A4 3-fold roll flyer template
</gallery>

== SVG and CSS ==

* '''Dashes''': Inkscape can now load and display files with dashes and/or dashoffsets defined in other units than the unitless user unit (e.g. %, mm) correctly. There is no user interface for editing these values currently, except for the XML editor. Values for the dasharray that are entered in other units (except for %) will be converted to user units when the new values are set.

* [Please fill in]

== Dialogs ==

=== Document Properties ===

* When resizing the page, the page margin fields can now be locked, so the same value will be used for all margins, but only needs to be entered once.
* The guides panel now has controls to lock or unlock all guides, create guides around the page, and delete all guides. These actions also appear on the Edit menu, making it possible to assign custom keyboard shortcuts.
* Grids can now be aligned to the corners, edge midpoints, or centre of the page with a button click in the grids panel.

<gallery>
File:Lock margins doc props.png|''Lock to set same margins for page resizing''|alt=Lock to set same margins for page resizing
File:New guide options doc props.png|''Document properties: Toggle guide lock for document, create page border guides, remove all guides''|alt=Document properties: Toggle guide lock for document, create page border guides, remove all guides
File:Grid alignment doc props.png|''Grid alignment options in document properties''|alt=Grid alignment options in document properties
</gallery>

=== Preferences ===

* The '''Bitmaps''' subsection has been renamed to '''Imported Images''', as it now applies to both imported (embedded or linked) raster images as well as to imported (embedded or linked) SVG images (i.e. to everything in <img> tags).
* The '''System''' subsection lists more relevant folders and offers buttons to open those folders with the system's file browser. This makes it easier to find the correct folder, e.g. for resetting the preferences or for adding an extension or a new icon set.
* An option for '''scaling a stroke's dash pattern when scaling the stroke width''' has been added and can be found at ''Behaviour → Dashes''. It is activated by default.
* '''Autosave''' is now enabled by default. The default directory has changed (the path is displayed in Edit > Preferences > Input/Output > Autosave: Autosave directory).

<gallery>
File:Open folders from preferences.png|''Important folders can be opened from the preferences''|alt=Important folders can be opened from the preferences
</gallery>

=== Symbols ===

* The Symbols dialog can now handle a lot of symbols without delay on startup, and also allows searching. Symbols and symbol sets now displayed in alphabetical order.

<gallery>
File:Symbols list.png|''Symbol sets ordered alphabetically''|alt=Symbol sets ordered alphabetically
File:Symbols search.png|''Searching for symbols''|alt=Searching for symbols
</gallery>

=== Filter Editor ===

* The filter primitives now also have a symbolic icon (one whose color can be changed).

== Customization ==

=== Customize all files in the share folder ===

All files in <code>/share</code> can be over-ridden by placing files in the user's configuration folder (e.g. <code>~/.config/inkscape</code>).
Configurable contents now includes extensions, filters, fonts, gradients, icons, keyboard shortcuts, preset markers, palettes, patterns, about screen, symbol sets, templates, tutorials and some user interface configuration files. Only the file 'units.xml' cannot be overridden.

=== Fonts ===

* Inkscape can now load fonts that are not installed on the system. By default Inkscape will load additional fonts from Inkscape's share folder (<code>/share/inkscape/fonts</code>) and the user's configuration folder (<code>~/.config/inkscape/fonts</code>). Custom folders can be set in preferences (see ''Tools → Text → Additional font directories'').

<gallery>
File:Custom font folders.png|''Set custom font folders''|alt=Set custom font folders
</gallery>

=== Keyboard shortcuts ===

* Allow to use "Super", "Hyper" and "Meta" modifier keys
* Improve shortcut handling code. This should fix a lot of issues and allow to use a lot of shortcuts which were inaccessible before, especially on non-English keyboard layouts.

=== User interface customization ===

* Inkscape is starting to use glade files for its dialogs so they can be reconfigured by users. Only one is currently supported (filter editor).
* The contents of the menus can be configured by customizing the <code>menus.xml</code> file.
* Toolbar contents for the command bar (<code>commands-toolbar.ui</code>), the snap bar (<code>snap-toolbar.ui</code>), the tool controls bars for each tool (<code>select-toolbar.ui</code>), the toolbox (<code>tool-toolbar.ui</code>) is now configurable.
* The file <code>keybindings.rc</code> allows you to... '''(TODO: do what? What does it do in comparison to keys.xml? Seems to not work at all... seems to be ancient. Can be deleted?)'''
* The interface colors and some more UI styles can be customized in <code>style.css</code> (very raw themeing support).

=== Theme selection ===

In 'Edit > Preferences > User Interface > Theme', users can set a custom GTK3 theme for Inkscape. If the theme comes with a dark variant, activating the 'Use dark theme' checkbox will result in the dark variant being used. The new theme will be applied immediately.

New theme folders can be added to the directory indicated in Edit > Preferences > System : User themes. A large selection of (more or less current) GTK3 themes is available for download at [https://www.gnome-look.org/browse/cat/135/ord/top/ gnome-look.org]

=== Icon set selection ===

In 'Edit > Preferences > User Interface > Theme', the icon set to use can be selected. By default, Inkscape comes with 'hicolor' and 'Tango' icons. In addition to this, it offers to use the system icons.

Inkscape also comes with a default symbolic icon set as part of the hicolor icon set. These icons can be colorized in a custom color.

Changes to the icon set take effect when Inkscape is restarted, or when the entire user interface is reloaded by clicking on the 'Reload icons' button. This rebuilds all Inkscape windows. Rebuild takes a couple of seconds, during which the Inkscape interface will be invisible.

<gallery>
File:Tango icons.png|''Light theme with Tango icon set''|alt=Light theme and Tango icon set
File:Hicolor icons.png|''Light theme with hicolor icon set''|alt=Light theme and hicolor icon set
File:Dark with symbolic icons.png|''Dark theme with symbolic icon set''|alt=Dark theme and symbolic icon set
File:Dark symbolic custom color.png|''Dark theme with symbolic icon set and a custom icon color''|alt=Dark theme with custom colored symbolic icon set
</gallery>

=== Saving the current file as template ===

A new entry for saving the current file as a template has been added to the 'File' menu. You need to specify a name for it, and optionally, you can add the template's author, a description and some keywords. A checkbox allows you to set the new template as the default template.

<gallery>
File:Save as templage.png|''Save current file as a template''|alt=Save current file as a template
</gallery>

=== Custom page sizes in Document Properties ===

Inkscape now creates a CSV file (comma separated values) called "pages.csv". It is located in your Inkscape user preferences folder, next to your 'preferences.xml' file. This file contains the default page sizes that you can choose from in the 'Page' tab of the 'Document properties' dialog. You can edit the pages.csv file to remove the page sizes you won't use, or to add new ones.

== Inkview ==

'''Inkview''' was considerably improved and got some new features:

* Support folders as input (will load all SVG files from the specified folder) The <code>-r</code> or <code>--recursive</code> option will even allow to search subfolders recursively.
* Implement <code>-t</code> or <code>--timer</code> option which allows to set a time after which the next file will be automatically loaded.
* Add <code>-s</code> or <code>--scale</code> option to set a factor by which to scale the displayed image.
* Add <code>-f</code> or <code>--fullscreen</code> option to launch Inkview in fullscreen mode
* Many smaller fixes and improvements

== Command Line ==

The Inkscape command line has undergone a large overhaul. The most important changes are:

* verbs/actions .......
* order of commands .......
* parallel exports ....
* shell mode(s)....
* ........

* Probably not in release: [[Using xverbs|xverbs]] (command line commands that take parameters, e.g. for saving the selection under a specified filename as svg file) ([https://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/33487d06-e3c1-a4e5-1496-7b370d672d2f%40gmail.com/#msg35392523 mailing list thread])
* New verb allows to swap fill and stroke from command line: EditSwapFillStroke (a keyboard shortcut can now be assigned to it) ([https://bugs.launchpad.net/inkscape/+bug/675690 bug 675690])
* Files can now also be saved as Inkscape SVG without calling the GUI save dialog (new command: --export-inkscape-svg)
* Inkscape can now import a specific page of a PDF file from the command line, for batch processing (new option: --pdf-page N) - does this still work after Tav's changes?

== Translations ==

New UI translations for [please fill in].

== Notable Bugfixes ==

* Symbols: Visio Stencils loaded from .vss files now use their actual name instead of a placeholder derived from the symbol file's name ([https://bugs.launchpad.net/inkscape/+bug/1676144 bug 1676144])
* Shapes on Pen and Pencil tools now retain color and width ([https://bugs.launchpad.net/inkscape/+bug/1707899 bug:1707899]).
* Text and Font dialog: The font selection no longer jumps to the top of the list when clicking Apply.
* Docked dialogs now open on their own when the corresponding functionality is called from a menu or button [TBC: Bug: if minimized, this requires a second click]
* The icon preview dialog now correctly shows the page background (Bug #[https://bugs.launchpad.net/inkscape/+bug/1537497 1537497]).

For an exhaustive list of bugs that have been fixed, please see the [https://launchpad.net/inkscape/1.0.x milestones page for Inkscape 1.0].

== Known Issues ==

[Please fill in]

== Previous releases ==
* [[Release notes/0.92]] ([[Release_notes/0.92.1 |0.92.1]], [[Release_notes/0.92.2 |0.92.2]], [[Release_notes/0.92.3 |0.92.3]])
* [[Release notes/0.91]]
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]], [[Release notes/0.48.4 | 0.48.4]], [[Release notes/0.48.5 | 0.48.5]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

URIs and Filenames

2018-12-08T14:39:06Z

Speleo3: Done section

Inkscape's handling of URIs and Filenames is a complete mess!
* What some variable names claim to be URIs are actually filenames and visa-versa.
* There is a lot of code duplication. (e.g. <code>[https://gitlab.com/inkscape/inkscape/blob/master/src/io/dir-util.cpp src/io/dir-utils.cpp]</code> and <code>[https://gitlab.com/inkscape/inkscape/blob/master/src/xml/rebase-hrefs.cpp src/xml/rebase-hrefs.cpp]</code>).

== Done ==

* [https://gitlab.com/inkscape/inkscape/merge_requests/364 Merge Request !364] (<code>Inkscape::URI</code> refactoring)
* [https://gitlab.com/inkscape/inkscape/merge_requests/437 Merge Request !437] (<code>Inkscape::URI</code> complete documentation and testing)

== To do ==

* Put all our own URI and Filename handling code in <code>src/io</code> (or at least list in README in that directory).
* Convert all routines to use:
** <code>std::string</code> (byte string) for file names and paths.
** <code>Glib::ustring</code> (unicode string) for URIs
* Rely on Glib functions where possible. Glib functions handle many of the WIN32/LINUX/MAC issues automatically.
** Use [http://manual.freeshell.org/glibmm-2.4/reference/html/classGio_1_1File.html Gio::File] class.
** Use Glib utility and conversion functions (see below).
* Remove 'sodipodi-absref' as this leaks user directory information.
* Clarify whether/when to use these classes (most stuff in Inkscape::IO should probably be removed, Tav):
** <code>[https://gitlab.com/inkscape/inkscape/blob/master/src/object/uri.h Inkscape::URI]</code>
** <code>[https://gitlab.com/inkscape/inkscape/blob/master/src/io/uristream.h Inkscape::IO::UriInputStream]</code>
*** Why does <code>UriInputStream</code> not decode <code>data:</code> URIs?

== Notes ==

* URIs should always use '/'. You cannot use Glib filename functions to handle URIs as they will use '/' or '\' depending on operating system.
* Use relative paths (URIs!) where possible as this allows moving documents with resources together.

== glibmm Documentation ==

=== [http://transit.iut2.upmf-grenoble.fr/doc/glibmm-2.4/reference/html/group__MiscUtils.html Misc. Utility Functions] ===

;<nowiki>bool Glib::path_is_absolute (const std::string& filename)</nowiki>
:Returns true if the given filename is an absolute file name, i.e. it contains a full path from the root directory such as "/usr/local" on UNIX or "C:\\windows" on Windows systems. More...

;<nowiki>std::string Glib::path_skip_root (const std::string& filename)</nowiki>
:Returns the remaining part of filename after the root component, i.e. after the "/" on UNIX or "C:\\" on Windows. More...

;<nowiki>std::string Glib::path_get_basename (const std::string& filename)</nowiki>
:Gets the name of the file without any leading directory components. More...

;<nowiki>std::string Glib::path_get_dirname (const std::string& filename)</nowiki>
:Gets the directory components of a file name. More...

;<nowiki>std::string Glib::build_filename (const Glib::ArrayHandle< std::string >& elements)</nowiki>
:Creates a filename from a series of elements using the correct separator for filenames. More...

;<nowiki>std::string Glib::build_filename (const std::string& elem1, const std::string& elem2)</nowiki>
:Creates a filename from two elements using the correct separator for filenames. More...

;<nowiki>std::string Glib::build_filename (const std::string& elem1, const std::string& elem2, const std::string& elem3)</nowiki>
:Creates a filename from three elements using the correct separator for filenames. More...

etc.

=== [http://manual.freeshell.org/glibmm-2.4/reference/html/group__CharsetConv.html Conversions] ===

;<nowiki>Glib::ustring Glib::filename_to_utf8 (const std::string& opsys_string)</nowiki>
:Converts a string which is in the encoding used for filenames into a UTF-8 string.

;<nowiki>std::string Glib::filename_from_utf8 (const Glib::ustring& utf8_string)</nowiki>
:Converts a string from UTF-8 to the encoding used for filenames.

;<nowiki>std::string Glib::filename_from_uri (const Glib::ustring& uri, Glib::ustring& hostname)</nowiki>
:Converts an escaped UTF-8 encoded URI to a local filename in the encoding used for filenames.

;<nowiki>std::string Glib::filename_from_uri (const Glib::ustring& uri)</nowiki>
:Converts an escaped UTF-8 encoded URI to a local filename in the encoding used for filenames.

;<nowiki>Glib::ustring Glib::filename_to_uri (const std::string& filename, const Glib::ustring& hostname)</nowiki>
:Converts an absolute filename to an escaped UTF-8 encoded URI.

;<nowiki>Glib::ustring Glib::filename_to_uri (const std::string& filename)</nowiki>
:Converts an absolute filename to an escaped UTF-8 encoded URI.

;<nowiki>Glib::ustring Glib::filename_display_basename (const std::string& filename)</nowiki>
:Returns the display basename for the particular filename, guaranteed to be valid UTF-8.

;<nowiki>Glib::ustring Glib::filename_display_name (const std::string& filename)</nowiki>
:Converts a filename into a valid UTF-8 string.

CompilingMacOsX

2018-11-04T12:52:12Z

Speleo3: minor changes

= Using MacPorts =

<ol>
<li>Install [http://developer.apple.com/tools/xcode/ Xcode tools] from the App Store
<li>Download and install [http://www.macports.org/ MacPorts]
<li>Edit the MacPorts variants config (optional).
 Add this line to <code>/opt/local/etc/macports/variants.conf</code>
<pre>-x11 +quartz</pre>
<li>In Terminal (Applications>Utilities>Terminal) type
<syntaxhighlight lang="bash">sudo port selfupdate
sudo port install \
cmake cairo boehmgc intltool libxslt lcms2 popt boost \
poppler gsl adwaita-icon-theme gdl3 gtkmm3 libsoup \
-x11 +quartz
</syntaxhighlight>
<li>In Terminal, get Inkscape
<syntaxhighlight lang="bash">git clone --recurse-submodules git@gitlab.com:inkscape/inkscape.git</syntaxhighlight>
<li>And build inkscape
<syntaxhighlight lang="bash">
# use a clean MacPorts environment (optional)
LIBPREFIX="/opt/local"
export PATH="$LIBPREFIX/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# where to build and install
PREFIX="$PWD/install-prefix"
mkdir build
cd build

cmake \
-DCMAKE_PREFIX_PATH="$LIBPREFIX" \
-DCMAKE_INSTALL_PREFIX="$PREFIX" \
-DWITH_OPENMP=OFF \
..

make install
</syntaxhighlight>
<li>Run Inkscape
<syntaxhighlight lang="bash">
$PREFIX/bin/inkscape
</syntaxhighlight>
</ol>

== Speed up Installation ==

You can use <code>[https://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>sudo port install ccache</code>) to speed up re-compilation.
Also, [https://ninja-build.org/ ninja] (<code>sudo port install ninja</code>) is a faster alternative to <code>make</code>.
Modify your call to <code>cmake</code> like this:

cmake \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-G Ninja \
# more cmake options here

ninja
ninja install

= Using Homebrew =

The Inkscape CI job uses homebrew, see [https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml#L51-71 .gitlab-ci.yml]

= Misc =

{{Needs_update}}

== Extension Python modules ==

In case you are using a Python version installed through MacPorts do a search for both modules and install the ones suitable for the Python version activated within MacPorts.
<pre>port search lxml numpy</pre>

For further info refer to the [[GettingEffectsWorking#on_Mac_OS_X|Getting Effects Working]] section of this wiki.

== Creating an .app bundle ==

TODO

== Creating a disk image to distribute Inkscape ==

TODO

= Links =

== User Examples ==
* Adam Strzeleki has outlined some improvements to this process on the Inkscape [http://www.nabble.com/Inkscape-native-Mac-OS-X-build---look-improvements-td14733036.html email list]. See his screenshot from January 10, 2008 [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here].
* JiHO has a video of his builds [http://jo.irisson.free.fr/?p=34 here] and [http://jo.irisson.free.fr/?p=62 here].
* Mac OS X native (aqua), PPC-only, Tiger-only build of 0.47, can be retrieved here: [http://verkehrsplanung.com/Inkscape_aqua_PPC_047.zip]. NOT FOR PRODUCTIVE USE - JUST TESTING! - (Nevertheless I'm doing quite a bit productive work on it… (-;)

== Apple Documentation ==
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

== Packaging ==

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

=See also=
*[[Compiling Inkscape]]
*[[Notes on Packaging for OS X]]
* https://github.com/valerioa/Inkscape-MacOS-Curated-Build

[[Category:Developer Documentation]]