Inkscape Wiki - User contributions [en]

CompilingMacOsX

2025-01-28T10:53:01Z

Marcin: + info about missing GSettings schemas

__TOC__

Section about MacPorts IS OUTDATED AND UNMAINTAINED!
Section about HomeBrew IS UP TO DATE as of Oct 30, 2024

= Using MacPorts =

If you can build successfully with MacPorts, please update this file and remove above comment.

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

Prerequisites:
* Xcode (AppStore)
* Xcode command line tools (<code>xcode-select --install</code>)
* HomeBrew

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.
(Make sure you don't have any MacPorts stuff in your PATH.)

List of '''packages''' to install with brew
(for Inkscape on master branch using GTK4):

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

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

To build version <code>1.4-x</code> you need <code>gtkmm3</code>, the <code>gtkmm4</code> is used from version <code>1.5</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.

Check out the source if you haven't already:

<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>

Then <code>cd inkscape</code> and follow the steps below.

Tested with:
* M4 MacBook Air with macOS 15.1.1 and Inkscape 1.5-dev (takes about 7 minutes)
* M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev
* M2 MacBook Air with macOS 13.0.1 and Inkscape 1.2.1, 1.2.x from git.
* M2 Mac Mini with macOS 14.2 and Inkscape 1.4-dev. (After adding pkg-config.)
* VM with macOS 15.1 and Inkscape 1.5-dev (master branch)

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

=Running=

If you encounter the following error (when, eg. going to open file dialog):
<code>
(org.inkscape.Inkscape:91305): GLib-GIO-ERROR **: 11:18:06.449: No GSettings schemas are installed on the system
</code>

Then you have to modify the following:
<code>
export XDG_DATA_DIRS=$XDG_DATA_DIRS:/opt/homebrew/share
</code>

=Packaging=

If <code>$PREFIX/bin/inkscape</code> works when executed and you want to turn it into an app or a DMG, have a look at the files inside the <code>inkscape/packaging/macos</code> directory. More info can be found on upstream mibap:

* https://github.com/dehesselle/mibap

Follow the steps to install the toolset, package the app, and create a DMG. In case you use upstream mibap, you will get the app under <code>/Users/Shared/work/mibap-*/</code> and you will get a DMG file in the same place you ran <code>./build_inkscape.sh</code>.

=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

2025-01-28T10:50:12Z

Marcin: /* Using Homebrew */ + tested with MBA with M4 and lib dependencies for 1.4

__TOC__

Section about MacPorts IS OUTDATED AND UNMAINTAINED!
Section about HomeBrew IS UP TO DATE as of Oct 30, 2024

= Using MacPorts =

If you can build successfully with MacPorts, please update this file and remove above comment.

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

Prerequisites:
* Xcode (AppStore)
* Xcode command line tools (<code>xcode-select --install</code>)
* HomeBrew

If you are using [https://brew.sh/ Homebrew] instead, you can still use the above guidelines with small modifications.
(Make sure you don't have any MacPorts stuff in your PATH.)

List of '''packages''' to install with brew
(for Inkscape on master branch using GTK4):

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

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

To build version <code>1.4-x</code> you need <code>gtkmm3</code>, the <code>gtkmm4</code> is used from version <code>1.5</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.

Check out the source if you haven't already:

<syntaxhighlight lang="bash">git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git</syntaxhighlight>

Then <code>cd inkscape</code> and follow the steps below.

Tested with:
* M4 MacBook Air with macOS 15.1.1 and Inkscape 1.5-dev (takes about 7 minutes)
* M1 MacBook Air with macOS 11.6 and Inkscape 1.2-dev
* M2 MacBook Air with macOS 13.0.1 and Inkscape 1.2.1, 1.2.x from git.
* M2 Mac Mini with macOS 14.2 and Inkscape 1.4-dev. (After adding pkg-config.)
* VM with macOS 15.1 and Inkscape 1.5-dev (master branch)

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

=Packaging=

If <code>$PREFIX/bin/inkscape</code> works when executed and you want to turn it into an app or a DMG, have a look at the files inside the <code>inkscape/packaging/macos</code> directory. More info can be found on upstream mibap:

* https://github.com/dehesselle/mibap

Follow the steps to install the toolset, package the app, and create a DMG. In case you use upstream mibap, you will get the app under <code>/Users/Shared/work/mibap-*/</code> and you will get a DMG file in the same place you ran <code>./build_inkscape.sh</code>.

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

Template:Other languages

2020-04-25T11:16:15Z

Marcin: Enable Polish

<noinclude>{{Moved to the website}}

</noinclude><div style="margin: .5em; padding: 0 .5em; border: 1px solid darkgray; background: #EFE; font-size: .9em;">
''Other languages:''


[[{{{ar|{{{en|}}}/ar}}}|العربية]]





[[{{{ca|{{{en|}}}/ca}}}|Català]]
[[{{{cs|{{{en|}}}/cs}}}|Česky]]

[[{{{de|{{{en|}}}/de}}}|Deutsch]]

[[{{{en|}}}|English]]

[[{{{es|{{{en|}}}/es}}}|Español]]


[[{{{fr|{{{en|}}}/fr}}}|Français]]






[[{{{it|{{{en|}}}/it}}}|Italiano]]
[[{{{ja|{{{en|}}}/ja}}}|日本語]]


[[{{{ko|{{{en|}}}/ko}}}|한국어]]









[[{{{pl|{{{en|}}}/pl}}}|Polski]]

[[{{{pt|{{{en|}}}/pt}}}|Português]]
[[{{{pt-br|{{{en|}}}/pt-br}}}|Português do Brasil]]

[[{{{ru|{{{en|}}}/ru}}}|Русский]]
[[{{{sk|{{{en|}}}/sk}}}|Slovenčina]]








[[{{{zh-cn|{{{en|}}}/zh-cn}}}|中文]]

</div>

InkscapeTerminology/pl

2020-04-22T13:39:18Z

Marcin:

= Polish Terminology for Inkscape =
{{ListTerminology}}

== Ogólne uwagi ==

== Terminologia ==

* '''drawing''' - rysunek
* '''guide''' - prowadnica
* '''preferences''' - ustawienia (nie ''preferencje'')
* '''selection''' - zaznaczenie
* '''folder''' - katalog

InkscapeTerminology/pl

2020-04-22T13:34:30Z

Marcin: Created page with "= Polish Terminology for Inkscape = {{ListTerminology}}"

= Polish Terminology for Inkscape =
{{ListTerminology}}

Template:ListTerminology

2020-04-22T13:33:07Z

Marcin: Added Polish

{{Other languages
|en=Inkscape glossary
|cs=CzechTerminology
|fr=FrenchTerminology
|de=GermanTerminology
|pl=InkscapeTerminology/pl
|ru=RussianTerminology
|es=InkscapeTerminology/es
|pt=Portuguese Terminology
|pt-br=Brazilian Portuguese Terminology
|sk=InkscapeTerminology/sk}}
<noinclude>
This template is for updating the languages list once in the page [[Inkscape glossary]] and its localized versions, insert the following into the page
<nowiki>{{ListTerminology}}</nowiki>

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

Translation information

2020-04-20T11:31:52Z

Marcin: /* Links and docs */ linking to git info

This page gathers useful information about translation.

== Links and docs ==

* '''[https://inkscape.org/contribute/translations/ How to contribute in translation]'''
* [https://inkscape.org/doc/devel/translations-statistics-092.html Translations statistics for stable 0.92.x branch]
* [https://inkscape.org/doc/devel/translations-statistics-master.html Translations statistics for master branch (development focus)]
* [https://inkscape.org/develop/inkscape-git/ Using Inkscape's repositories]
* [https://lists.sourceforge.net/lists/listinfo/inkscape-translator Subscribe to the translator mailing list]
* [https://sourceforge.net/p/inkscape/mailman/inkscape-translator/ Translator mailing list archives]
* [[Interface translation]]
* [[Documentation translation]]
* [[WebSite#Translations|Website translation]]

== PO translation files ==

=== Add a new translation file ===

If the PO file for your language does not exist yet, then you must create it as a copy of the translation template. This template is a file whose name ends with .pot. It contains the strings to translate without any translation. Create a copy and put it to the right place (just see how other languages are managed).

=== Tools for translators ===

You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.

Recommended:
* [https://poedit.net/ Poedit] (cross-platform);
* [https://userbase.kde.org/Lokalize Lokalize] (KDE).

You might also try:
* Emacs's po-mode (contained in the gettext distribution; the version in po-utils is old);
* [https://wiki.gnome.org/action/show/Apps/Gedit gedit] — text editor for GNOME desktops, has a syntax highlight mode for PO file syntax;
* [http://virtaal.translatehouse.org/ Virtaal] — cross-platform PO editor that is clean, simple to use yet powerful;
* [https://wiki.gnome.org/Apps/Gtranslator Gtranslator] (GNOME).

And last but not least, [http://www.gnu.org/software/gettext/manual/ gettext] utils, which are installed on every Linux distribution. You can see a complete reference too from installed info pages by running the command:
<pre>
info gettext
</pre>

=== Update a translation file ===

If a translation file is already present for your language but the programmers have updated the template (.pot) since the translation was done, you need to sync the PO file with the template, especially for the new strings being added, but also for other info: position of the original string in the project, removing or marking obsolete strings, recognizing small string modifications…

Some software offers the ability to automatically sync the translation file with the template, e.g. with Poedit you can use the menu option ‘Catalog > Update from POT file…’.

GNU gettext also provides the command <code>msgmerge</code>. You can use it like this to update ''lt.po'' from ''inkscape.pot'':
<pre>
msgmerge -U lt.po inkscape.pot
</pre>

=== File format ===

If you open a PO file with a text editor for the first time, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.

<pre>
#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."
</pre>

In addition to the msgid and msgstr parts, a message usually also has lines starting with <code>#:</code> that tell what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from.

A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:

* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.
* A new string has been added to the source, and the string is similar (but not identical) to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.

=== A few important things to remember ===

* Some strings that can be ambiguous or having several meanings according to different contexts may have a context prefix: ‘Context|Ambiguous string’. In this case, give the translation for ‘Ambiguous string’ only; the ‘Context|’ part is just a not to translate indication.
* After translating a fuzzy string (one that is marked with a <code>", fuzzy"</code> comment), please remove its fuzzy tag — otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated.
* Before publishing your work (after you have finished updating the PO file), please update the <code>"PO-Revision-Date"</code> and <code>"Last-Translator"</code> fields in the PO file header.

If you use a translation software, it may deal with the last two points for you automatically (check the settings).

=== Verification ===

Before submitting your file to the project, you should make sure it is valid.
* Make sure the file is encoded in UTF-8.
* Make sure it is a valid PO file and obtain some statistics about it: simply run <code>msgfmt --statistics -cv translation_file.po</code> from a command window.
* Make sure it is correctly formatted: run <code>check-markup translation_file.po</code> from a command window and verify it doesn't output any error message. The ‘check-markup’ Perl script can be found in the /po directory of Inkscape trunk.

If your translation software can compile PO files to .mo, it should detect any errors when you save your translations so you don't need to do any further verifications.

=== Programmers ===

There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string (<code>""</code>) as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the ‘translation’. In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.

Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

See also [https://developer.gnome.org/glib/unstable/glib-I18N.html#Q-:CAPS how to disambiguate a string].

== Submit finished work ==

After you translated a file there are three possible means to submit it (the third is preferred as it allows to review the changes easily). These allow to discuss your work and gather relevant information at a dedicated place; they also require you to have an account, please see links below.

* Simply send your file to Inkscape's translators mailing list.

* Upload your file via the bug tracker for the proper repository: [https://gitlab.com/inkscape/inkscape/issues Inkscape interface and documentation], [https://gitlab.com/inkscape/inkscape-web-i18n/issues website]. Open a new bug report titled ‘Translation to <your language>’ and attach the files you created or modified to it.

* Create a merge request on GitLab ([https://gitlab.com/inkscape/inbox/issues Inkscape interface], [https://gitlab.com/inkscape/inkscape-docs/documentation/ documentation], [https://gitlab.com/inkscape/inkscape-web website]):
*# Visit the repository on GitLab, and click on 'Fork' to create your own, independent repository.
*# Make your changes to the code. There are two possibilities:
*#* Edit the files directly in your repository on the GitLab website via the provided web UI. ''(no prior knowledge required)''
*#* Download the code to you computer to work with it locally and re-upload it later. ''(some [[Working with Git|Git]] knowledge required)''
*#: Checkout the fork's code to you computer:
*#:: <code>git clone https://gitlab.com/<your_username>/<repository-name></code>
*#: Replace the previous file for your language with your new file in the directory. If there is no previous file, put your file into the right place. Tell the system it must take care of your added/changed file with:
*#:: <code>git add /path/to/your-file.po</code>
*#: Commit your changes to your own repository (put the correct information instead of the <placeholders>):
*#:: <code>git commit -m "Translated <file> for <language>, <xx>% complete</code>
*#:: <code>git push</code>
*# Visit your repository on the GitLab website, go to 'Merge requests' and make a new merge request, asking for your work to be reviewed and included in the main ('master') branch.

Many thanks for your work!

== Review ==

This is the start of a list of places to get translation reviews done. So far:
* http://www.linux.it/tp/

[[Category:Translation]]

CompilingMacOsX

2020-04-18T17:26:51Z

Marcin: /* Using Homebrew */

= 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

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

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="/usr/local/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]]

CompilingMacOsX

2020-04-18T17:18:11Z

Marcin: 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 \
..

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

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

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="/usr/local/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]]

User:Marcin

2020-04-18T16:58:35Z

Marcin: New Page (with info about the previous account)

= Marcin Floryan =

This is a new account for [[User:Mfloryan|mfloryan]].

As of 2020 based in Stockholm, Sweden.