GNUstepWiki - User contributions [en]

User:Letterus

2024-12-19T08:04:41Z

Letterus:

This is Letterus, I am interested in [http://wiki.gnustep.org/index.php/Platform:Linux#Install_from_source:_Dependencies| compiling on GNU/Linux] and [http://wiki.gnustep.org/index.php/XIB desktop cross platform development for GNU/Linux and macOS].

* Coding: https://codeberg.org/letterus
* Website: http://devbeejohn.de/ | gemini://devbeejohn.de
* Mastodon: https://fosstodon.org/@lazarus

User:Letterus

2024-12-19T08:02:36Z

Letterus: Update contact information

This is Letterus, I am interested in [http://wiki.gnustep.org/index.php/Platform:Linux#Install_from_source:_Dependencies| compiling on GNU/Linux] and [http://wiki.gnustep.org/index.php/XIB|desktop cross platform development for GNU/Linux and macOS].

* Coding: https://codeberg.org/letterus
* Website: http://devbeejohn.de/ | gemini://devbeejohn.de
* Mastodon: https://fosstodon.org/@lazarus

Success Stories

2024-07-11T11:48:58Z

Letterus: Added SOGo and Oolite.

= Adobe Crossbridge =
[http://adobe-flash.github.io/crossbridge/ Adobe Crossbridge] CrossBridge is the open-source version of Adobe FlasCC (formerly the Alchemy project).

= Apportable =
[http://www.apportable.com Apportable] is a mobile platform for porting applications from iOS to Android. Apportable has used [http://www.apportable.com/open_source GNUstep] to port many well known apps from the iOS app store to all kinds of Android based devices.

= Brilliant Service =
[http://www.brilliantservice.co.jp/viking/ Brilliant Service] is a vendor in Japan working on creating a platform for a Head Mounted Display. They are using GNUstep as the basis for the Objective-C based programming environment. Their press release is [http://hmdviking.blogspot.jp/ here].

= Cenon =
[http://www.cenon.info/ Cenon] is a vector graphics tool with a wide range of applications. It is built upon a modular graphical core, and offers a variety of applications beyond desktop publishing. Cenon can convert, import, and export many graphics formats. The modular concept allows the extension of Cenon for specialized applications.

= eggPlant =
Created by [http://www.testplant.com TestPlant], eggPlant is an application which is used by developers for user interface testing. It is an image based testing program which includes an integrated VNC client which can connect to other machines which are running VNC servers to run it's scripts against them using it's scripting language known as SenseTalk.

= GNUspeech =
[http://www.gnu.org/software/gnuspeech/ GNUspeech] an extensible, text-to-speech package, based on real-time, articulatory, speech-synthesis-by-rules. That is, it converts text strings into phonetic descriptions, aided by a pronouncing dictionary, letter-to-sound rules, rhythm and intonation models; transforms the phonetic descriptions into parameters for a low-level articulatory synthesiser; and uses these to drive an articulatory model of the human vocal tract producing an output suitable for the normal sound output devices.

= Oolite =
[https://oolite.space/ Oolite] is a free and open source 3D space trading and combat simulator "in the spirit of" Elite, a similar game published in the 1980s. The name is a contraction of object oriented Elite, because it was written in Objective-C. Among Oolite's several similarities to its source, the gaming experience is enhanced by the context set in Elite's original manual, and the accompanying novella, The Dark Wheel.

= RailML Editor =
The [http://www.ivt.baug.ethz.ch/oev/railmleditor_d.html RailML Editor] was ported to GNUstep from OPENSTEP. The RailML.org Initiative attempts to facilitate communication between railway applications. RailML Editor is one of the many applications that follow the railML standard.

= SOGo =
[https://www.sogo.nu/ SOGo] is a fully supported and trusted groupware server with a focus on scalability and open standards. SOGo provides a rich AJAX-based Web interface and supports multiple native clients through the use of standard protocols such as CalDAV, CardDAV and GroupDAV, as well as Microsoft ActiveSync.

= NetMage =
NetMage is a client-server system developed completely in GNUstep and
Objective-C and running on GNU/Linux and other flavors of *nix. It is
used internally by the companies NETLAB and GTS Nextra for collective
monitoring and administering of long-range synchronous radio
telecommunications links.

Some screenshots:

1. NetMage with the login screen visible and a list of available
synchronous networks to connect to:
http://netdev.netlab.sk/netmage1.png

2. NetMage showing a network of radio links in a synchronous network:
http://netdev.netlab.sk/netmage2.png

3. NetMage showing the settings of a modular link multiplexer along with
a list of available interface cards:
http://netdev.netlab.sk/netmage3.png

Please consider the above screenshots licensed under the FDL - I provide
them in good faith for the endorsement of GNUstep, not for any profit
(we don't sell the above mentioned software anyways...).

= See also =
[[GNUstep in production]]

Platform:Linux

2021-04-19T18:11:12Z

Letterus: /* Arch Linux / Manjaro */

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Arch Linux / Manjaro ==

=== Offical packages ===

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

=== User package sources (build yourself) ===

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies for building with gcc ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show/X11:GNUstep OBS]).

[[Category:Development]]

Platform:Linux

2021-02-22T20:32:30Z

Letterus: /* OpenSuse */ Update

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Arch Linux / Manjaro ==

=== Offical packages ===

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

=== User package sources (build yourself) ===

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

=== Prebuilt unstable packages for x86_64 ===

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app], [https://build.opensuse.org/project/show/home:letterus:gnustep-ngr list of packages]

Installing packages should be as easy as:

Add the following lines to your /etc/pacman.conf with <code>sudo nano /etc/pacman.conf</code>:

[home_letterus_gnustep-ngr_Arch]
SigLevel = Optional TrustAll
Server = https://download.opensuse.org/repositories/home:/letterus:/gnustep-ngr/Arch/$arch

Install the basic package groups:

sudo pacman -Syy gnustep-ngr gnustep-ngr-dev gnustep-ngr-desktop

If you use Manjaro it is possible you need to switch to the testing or unstable branch as that repo is built against Arch packages/dependencies. Currently you are ok with stable.

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies for building with gcc ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show/X11:GNUstep OBS]).

[[Category:Development]]

Platform:Linux

2021-02-22T20:30:45Z

Letterus: /* Dependencies */

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Arch Linux / Manjaro ==

=== Offical packages ===

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

=== User package sources (build yourself) ===

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

=== Prebuilt unstable packages for x86_64 ===

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app], [https://build.opensuse.org/project/show/home:letterus:gnustep-ngr list of packages]

Installing packages should be as easy as:

Add the following lines to your /etc/pacman.conf with <code>sudo nano /etc/pacman.conf</code>:

[home_letterus_gnustep-ngr_Arch]
SigLevel = Optional TrustAll
Server = https://download.opensuse.org/repositories/home:/letterus:/gnustep-ngr/Arch/$arch

Install the basic package groups:

sudo pacman -Syy gnustep-ngr gnustep-ngr-dev gnustep-ngr-desktop

If you use Manjaro it is possible you need to switch to the testing or unstable branch as that repo is built against Arch packages/dependencies. Currently you are ok with stable.

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies for building with gcc ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Platform:Linux

2021-02-22T20:29:33Z

Letterus: /* Debian */ Remove obsolete dep

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Arch Linux / Manjaro ==

=== Offical packages ===

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

=== User package sources (build yourself) ===

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

=== Prebuilt unstable packages for x86_64 ===

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app], [https://build.opensuse.org/project/show/home:letterus:gnustep-ngr list of packages]

Installing packages should be as easy as:

Add the following lines to your /etc/pacman.conf with <code>sudo nano /etc/pacman.conf</code>:

[home_letterus_gnustep-ngr_Arch]
SigLevel = Optional TrustAll
Server = https://download.opensuse.org/repositories/home:/letterus:/gnustep-ngr/Arch/$arch

Install the basic package groups:

sudo pacman -Syy gnustep-ngr gnustep-ngr-dev gnustep-ngr-desktop

If you use Manjaro it is possible you need to switch to the testing or unstable branch as that repo is built against Arch packages/dependencies. Currently you are ok with stable.

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Platform:Linux

2021-02-22T20:28:51Z

Letterus: /* Archlinux */ More instructions for Arch / Manjaro

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Arch Linux / Manjaro ==

=== Offical packages ===

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

=== User package sources (build yourself) ===

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

=== Prebuilt unstable packages for x86_64 ===

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app], [https://build.opensuse.org/project/show/home:letterus:gnustep-ngr list of packages]

Installing packages should be as easy as:

Add the following lines to your /etc/pacman.conf with <code>sudo nano /etc/pacman.conf</code>:

[home_letterus_gnustep-ngr_Arch]
SigLevel = Optional TrustAll
Server = https://download.opensuse.org/repositories/home:/letterus:/gnustep-ngr/Arch/$arch

Install the basic package groups:

sudo pacman -Syy gnustep-ngr gnustep-ngr-dev gnustep-ngr-desktop

If you use Manjaro it is possible you need to switch to the testing or unstable branch as that repo is built against Arch packages/dependencies. Currently you are ok with stable.

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install x-window-system-core wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Platform:Linux

2021-02-22T20:18:24Z

Letterus: /* Archlinux */

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Archlinux ==

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app], [https://build.opensuse.org/project/show/home:letterus:gnustep-ngr list of packages]

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install x-window-system-core wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Platform:Linux

2021-02-22T20:17:31Z

Letterus: /* Archlinux */

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Archlinux ==

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR].

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app gnustep.app]

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install x-window-system-core wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Platform:Linux

2021-02-22T20:17:11Z

Letterus: /* Archlinux */ Added info on how to obtain current GNUstep packages

{{stub}}

== ALT Linux ==

Includes [http://packages.altlinux.org/en/search?query=gnustep- quite a few packages] within Sisyphus the unstable development repository as of April 2014 with most of them being maintained in stable t7/branch as well; there's no metapackage so far, so

apt-get install gnustep-base

and start deploying apps you'd like to see:

apt-get install gnustep-gworkspace gnustep-Affiche

There's an installable [http://en.altlinux.org/Starterkits/gnustep LiveCD] as well.

== Archlinux ==

For make and base there are official [https://www.archlinux.org/packages/?q=GNUstep Packages].

For all the other libraries and apps there are packaging sources at the [https://aur.archlinux.org/packages/?K=gnustep AUR]

There is a repo with prebuilt, currently unstable packages using libobjc2 over there: [https://gnustep.app]

== Debian / Ubuntu ==
=== Debian ===
Since Debian ''Sarge'' (3.1) you can use '''apt-get''' to obtain GNUstep packages.

# apt-get install x-window-system-core wmaker gnustep gnustep-devel gnustep-games

to install GNUstep, X11 and Window Maker.

The best way to get up-to-date GNUstep packages is to upgrade from ''stable'' to ''testing'' or ''unstable''. If upgrading to Debian ''unstable'' is not desirable it is possible to simply add the unstable apt lines to the sources.list and specify the distribution when installing the packages, e.g.
# apt-get install -t unstable gnumail.app
This method might upgrade some other packages to satisfy dependencies, but will have a much smaller impact on the system since only the packages on which GNUstep depends will be upgraded.

=== Ubuntu ===
As Ubuntu is Debian-based you can likewise install gnustep libraries (and their dependencies) via
sudo apt-get install gnustep gnustep-devel
apt will also suggest a lot of apps to install.

=== Install from source ===
See [[GNUstep_under_Ubuntu_Linux]] for detailed instructions for Ubuntu and Debian. At the repository mentioned there you will see efforts to collect scripts that are able to build a working GNUstep runtime under different GNU/Linux distributions (Ubuntu and Debian currently).

There is also a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

There are some general, but somewhat outdated instructions using the old SVN at [[GNUstep_SVN_installation_guide]].

=== Dependencies ===

If you want to compile from source install the following [[Dependencies]] packages (applies to both Debian and Ubuntu):

<tt>gobjc, libx11-dev, libx11-xft, libxmu-dev, libtiff4-dev, libpng12-dev, libungif4-dev, libart-2.0-dev, libxml2-dev, libxslt1-dev, libssl-dev, libgmp3-dev, libffcall1-dev, libcairo2-dev</tt> (universe), and <tt>svn</tt> if you want to download the svn version.

Optional: <tt>libaspell-dev</tt> for [[GSspell.service]]

== Fedora ==

This section needs updating.
Fedora 14 users can install GNUstep via rpm. See the [http://fedoraproject.org/wiki/Features/GNUstep Features] page.

== Gentoo ==
To install GNUstep libs and scripts, do
emerge gnustep-env
For a list of GNUstep-related ebuilds, see the [http://packages.gentoo.org/search/?sstring=gnustep Online Package Database].
For the most recent packages, type <code>ACCEPT_KEYWORDS="~x86" emerge package-name</code> (or analogically for your cpu family: <tt>"~sparc"</tt>, <tt>"~ppc"</tt> ...)

== Slackware ==

=== Version 10.2 ===
Libraries and accompanying applications will build with no modifications. Slackware 10.2 ships with GCC 3.3.6, so mixed Objective-C and C++ code is not supported, meaning additional frameworks/libraries may not be supported.

=== Version 11.0 ===
This version of Slackware works the same as the previous (10.2). Libraries and applications will build with no modifications, but due to the GCC version used (3.4.6) Objective-C++ is not supported.

=== Version 12.0 ===
GNUstep compiles and install on Slackware 12.0 perfectly. Unfortunately, this version of Slackware does not include an Objective-C++ compiler.

=== Version 12.2 ===
==== Packages ====
Slackware packages have been created and can be found in:
* [ftp://ftp.gnustep.org/pub/gnustep/binaries/slackware/ GNUstep FTP] (Please read gnustep-core.README before installing)
==== Build Scripts ====
SlackBuild scripts can be found at:
* [http://slackbuilds.org/result/?search=gnustep SlackBuilds.org GNUstep scripts]

== OpenSuse ==
Packages for GNUstep releases can be found on the Open Build Service ([https://build.opensuse.org/project/show?project=X11%3AGNUstep OBS]).

=== Version 11.3 ===
The package of pixman that comes with OpenSuse 11.3 seems to be broken for some graphic drivers. You may either downgrade or upgrade to another version of pixman (plus cairo) or use a different GNUstep backend.
For me upgrading to the cairo version as provided by the GNOME Factory project on the OpenSuse Build Service worked perfectly. [http://software.opensuse.org/ymp/GNOME:Factory/openSUSE_11.3/libcairo2.ymp?base=openSUSE%3A11.3&query=cairo]

=== Version 11.4 ===
Packages provided by Richard Stonehouse [http://www.rstonehouse.co.uk/extras/gnustep-general/index.html here] (including installation instructions).

=== Version 12.1 ===
=== Version 12.2 ===

These versions require that you install a few dev packages (e.g. libffi dev, cairo dev, ...), then GNUstep SVN compiles out of the box.

[[Category:Development]]

Themes

2020-05-12T11:19:00Z

Letterus: Add how to install a theme.

Here is a list of themes for your GNUstep Apps. This will help integrate GNUstep with your desktop environment of choice.

== Install ==

If the theme needs to be compiled, install it by using <code>make install</code>. If you have a simple .theme-Bundle, simply copy the whole bundle to <code><GNUstepdir>/Local/Library/Themes/</code>.

Then you should be able set the themes using [[SystemPreferences.app]], or using the command:

<code>
defaults write NSGlobalDomain GSTheme THEME-NAME
</code>

== User Maintained Themes ==

* [[Silver.theme]] Theme with silvered controls and scrollbars at right side.
* [https://github.com/AlessandroSangiuliano/rik.theme Rik] - A Mac-like theme for GNUstep.
* [https://github.com/BertrandDekoninck/NarcissusRik NarcissusRik] - The Narcissus theme from Etoile project (see below) using Rik icons.
* [https://github.com/BertrandDekoninck/NesedahRik NesedahRik] - The Nesedah theme using Rik icons.
* [https://github.com/BertrandDekoninck/Sombre Sombre] - A fresh dark theme from Bertrand Dekoninck.

== GNUstep Maintained Themes ==

The GnomeTheme has been renamed to Gtk.theme.
It will read the current Gtk theme and apply style information to your current GNUstep setup.
It is available on the official GNUstep GitHub:

https://github.com/gnustep/plugins-themes-Gtk

WinUXTheme is the theme for a Windows-like look and feel:

https://github.com/gnustep/plugins-themes-WinUXTheme

== GNUstep Application Project Themes ==
You find more at [http://www.nongnu.org/gap/themes/ GAP].

== Etoile Themes (outdated) ==
* [[Camaelon]]

* [http://etoileos.com/etoile/mockups/narcissus/ Narcissus]

[[Category:Themes]]

Building GNUstep under Debian FreeBSD

2020-04-30T17:27:22Z

Letterus: /* Download GNUSTEP */ Add the hint to get git submodules for libobjc2

Here's a tutorial on how to to build gnustep and its dependencies if you want to run it using GNUstep runtime 2.0 (ng), which has to be built using clang 8.0.

You'll find these steps bundled in a script which you can execute under Debian 9 at https://github.com/plaurent/gnustep-build/tree/master/debian-9-clang-8.0-runtime-2.0.

== Install empty VM ==

We start with an empty Debian9 or FreeBSD 12 VM.

== Dependencies under Debian 9 ==

we install these packages under Debian as they are coming up as dependencies anyhow

apt-get install dirmngr
sudo apt -y install build-essential git subversion \
libpthread-workqueue0 libpthread-workqueue-dev \
libxml2 libxml2-dev \
libffi6 libffi-dev \
libicu-dev \
libuuid1 uuid-dev uuid-runtime \
libsctp1 libsctp-dev lksctp-tools \
libavahi-core7 libavahi-core-dev \
libavahi-client3 libavahi-client-dev \
libavahi-common3 libavahi-common-dev libavahi-common-data \
libgcrypt20 libgcrypt20-dev \
libtiff5 libtiff5-dev \
libbsd0 libbsd-dev \
util-linux-locales \
locales-all \
libjpeg-dev \
libtiff-dev \
libcups2-dev \
libfreetype6-dev \
libcairo2-dev \
libxt-dev \
libgl1-mesa-dev \
libpcap-dev \
libc-dev libc++-dev libc++1 \
python-dev swig \
libedit-dev libeditline0 libeditline-dev readline-common \
binfmt-support libtinfo-dev \
bison flex m4 wget \
libicns1 libicns-dev \
libxslt1.1 libxslt1-dev \
libxft2 libxft-dev \
libflite1 flite1-dev \
libxmu6 libxpm4 wmaker-common \
libgnutls30 libgnutls28-dev \
libpng-dev libpng16-16 \
default-libmysqlclient-dev \
libpq-dev \
libstdc++-6-dev \
libreadline7 libreadline-dev \gobjc-6 gobjc++-6 \
libgif7 libgif-dev libwings3 libwings-dev libwraster5 \
libwraster-dev libwutil5 \
libcups2-dev libicu57 libicu-dev \
gobjc++ \
xorg \
libfreetype6 libfreetype6-dev \
libpango1.0-dev \
libcairo2-dev \
libxt-dev libssl-dev \
libasound2-dev libjack-dev libjack0 libportaudio2 \
libportaudiocpp0 portaudio19-dev \
libstdc++-6-dev libstdc++-6-doc libstdc++-6-pic \
libstdc++6 wmaker cmake cmake-curses-gui xpdf

== Dependencies under FeeBSD 12 ==

pkg install git \
autoconf \
automake \
cmake \
subversion \
wget \
bash \
pkgconf \
sudo \
gmake \
windowmaker \
jpeg \
tiff \
png \
libxml2 \
libxslt \
gnutls \
libffi \
icu \
cairo \
avahi \
portaudio \
flite \
pngwriter \
mariadb103-client \
postgresql96-client \
bash \
clang \
lldb

== We install a decent clang compiler. ==

clang-8: from clang8 repository: Add a file /etc/apt/sources.d/llvm.list with content

deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main

To install you call it like this:

apt-get update
apt-get install clang-8 lldb-8 lld-8

Note: clang-7 has a bug which makes gnustep-base fail during its ./configure phase.

(Note today clang-8 was no longer in the llvm repo for some reason. Maybe temporary issue. I also tried the bleeding edge clang-9 and that worked similarly)

Under FreeBSD we use the clang compiler which comes with FreeBSD12.
If you use CentOS 7 or the like, you probably have to compile the clang compiler from source. this is time consuming and can be done like tis:

git clone https://git.llvm.org/git/llvm.git/
cd llvm/tools
git clone https://git.llvm.org/git/clang.git/
cd ../projects
git clone https://git.llvm.org/git/compiler-rt.git/
cd ..
mkdir BUILD
cd BUILD
cmake .. -DCMAKE_BUILD_TYPE=Release make -j8
make install

(note this installs your compiler in /usr/local/bin so you have to change the path on the later stages below)

== Download GNUSTEP ==

We download the sources we need. Make sure you use <code>--recursive</code> for libobjc2 to get the git submodule(s) as well:

mkdir gnustep
cd gnustep
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.15.tar.gz
git clone https://github.com/apple/swift-corelibs-libdispatch
git clone https://github.com/gnustep/scripts
git clone https://github.com/gnustep/make
git clone --recursive https://github.com/gnustep/libobjc2
git clone https://github.com/gnustep/base
git clone https://github.com/gnustep/corebase
git clone https://github.com/gnustep/gui
git clone https://github.com/gnustep/back
./scripts/install-dependencies

The last step should basically not show any additional dependency we have not already covered. On FreeBSD , the last step has to be skipped as the script is not prepared for FreeBSD yet.

== libiconv ==

This applies for Debian 9 (or maybe older). From Debian 10 upwards you won't need to install libiconv. You do not have to do this when installing for Ubuntu.

For Debian 9 (and older?): We compile libiconv. Debian comes standard with version 1.14 but there was an issue in 1.14 which got fixed in 1.15 which was relevant to us so using 1.15 is recommended.

tar -xvzf libiconv-1.15.tar.gz
cd libiconv-1.15
./configure --enable-static --enable-dynamic
make
make install
cd ..

== Defaults ==

We set some environment defaults for the remainder of the session

# we set the C and C++ compiler version
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export RUNTIME_VERSION=gnustep-2.0
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD=/usr/bin/ld.gold
export LDFLAGS=-fuse-ld=/usr/bin/ld.gold
export OBJCFLAGS="-fblocks"

Using the ld.gold linker is important as otherwise strange things happens. old ld does stuff wrong, newer lld from clang optimises stuff away it shouldn't.

== libdispatch ==

The libdispatch is an open source library supplied by Apple which takes care of running multiple background tasks. Apple calls it "Grand Central Dispatch". The Swift language also uses it, hence the repo name. We're not really directly using it but other objc code might use it or benefit from it so we compile it as well.

cd swift-corelibs-libdispatch
mkdir build
cd build
cmake .. -DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_BUILD_TYPE=Release \
-DUSE_GOLD_LINKER=YES
make -j40
make install
ldconfig

== libobjc2 / gnustep-base ==

Now we have reached a point where the magic triple libobjc2 + gnustep-make + gnustep-base comes into play. To understand the context here. The objectiveC compiler needs a runtime. The runtime is taking care of the basic functionality of objectiveC objects such as their memory allocation and release and other stuff. The compiler calls the runtime when specific stuff happens. When a method is called, the compiler puts a call into the runtime which then looks up the dynamic methods and calls the method etc. When a block ends and certain objects are no longer needed, the compiler calls the runtime so it can release the objects accordingly.

There are different runtimes around. The original objectiveC runtime supplied by the gcc compiler. It's old, outdated and doesn't deal with automatic reference counting and a lot of other things. So it's not recommended. The libobjc2 is the "modern" rewrite for a runtime and is actually based on a project called Etoile. It's ABI has different variants. There is a fragile and a non fragile ABI.

Read this blogpost to understand what the difference is: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_explain_Non-fragile_ivars.html
If you get this is wrong, you might end up with objects no longer using the right position of variables in the data of super or subclasses and things can get totally out of control. So the new non-fragile-ABI is really the way to go. There are also different versions of the ABI on how the compiler calls the runtime. So the compiler and the runtime are working together as a team.

So once we have a runtime library which is a requirement for any objectiveC code, there is also the base library gnustep-base which corresponds to Apple's Foundation framework. This one implements basic functionality which is used in almost all ObjC code.. It brings stuff like dealing with strings, arrays, dictionaries, and lots of other things you need day in day out. It does not supply any GUI code. All NextStep/Apple ObjectiveC code is derived from a base class called NSObject which is defined in gnustep-base. GnuStep is an open source reimplementation of NextStep and the Apple Foundation/AppKit classes.

There are 3 other libraries in GnuStep which are gnustep-gui which does all the graphical interface, gnustep-back which is the backend for the GUI (so there's a variant for X-windows, one for Windows, one for MacOS aqua etc) which is like a driver for the gui to do the displaying on actual hardware and there is gnustep-corebase which is a glue library to use objective C objects from C and to deal with the fundamental data types of objective C like NSData, NSArray etc.

== compiling libobjc2 ==

cd libobjc2
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DBUILD_STATIC_LIBOBJC=1 \
-DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_LINKER=${LD} \
-DCMAKE_MODULE_LINKER_FLAGS=${LDFLAGS}
make -j40
make install
ldconfig
make test
cd ../..

this should pass everywhere except these two which according to David Chisnal are corner cases which shouldn't affect real software:

18 - AssociatedObject_optimised (OTHER_FAULT)
20 - AssociatedObject_legacy_optimised (OTHER_FAULT)

== installing gnustep-make ==

Gnustep Make is a package of makefiles to be used inside Gnustep projects. This way some common settings can be shared along all projects such as the location of certain runtime files (defaults, file layouts etc). It does not have any compiled code but its needed for the rest.
Edit the file library-combo.make and on line 47 replace

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-1.8
endif

with

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-2.0
endif

Please note: Instead of editing the make file you can set the runtime version using the env variable as well:

export RUNTIME_VERSION=gnustep-2.0

or

export RUNTIME_VERSION=gnustep-1.9

For the older runtime.
Then you can install make

cd make
./configure \
--with-layout=fhs \
--disable-importing-config-file \
--enable-native-objc-exceptions \
--enable-objc-arc \
--enable-install-ld-so-conf \
--with-library-combo=ng-gnu-gnu \
--with-config-file=/usr/local/etc/GNUstep/GNUstep.conf \
--with-user-config-file='.GNUstep.conf' \
--with-user-defaults-dir='GNUstep/Library/Defaults'
make
make install

== installing gnustep-base ==

cd base
./configure --with-config-file=/usr/local/etc/GNUstep/GNUstep.conf
make -j8
make install
ldconfig
make check
cd ..

There is one test which will fail. For our usage this is not vital.

Failed test: basic.m:31 ... Expiration date can be retrieved

== installing gnustep-corebase ==

cd corebase
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-gui ==

cd gui
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-back ==

cd back
./configure
make -j8
make install
ldconfig
cd ..

Author: Andreas Fink as of 2019-05-05.

Building GNUstep under Debian FreeBSD

2020-04-30T17:21:33Z

Letterus: /* Dependencies under Debian 9 */ Remove Ubuntu keys, not needed

Here's a tutorial on how to to build gnustep and its dependencies if you want to run it using GNUstep runtime 2.0 (ng), which has to be built using clang 8.0.

You'll find these steps bundled in a script which you can execute under Debian 9 at https://github.com/plaurent/gnustep-build/tree/master/debian-9-clang-8.0-runtime-2.0.

== Install empty VM ==

We start with an empty Debian9 or FreeBSD 12 VM.

== Dependencies under Debian 9 ==

we install these packages under Debian as they are coming up as dependencies anyhow

apt-get install dirmngr
sudo apt -y install build-essential git subversion \
libpthread-workqueue0 libpthread-workqueue-dev \
libxml2 libxml2-dev \
libffi6 libffi-dev \
libicu-dev \
libuuid1 uuid-dev uuid-runtime \
libsctp1 libsctp-dev lksctp-tools \
libavahi-core7 libavahi-core-dev \
libavahi-client3 libavahi-client-dev \
libavahi-common3 libavahi-common-dev libavahi-common-data \
libgcrypt20 libgcrypt20-dev \
libtiff5 libtiff5-dev \
libbsd0 libbsd-dev \
util-linux-locales \
locales-all \
libjpeg-dev \
libtiff-dev \
libcups2-dev \
libfreetype6-dev \
libcairo2-dev \
libxt-dev \
libgl1-mesa-dev \
libpcap-dev \
libc-dev libc++-dev libc++1 \
python-dev swig \
libedit-dev libeditline0 libeditline-dev readline-common \
binfmt-support libtinfo-dev \
bison flex m4 wget \
libicns1 libicns-dev \
libxslt1.1 libxslt1-dev \
libxft2 libxft-dev \
libflite1 flite1-dev \
libxmu6 libxpm4 wmaker-common \
libgnutls30 libgnutls28-dev \
libpng-dev libpng16-16 \
default-libmysqlclient-dev \
libpq-dev \
libstdc++-6-dev \
libreadline7 libreadline-dev \gobjc-6 gobjc++-6 \
libgif7 libgif-dev libwings3 libwings-dev libwraster5 \
libwraster-dev libwutil5 \
libcups2-dev libicu57 libicu-dev \
gobjc++ \
xorg \
libfreetype6 libfreetype6-dev \
libpango1.0-dev \
libcairo2-dev \
libxt-dev libssl-dev \
libasound2-dev libjack-dev libjack0 libportaudio2 \
libportaudiocpp0 portaudio19-dev \
libstdc++-6-dev libstdc++-6-doc libstdc++-6-pic \
libstdc++6 wmaker cmake cmake-curses-gui xpdf

== Dependencies under FeeBSD 12 ==

pkg install git \
autoconf \
automake \
cmake \
subversion \
wget \
bash \
pkgconf \
sudo \
gmake \
windowmaker \
jpeg \
tiff \
png \
libxml2 \
libxslt \
gnutls \
libffi \
icu \
cairo \
avahi \
portaudio \
flite \
pngwriter \
mariadb103-client \
postgresql96-client \
bash \
clang \
lldb

== We install a decent clang compiler. ==

clang-8: from clang8 repository: Add a file /etc/apt/sources.d/llvm.list with content

deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main

To install you call it like this:

apt-get update
apt-get install clang-8 lldb-8 lld-8

Note: clang-7 has a bug which makes gnustep-base fail during its ./configure phase.

(Note today clang-8 was no longer in the llvm repo for some reason. Maybe temporary issue. I also tried the bleeding edge clang-9 and that worked similarly)

Under FreeBSD we use the clang compiler which comes with FreeBSD12.
If you use CentOS 7 or the like, you probably have to compile the clang compiler from source. this is time consuming and can be done like tis:

git clone https://git.llvm.org/git/llvm.git/
cd llvm/tools
git clone https://git.llvm.org/git/clang.git/
cd ../projects
git clone https://git.llvm.org/git/compiler-rt.git/
cd ..
mkdir BUILD
cd BUILD
cmake .. -DCMAKE_BUILD_TYPE=Release make -j8
make install

(note this installs your compiler in /usr/local/bin so you have to change the path on the later stages below)

== Download GNUSTEP ==

We download the sources we need:

mkdir gnustep
cd gnustep
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.15.tar.gz
git clone https://github.com/apple/swift-corelibs-libdispatch
git clone https://github.com/gnustep/scripts
git clone https://github.com/gnustep/make
git clone https://github.com/gnustep/libobjc2
git clone https://github.com/gnustep/base
git clone https://github.com/gnustep/corebase
git clone https://github.com/gnustep/gui
git clone https://github.com/gnustep/back
./scripts/install-dependencies

The last step should basically not show any additional dependency we have not already covered. On FreeBSD , the last step has to be skipped as the script is not prepared for FreeBSD yet.

== libiconv ==

This applies for Debian 9 (or maybe older). From Debian 10 upwards you won't need to install libiconv. You do not have to do this when installing for Ubuntu.

For Debian 9 (and older?): We compile libiconv. Debian comes standard with version 1.14 but there was an issue in 1.14 which got fixed in 1.15 which was relevant to us so using 1.15 is recommended.

tar -xvzf libiconv-1.15.tar.gz
cd libiconv-1.15
./configure --enable-static --enable-dynamic
make
make install
cd ..

== Defaults ==

We set some environment defaults for the remainder of the session

# we set the C and C++ compiler version
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export RUNTIME_VERSION=gnustep-2.0
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD=/usr/bin/ld.gold
export LDFLAGS=-fuse-ld=/usr/bin/ld.gold
export OBJCFLAGS="-fblocks"

Using the ld.gold linker is important as otherwise strange things happens. old ld does stuff wrong, newer lld from clang optimises stuff away it shouldn't.

== libdispatch ==

The libdispatch is an open source library supplied by Apple which takes care of running multiple background tasks. Apple calls it "Grand Central Dispatch". The Swift language also uses it, hence the repo name. We're not really directly using it but other objc code might use it or benefit from it so we compile it as well.

cd swift-corelibs-libdispatch
mkdir build
cd build
cmake .. -DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_BUILD_TYPE=Release \
-DUSE_GOLD_LINKER=YES
make -j40
make install
ldconfig

== libobjc2 / gnustep-base ==

Now we have reached a point where the magic triple libobjc2 + gnustep-make + gnustep-base comes into play. To understand the context here. The objectiveC compiler needs a runtime. The runtime is taking care of the basic functionality of objectiveC objects such as their memory allocation and release and other stuff. The compiler calls the runtime when specific stuff happens. When a method is called, the compiler puts a call into the runtime which then looks up the dynamic methods and calls the method etc. When a block ends and certain objects are no longer needed, the compiler calls the runtime so it can release the objects accordingly.

There are different runtimes around. The original objectiveC runtime supplied by the gcc compiler. It's old, outdated and doesn't deal with automatic reference counting and a lot of other things. So it's not recommended. The libobjc2 is the "modern" rewrite for a runtime and is actually based on a project called Etoile. It's ABI has different variants. There is a fragile and a non fragile ABI.

Read this blogpost to understand what the difference is: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_explain_Non-fragile_ivars.html
If you get this is wrong, you might end up with objects no longer using the right position of variables in the data of super or subclasses and things can get totally out of control. So the new non-fragile-ABI is really the way to go. There are also different versions of the ABI on how the compiler calls the runtime. So the compiler and the runtime are working together as a team.

So once we have a runtime library which is a requirement for any objectiveC code, there is also the base library gnustep-base which corresponds to Apple's Foundation framework. This one implements basic functionality which is used in almost all ObjC code.. It brings stuff like dealing with strings, arrays, dictionaries, and lots of other things you need day in day out. It does not supply any GUI code. All NextStep/Apple ObjectiveC code is derived from a base class called NSObject which is defined in gnustep-base. GnuStep is an open source reimplementation of NextStep and the Apple Foundation/AppKit classes.

There are 3 other libraries in GnuStep which are gnustep-gui which does all the graphical interface, gnustep-back which is the backend for the GUI (so there's a variant for X-windows, one for Windows, one for MacOS aqua etc) which is like a driver for the gui to do the displaying on actual hardware and there is gnustep-corebase which is a glue library to use objective C objects from C and to deal with the fundamental data types of objective C like NSData, NSArray etc.

== compiling libobjc2 ==

cd libobjc2
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DBUILD_STATIC_LIBOBJC=1 \
-DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_LINKER=${LD} \
-DCMAKE_MODULE_LINKER_FLAGS=${LDFLAGS}
make -j40
make install
ldconfig
make test
cd ../..

this should pass everywhere except these two which according to David Chisnal are corner cases which shouldn't affect real software:

18 - AssociatedObject_optimised (OTHER_FAULT)
20 - AssociatedObject_legacy_optimised (OTHER_FAULT)

== installing gnustep-make ==

Gnustep Make is a package of makefiles to be used inside Gnustep projects. This way some common settings can be shared along all projects such as the location of certain runtime files (defaults, file layouts etc). It does not have any compiled code but its needed for the rest.
Edit the file library-combo.make and on line 47 replace

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-1.8
endif

with

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-2.0
endif

Please note: Instead of editing the make file you can set the runtime version using the env variable as well:

export RUNTIME_VERSION=gnustep-2.0

or

export RUNTIME_VERSION=gnustep-1.9

For the older runtime.
Then you can install make

cd make
./configure \
--with-layout=fhs \
--disable-importing-config-file \
--enable-native-objc-exceptions \
--enable-objc-arc \
--enable-install-ld-so-conf \
--with-library-combo=ng-gnu-gnu \
--with-config-file=/usr/local/etc/GNUstep/GNUstep.conf \
--with-user-config-file='.GNUstep.conf' \
--with-user-defaults-dir='GNUstep/Library/Defaults'
make
make install

== installing gnustep-base ==

cd base
./configure --with-config-file=/usr/local/etc/GNUstep/GNUstep.conf
make -j8
make install
ldconfig
make check
cd ..

There is one test which will fail. For our usage this is not vital.

Failed test: basic.m:31 ... Expiration date can be retrieved

== installing gnustep-corebase ==

cd corebase
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-gui ==

cd gui
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-back ==

cd back
./configure
make -j8
make install
ldconfig
cd ..

Author: Andreas Fink as of 2019-05-05.

Installation Instructions

2020-04-30T17:20:03Z

Letterus: Most installation guides are on the user page. Link to that one.

Please see [[User Guides]] for some general and up to date instructions on how to install GNUstep.

== Platform specific installation information ==
For information on how to install [[Dependencies]] or or about installation on exotic systems (like [[Windows]]), see
<big>[[Platform compatibility]]</big>!

== Links ==
* [http://gnustep.made-it.com/BuildGuide/ Build-Guide for Unix-like systems] describes installation and configuration step-by-step.

Platform:BSD

2020-04-15T14:06:30Z

Letterus: /* Install and compile */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14, 10.15.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install pkgconfig
brew install gnutls
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

It might be better to ''not'' use <code>--disable-importing-config-file</code>, as that option might break the setup (10.14).

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-15T10:40:50Z

Letterus: /* Install and compile */ Remove unnecessary flags

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14, 10.15.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install pkgconfig
brew install gnutls
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

It migh be better to ''don't'' use <code>--disable-importing-config-file</code>, as that option might break the setup (10.14).

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-15T10:38:14Z

Letterus: /* Extensions / Base Additions Install */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14, 10.15.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install pkgconfig
brew install gnutls
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

It migh be better to ''don't'' use <code>--disable-importing-config-file</code>, as that option might break the setup (10.14).

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-15T10:37:44Z

Letterus: /* Install and compile */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install pkgconfig
brew install gnutls
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

It migh be better to ''don't'' use <code>--disable-importing-config-file</code>, as that option might break the setup (10.14).

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-15T05:57:43Z

Letterus: /* Dependencies */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install pkgconfig
brew install gnutls
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-15T05:57:13Z

Letterus: /* Set environment variables */ Removed unneeded env vars

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

User Guides

2020-04-15T05:55:37Z

Letterus: /* Installing GNUstep */ Removed links without helpful information.

This page is intended as a collection of guides for users.

== Installing GNUstep ==

Installation can be easy or complex, depending on the system you use. If you encounter problems that aren't discussed here, please [[Get Help|ask for help on the mailing lists]].

* Instructions on how to install on [[Platform:BSD|BSD]] or [[Platform:Linux|Linux]].
* Comprehensive [http://gnustep.made-it.com/BuildGuide/ build guide] for GNUstep on GNU/Linux.

== Configuration ==

* [http://www.gnustep.org/resources/documentation/User/Gui/KeyboardSetup.html User Keyboard Setup]
* [http://www.gnustep.org/resources/documentation/User/Gui/LanguageSetup.html Setup for East Asian Languages]
* User Defaults ([http://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html GUI]) ([http://www.gnustep.org/resources/documentation/Developer/Back/General/DefaultsSummary.html Back])

== Advanced installation ==

* [[GNUstep SVN Installation Guide]]
* [http://svn.gna.org/svn/etoile/trunk/Etoile/INSTALL.Ubuntu GNUstep and Étoilé dependency list]
* [[Building GNUstep with Clang]]
* [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]]
* [http://artinamessage.wordpress.com/2013/06/03/gnustep-install-with-clang-blocks-and-grand-central-dispatch-gcd/ Building GNUstep with clang, blocks, and Grand Central Dispatch]
* [[Raspbian Install| Raspbian Install]]

== Using GNUstep ==

* [[:Category:Applications|User Applications]]
* [http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem_toc.html Filesystem Layout] ([http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem.pdf PDF])
* [[User_FAQ|GNUstep Users' FAQ]] ([http://www.gnustep.org/resources/documentation/User/GNUstep/userfaq.pdf PDF])
* [[Get Help|Mailing Lists, IRC and Newsgroups]]
* [[Cross Compiling]]
* [http://gnustep.files.wordpress.com/2010/11/objective-c_gnustep.pdf Manual de Objective-C y GNUstep (PDF en español)]
* [[Themes|Changing GNUstep Theme]]

== Other Info ==

* News and info:
** [http://freecode.com/tags/objective-c Freshmeat] ->Freecode Effective 2014-06-18 Freecode is no longer being updated (content may be stale).
** [http://www.gnustep.wordpress.com/ GNUstep en español] - Noticias e información
* Projects:
** [[:Category:Desktop Environments|Desktop Environments]]
*** [http://www.nongnu.org/backbone/ Backbone] - GNUstep Desktop project
*** [http://www.etoile-project.org/ Étoilé] - GNUstep based user environment
*** [http://www.nongnu.org/gap/ GAP] - GNUstep Application Project
*** [https://trunkmaster.github.io/ Nextspace] - GNUstep based Desktop project
** Live CDs
*** [http://livecd.gnustep.org/ GNUSTEP Live CD] - based on Debian
*** ALT Linux based (i586/x86_64, BIOS/UEFI, considerable number of GNUstep/Étoilé apps):
**** [http://en.altlinux.org/Starterkits/gnustep GNUstep starterkit] - updated quarterly (as of June 2014) using stable package branch
**** [http://en.altlinux.org/Regular#experimental Regular GNUstep] - updated [http://nightly.altlinux.org/sisyphus/flavours/gnustep/ weekly] using unstable development branch
* Developer sites:
** [[For_Developers | Developers]] - List of developers
** [http://www.gnustep.it/ GNUstep.it] - Italian developer site
** [http://www.collaboration-world.com/ Collaboration World] - home to GNUMail, Affiche and more
** [http://www.roard.com/docs/ GNUstep HelpCenter]
** [http://www.aiei.ch/gnustep/icons/icons.html GNUstep Icons project]
* [[Success_Stories | GNUstep Success Stories]]

== Stores ==

Platform:BSD

2020-04-14T21:33:38Z

Letterus: /* Extensions / Base Additions Install */ Fix: Just let gnutls be found by pkgconfig by adding its path

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/gnutls/lib/pkgconfig:$PKG_CONFIG_PATH"

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

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-14T21:28:56Z

Letterus: /* Install and compile */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Preparations / Fixes ====

Manually create <code>/usr/local/bin/libgnutls-config</code> with the following content:

#!/bin/bash
pkg-config $1 gnutls

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH=/usr/local/opt/icu4c/lib/pkgconfig:"$PKG_CONFIG_PATH"

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

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep project and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-14T21:28:21Z

Letterus: /* Mac OS X */

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Preparations / Fixes ====

Manually create <code>/usr/local/bin/libgnutls-config</code> with the following content:

#!/bin/bash
pkg-config $1 gnutls

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH=/usr/local/opt/icu4c/lib/pkgconfig:"$PKG_CONFIG_PATH"

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

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep projekt and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-14T21:27:21Z

Letterus: /* Install and compile */ Added hint for make options

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Preparations / Fixes ====

Manually create <code>/usr/local/bin/libgnutls-config</code> with the following content:

#!/bin/bash
pkg-config $1 gnutls

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH=/usr/local/opt/icu4c/lib/pkgconfig:"$PKG_CONFIG_PATH"

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

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

'''Don't''' use <code>--disable-importing-config-file</code>, that option will break the setup.

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep projekt and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Platform:BSD

2020-04-14T21:24:48Z

Letterus: /* Extensions Install */ Updated the instruction to reflect how install base additions under macOS 10.14

{{stub}}

= Darwin =

=== Intel ===
Currently tested on Darwin 7.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)

Default compiler (Apple GCC) has unknown problems. Download the FSF GCC compiler (mirrors at http://gcc.gnu.org/mirrors.html) and configure it with -enable-threads=posix. You don't need binutils or anything else. Use the GNU runtime. Make sure to add

export CC=/usr/local/bin/gcc (use the correct path to FSF gcc)

so that the correct compiler is found

'''Extra libs needed'''
 Use libffi from http://sourceware.org/libffi/ or the older ffcall if this does not work for some reason.

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

=== PowerPC ===
This section is for building the complete GNUstep system. This system will not interact at all with Mac OS X/Cocoa. It uses different compilers, different display systems, etc. For building GNUstep extensions to be used with Mac OS X (for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail), see the MacOSX/PowerPC section.

Currently tested on Darwin 6.x, 7.x, 8.x

'''Recommended compiler'''
 gcc 3.3.2 or greater 3.3.* versions. Older versions will not compile on Darwin and 3.4.* versions don't support GNU runtime compilation on Darwin currently (The GCC bug report is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572).
 gcc 4.0.3 or greater 4.* versions (the bug mentioned above has been fixed for 4.0.3 and newer)
 Apple GCC with Xcode 2.5.

'''Extra libs needed'''
 Use libffi (not ffcall). This should be enabled by default in gnustep-base so you don't have to type --enable-libffi. For 6.x, you need the dlcompat library (from www.opendarwin.org) to load bundles (not needed for 7.x).

'''Special Instructions'''
 Read the README.Darwin file in the gnustep-make/Documentation directory for complete instructions.

See also the [[Platform:BSD#Mac_OS_X|Mac OSX / PowerPC]] section

= FreeBSD-based systems =

== DesktopBSD ==
[http://www.desktopbsd.net/ DesktopBSD] joins the ranks of [[#PC-BSD|PC-BSD]] and [[#FreeSBIE|FreeSBIE]] as a desktop-ready version of [[#FreeBSD|FreeBSD]]. However, their desktop is based on [http://www.kde.org KDE].

== DragonFly ==
[http://www.dragonflybsd.org DragonFly] is an operating system and environment designed to be the logical continuation of the [[#FreeBSD|FreeBSD]]-4.x OS series.

I have mostly ported GNUstep to DragonFly, I just need to submit patches now for both GNUstep and DragonFly. To know more, you can contact me. ''[[user:Qmathe | Quentin Mathé]]''

== FreeBSD ==
You can install GNUstep using the ''[http://www.freebsd.org/cgi/url.cgi?ports/devel/gnustep/pkg-descr /usr/ports/devel/gnustep/]'' meta port. To automatically install GNUstep '''and''' (literally) tons of GNUstep-related applications, take a look at the ''[http://www.freebsd.org/cgi/url.cgi?ports/x11/gnustep-app/pkg-descr /usr/ports/x11/gnustep-app/]'' meta port.

These ports should now install all dependencies -- a complete list can [[Dependencies|be found here]].

'''Note'''
: Prior to FreeBSD-6.0, there is a bug in ''kvm(3)'' that '''requires''' a mounted ''/proc'' for GNUstep to work properly. Until this bug is fixed, make sure you have an entry for ''/proc'' in your ''/etc/fstab'':

proc /proc procfs rw 0 0

References:
[http://www.freebsd.org/cgi/ports.cgi?query=gnustep&stype=all FreeBSD GNUstep ports],
[http://www.freshports.org/search.php?stype=longdescription&method=match&query=gnustep&num=10&orderby=category&orderbyupdown=asc&search=Search Freshports GNUstep]

=== Building from scratch ===

There is a comprehensive guide on how to build GNUstep from scratch at [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]].

== FreeBSD-Kernel w/ GNU userland, and GNU C library ==
It was reported that this runs GNUstep as well. For more details see the topic of
the IRC channel #gnu-kbsd on irc.gnu.org

== FreeSBIE ==
[http://www.freesbie.org/ FreeSBIE] is a Live-CD Version of FreeBSD.

== MidnightBSD ==
[http://www.midnightbsd.org/ MidnightBSD] is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.

The most intriguing thing about MidnightBSD is their integration of GNUstep into the system.

== PicoBSD ==
[http://people.freebsd.org/~picobsd/old/picobsd.html PicoBSD] is a one floppy version of [[#FreeBSD|FreeBSD]] 3.0-current. You won't be able to use it as a platform for GNUstep.

== PC-BSD ==
[http://www.pcbsd.org/ PC-BSD] has as its goals to be an easy to install and use desktop OS, which is built on the [[#FreeBSD|FreeBSD]] operating system.

= Mac OS X =

=== Full Install ===

GNUstep *does* work on OS X 10.4 and later, too, but it will not work out of the box with the dependencies built from MacPorts (and I guess from fink either). The problem is not the Apple linker per se, but rather that many of our dependencies nowadays depend directly or indirectly on CoreFoundation on OS X and, unfortunately, CoreFoundation started to depend on Apple's libobjc in 10.4.

To successfully build and run GNUstep on Mac OS X 10.4 and later, you need (at least) to configure aspell with --disable-nls (the nonls variant of aspell should do for MacPorts). Next, you need a freetype configured with --without-old-mac-fonts (unfortunately no help from MacPorts here and the freetype shipped with Mac OS X 10.5 will not work either). Apart from that, configure GNUstep-base with --disable-tls and GNUstep-back with --disable-glx and use either the libart (the default) or xlib backend. Eventually, I may have forgotten some other libraries in this list, but you will notice that when looking at the crash report being produced in ~/Library/Logs/CrashReporter. Look for a line containing /usr/lib/libobjc.A.dylib.

See [https://github.com/ericwa/gnustep-macports-fixes Macport Patches] for patches to Macports that might also work

=== Extensions / Base Additions Install ===

This section is for building the GNUstep extensions (base additions) only. Use this if, for instance, if you want to build something based on GNUstep, such as GSWeb or GNUMail. If you want to build the complete GNUstep system independant of Mac OS X, see the Full Install section above or Darwin/PowerPC section.

Currently tested on macOS 10.14.

==== Recommended compiler ====

Default - clang. There is no gcc anymore.

==== Dependencies ====

# Install [https://brew.sh/ homebrew].
#

brew install gnutls
brew install pkgconfig
brew install icu4c

==== Preparations / Fixes ====

Manually create <code>/usr/local/bin/libgnutls-config</code> with the following content:

#!/bin/bash
pkg-config $1 gnutls

==== Set environment variables ====

Make sure these variables are set before installing gnustep-make ([https://github.com/gnustep/tools-make tools-make]) and before compiling [https://github.com/gnustep/libs-base gnustep-base additions]. You might want to add them to your <code>~/.bash_profile</code>.

export CC=clang
export CXX=clang++
export OBJCFLAGS="-fobjc-nonfragile-abi -fblocks"
export CXXFLAGS="-std=c++11"

export LDFLAGS="${LDFLAGS} -L/usr/local/opt/icu4c/lib"
export CPPFLAGS="${CPPFLAGS} -I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH=/usr/local/opt/icu4c/lib/pkgconfig:"$PKG_CONFIG_PATH"

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

==== Install and compile ====

Download tools-make and gnustep-base - either the tarballs or from git. Let's assume they are in directories named <code>tools-make</code> and <code>libs-base</code>.

cd tools-make
./configure \
--with-layout=apple \
--enable-native-objc-exceptions \
--enable-objc-arc \
--with-library-combo=apple-apple-apple
sudo -E make install

. /Library/GNUstep/Makefiles/GNUstep.sh
cd ../libs-base
./configure
make -j8 debug=yes base=no add=yes
sudo -E make install

After this you should be finished. Add the following line to your <code>~/.bash_profile</code>:

. /Library/GNUstep/Makefiles/GNUstep.sh

If you have sourced GNUstep.sh you can <code>cd</code> to any typical GNUstep projekt and build it using <code>make</code>.

See also the [[Platform:BSD#Darwin|Darwin / PowerPC]] section.

= NetBSD =
Installing GNUstep from pkgsrc is really straight-forward for NetBSD if you're using a recent pkgsrc distribution. NetBSD/i386 has no known problems right now, however there are reports of crashout problems for gdomap on NetBSD/sparc which may be related to ffi/ffcall issues.

In terms of pre-requisites, ensure you've got a working X11 environment on your system and preferrably are using WindowMaker as your window manager.

'''Build instructions'''

To install GNUstep, you need to cd to your pkgsrc tree and then cd to the right package directory, on my system:

cd /usr/pkgsrc

then go to the package you wish to install, for example:

cd meta-pkgs/gnustep

and issue the command:

make install

This command will download source code and whatever dependencies and compile and install them. The version of the meta-packages I used (released with NetBSD 2.0 and called gnustep-1.10.0nb2) installs the following GNUstep components as parts of the meta-package:

* gnustep-make-1.10.0
* gnustep-base-1.10.1
* gnustep-ssl-1.10.1
* gnustep-gui-0.9.4
* gnustep-back-0.9.4
* gnustep-examples-1.0.0
* ImageViewer-0.6.3
* Pantomime-1.1.2
* Addresses-0.4.6
* GNUMail-1.1.2
* Gorm-0.8.0
* ProjectCenter-0.4.0
* GWLib-0.6.5
* Renaissance-0.8.0
* gworkspace-0.6.5

A number of dependency packages are also installed.

This may be overkill - if you don't need all the applications etc, you can install the packages individually.

= OpenBSD =

Since many years, GNUstep is available in the OpenBSD ports tree. Packages are available for amd64, i386, and powerpc.
The packages are based on the latest releases. Since some time, using libobjc2, but compiled with the system gcc.
For easy installation, a meta package is provided.

sudo pkg_add -i gnustep-desktop

Above command will install the meta package, and all the packages from the [http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/gnustep/ x11/gnustep] part of the ports tree.

[[Category:Development]]

Integrated Development Environments for Objective C

2020-04-14T07:42:08Z

Letterus: /* Tools from the GNUstep project */

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you may want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces. For more information on Gorm and ProjectCenter also see [[Development tools]].

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known to Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

=== Xcode ===

You are not able to install Xcode using a Free Software environment. But of course it is possible to use Apple's Xcode to develop apps that are based on Foundation and AppKit. Xcode won't create a proper makefile for you. You will have to do that yourself or let ProjectCenter do the work for you. But if you use Xcode's interface builder (formerly "Interface Builder") to create graphical user interfaces utilizing [[XIB]] files instead of storyboards, GNUstep will be able to load and execute these [[XIB]] files as well.

Development tools

2020-04-14T07:40:49Z

Letterus: /* Integrated Development Environments for Objective C */

More about development tools: http://www.gnustep.org/experience/DeveloperTools.html

== Gorm - Graphical Object Relationship Modeller ==

Gorm stands for "Graphical Object Relationship Modeller" and is GNUstep's easy-to-use interface designer.

With Gorm designing tough and complex graphical interfaces for your applications can be done easily and quickl, using drag & drop, powerful inspectors and teamwork with ProjectCenter.

Gorm allows developers to quickly create and edit graphical application interfaces using a whole lot of GUI elements: windows, menus, buttons, labels, sliders, tables, textfields, browsers, images, altert panels and more. Custom palettes can be dynamically loaded to add additional elements or functionality.

After creating the interface, objects can be linked using mouse operations. Also Gorm features interactive testing of interfaces.

Please see the following wiki sections to learn tips on how to effectively utilize Gorm:

* [[Gorm Manual]]
* [[Gorm FAQ]]
* [[Gorm Installation On Windows]]

Also see the following external links:

* ''' [http://www.gnustep.org/experience/Gorm.html Official Gorm page] '''

* '''[https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gorm Debian Offical Release]'''

* '''[http://www.freshports.org/devel/gorm FreeBSD Ports]'''

== Project Center ==
''' [http://www.gnustep.org/experience/ProjectCenter.html Project Center] '''

ProjectCenter is GNUstep's integrated developement environment (IDE). It is based in part on NeXT's original Project Builder. It assists you in starting new projects and lets you manage your project files using a intuitive and well ordered graphical user interface.

* [[ProjectCenter FAQ]]

== Other tools ==

=== [[Integrated Development Environments for Objective C]] ===

Besides ProjectCenter there are several IDEs - [[Integrated Development Environments for Objective C]].

=== Unit Testing ===

GNUstep is blessed with a number of unit test frameworks:

* Traditionally, it has provided a [http://www.gnustep.org/resources/documentation/testdoc_toc.html testing environment] based around Guile, an implementation of Scheme that has been blessed as the preferred GNU scripting language. It has been hard to convince Objective-C programmers to write tests in this language, and the utility of the package has not lived up to expectations.

* GNUstep now also contains a unit testing framework intended as general framework for testing the core GNUstep libraries, called [http://lists.gnu.org/archive/html/gnustep-dev/2005-06/msg00050.html Testsuite]. This may not be suitable for more general unit testing of applications as it's been designed to operate with little of the GNUstep environment actually running. ''Tip: use this if you're describing or fixing bugs or features in base, gui etc.''

* [https://gna.org/projects/etoile Étoilé] contains a port to GNUstep of [https://github.com/etoile/UnitKit UnitKit 1.5]. This is a straight-forward unit testing environment, suited to the needs of application developers. It also works under X-code on MacOS X.

* [http://www.sente.ch/ Sen:te] have provided a unit testing environment called [http://www.sente.ch/software/ocunit/ OCUnit] which apparently works under GNUstep, although there are comments in the mailing lists about difficulty getting it working.

* Perhaps [[ObjcUnit]] is also relevant? --[[User:Svetlana|svetlana]] 01:26, 16 January 2017 (CET)

----

See also:
* [[:Category:Frameworks|Official Development Frameworks]]
* [[:Category:Development Frameworks|Development Frameworks]]

Development tools

2020-04-14T07:40:24Z

Letterus: /* Other tools */ Added link to Integrated Development Environments for Objective C.

More about development tools: http://www.gnustep.org/experience/DeveloperTools.html

== Gorm - Graphical Object Relationship Modeller ==

Gorm stands for "Graphical Object Relationship Modeller" and is GNUstep's easy-to-use interface designer.

With Gorm designing tough and complex graphical interfaces for your applications can be done easily and quickl, using drag & drop, powerful inspectors and teamwork with ProjectCenter.

Gorm allows developers to quickly create and edit graphical application interfaces using a whole lot of GUI elements: windows, menus, buttons, labels, sliders, tables, textfields, browsers, images, altert panels and more. Custom palettes can be dynamically loaded to add additional elements or functionality.

After creating the interface, objects can be linked using mouse operations. Also Gorm features interactive testing of interfaces.

Please see the following wiki sections to learn tips on how to effectively utilize Gorm:

* [[Gorm Manual]]
* [[Gorm FAQ]]
* [[Gorm Installation On Windows]]

Also see the following external links:

* ''' [http://www.gnustep.org/experience/Gorm.html Official Gorm page] '''

* '''[https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=gorm Debian Offical Release]'''

* '''[http://www.freshports.org/devel/gorm FreeBSD Ports]'''

== Project Center ==
''' [http://www.gnustep.org/experience/ProjectCenter.html Project Center] '''

ProjectCenter is GNUstep's integrated developement environment (IDE). It is based in part on NeXT's original Project Builder. It assists you in starting new projects and lets you manage your project files using a intuitive and well ordered graphical user interface.

* [[ProjectCenter FAQ]]

== Other tools ==

=== [[Integrated Development Environments for Objective C]] ===

Besides ProjectCenter there are several [[Integrated Development Environments for Objective C]].

=== Unit Testing ===

GNUstep is blessed with a number of unit test frameworks:

* Traditionally, it has provided a [http://www.gnustep.org/resources/documentation/testdoc_toc.html testing environment] based around Guile, an implementation of Scheme that has been blessed as the preferred GNU scripting language. It has been hard to convince Objective-C programmers to write tests in this language, and the utility of the package has not lived up to expectations.

* GNUstep now also contains a unit testing framework intended as general framework for testing the core GNUstep libraries, called [http://lists.gnu.org/archive/html/gnustep-dev/2005-06/msg00050.html Testsuite]. This may not be suitable for more general unit testing of applications as it's been designed to operate with little of the GNUstep environment actually running. ''Tip: use this if you're describing or fixing bugs or features in base, gui etc.''

* [https://gna.org/projects/etoile Étoilé] contains a port to GNUstep of [https://github.com/etoile/UnitKit UnitKit 1.5]. This is a straight-forward unit testing environment, suited to the needs of application developers. It also works under X-code on MacOS X.

* [http://www.sente.ch/ Sen:te] have provided a unit testing environment called [http://www.sente.ch/software/ocunit/ OCUnit] which apparently works under GNUstep, although there are comments in the mailing lists about difficulty getting it working.

* Perhaps [[ObjcUnit]] is also relevant? --[[User:Svetlana|svetlana]] 01:26, 16 January 2017 (CET)

----

See also:
* [[:Category:Frameworks|Official Development Frameworks]]
* [[:Category:Development Frameworks|Development Frameworks]]

Integrated Development Environments for Objective C

2020-04-14T07:38:58Z

Letterus: /* Tools from the GNUstep project */ Added link to page Development tools

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you may want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces. For more information on Gorm and ProjectCenter see [[Development tools]].

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known to Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

=== Xcode ===

You are not able to install Xcode using a Free Software environment. But of course it is possible to use Apple's Xcode to develop apps that are based on Foundation and AppKit. Xcode won't create a proper makefile for you. You will have to do that yourself or let ProjectCenter do the work for you. But if you use Xcode's interface builder (formerly "Interface Builder") to create graphical user interfaces utilizing [[XIB]] files instead of storyboards, GNUstep will be able to load and execute these [[XIB]] files as well.

Introduction to GNUstep

2020-04-14T07:36:40Z

Letterus:

GNUstep is a free, object-oriented, cross-platform development environment that strives for simplicity and elegance. GNUstep is based on and completely compatible with the [[OpenStep]] specification developed by NeXT (now Apple Computer Inc.) as well as implementing many extensions included in Mac OS X/Cocoa.

* [http://www.gnustep.org/information/GNUstep-brochure.pdf Summary brochure] (2Mb PDF)
* [http://www.gnustep.org/information/Booklet.pdf Summary Booklet] (3Mb PDF)
* Our [[Mission]]

== GNUstep is... ==

=== ...an object-oriented tool development kit ===

The first two packages (GNUstep-make and GNUstep-base) that make up the core libraries contain a complete system for writing non-graphic tools in Objective-C. The make package allows you to setup a simple and powerful system for building, installing and packaging your tools. The base package includes all the classes necessary for writing an incredible array of tools, from wrappers for system tools to tools for communicating with web and other types of servers.

=== ...a graphical development kit ===

The core libraries contain classes for developing a complete graphical application for almost any purpose. Along with our object-oriented, graphical development applications, [[ProjectCenter]] and [[Gorm]] it's simple to write very complex commercial applications in weeks or months, rather than years (or often, never) in the case of other development environments.

=== ...a desktop ===

Many GNUstep [[:Category:Applications|applications]] have been written to provide a powerful user experience for working on your computer. These include our workspace manager, [[GWorkspace]], and mail client, [[GNUMail]]. GNUstep does NOT have a window manager. You can use any window manager you want, although we recommend that you use [[WindowMaker]] for a better experience -- the WindowMaker project, however, is not associated with GNUstep. Many other applications that are useful for a desktop are not contained on this web site, nor are they controlled by the GNUstep project - there are too many ideas about what a desktop should look like that we have not made up our minds about which one to endorse yet.

Here are some current ones:

* [http://www.nongnu.org/gap/ GNUstep Application Project]
* [https://trunkmaster.github.io/ Nextspace]

== GNUstep is not a window manager ==

GNUstep is [[GNUstepIsNotWindowMaker|not a window manager]]. And the libraries are not used by WindowMaker at present, although WindowMaker shares a similar look.

At no stage will you ever 'run' GNUstep - you will run applications and tools and will make use of its services. At some point you may well find packages distributed as 'GNUstep' systems in the way that you get 'GNU/Linux' systems packaged today. Look at the [http://io.debian.net/~tar/gnustep/ GNUstep Live CD] for example.

== Additions to OpenStep ==

In addition to the OpenStep API, GNUstep also implements many additional classes and methods, some from the Cocoa API for the sake of compatibility. GNUstep is written in the object-oriented language [[Objective-C]], a superset of C which adds object-orientation to C. Objective-C is very simple, yet very powerful. GNUstep also includes bindings to other languages such as Java (JIGS) and Ruby (RIGS).

For more information, see the following [http://www.gnustep.org/information/statement.html testimonial] from a GNUstep user.

== Why should I learn Objective-C? ==

[[Objective-C]] gives you the full power of a true object-oriented language with exactly one syntax addition to C and a dozen additional keywords. Its power lies in its elegance and simplicity. Don't like [[Objective-C]]? You can use Java (See [http://www.gnustep.it/jigs/index.html JIGS]) or Ruby (See [http://www.gnustep.org/experience/RIGS.html RIGS]).

== Why should I use GNUstep? ==

GNUstep provides an excellent, mature framework for writing good applications. There's good [http://www.stepwise.com/Articles/Business/NextOrderOfBusiness.html anecdotal] [http://www.stepwise.com/Articles/Business/NuclearStrike.html evidence] that [[OpenStep]] developers have written very complex commercial applications in weeks or months, rather than years (or often, never) in the case of other development environments. Using the visual interface modeling application, you can construct a decent user interface skeleton in a day or so with no coding.

== Why not just use GNOME/KDE, X11, and C/C++? ==

GNUstep works with GNOME, KDE (See [[IconManager.app]]), as well as many X11-based window managers. GNUstep runs on top of X11. You can still do programming in C (since Objective-C is a pure superset of C), and GCC version 4.1 and newer even supports the mixing of C++ and Objective-C. GNUstep frees you to develop cross-platform applications without the work of developing an OS independent framework from scratch. It gives you lots of functionality, including Font Panels, Unicode strings, and even Distributed Objects.

== What development tools can I use? ==

See page [[Development tools]] for this.

== License ==

The GNUstep libraries are covered under the [http://www.gnu.org/copyleft/lesser.html GNU Lesser (Library) Public License]. This generally means you can use these libraries in any program (even non-free programs) without affecting the license of your program or any other libraries GNUstep is linked with. If you distribute the GNUstep libraries along with your program, you must make the improvements you have made to the GNUstep libraries freely available. The stand-alone tools in GNUstep are under the standard [http://www.gnu.org/copyleft/gpl.html GPL].

With GNUstep-Base, we recommend the use of the ffcall libraries, which provides stack frame handling for NSInvocation and NSConnection. "Ffcall is under GNU GPL. As a special exception, if used in GNUstep or in derivate works of GNUstep, the included parts of ffcall are under GNU LGPL" (Text in quotes provided by the author of ffcall).

== Design ==

The GNUstep logo has been designed by Ayis Theseas Pyrros. It stands for the "yin-yang" of objects taking you "a couple of steps" further.

Introduction to GNUstep

2020-04-14T07:36:13Z

Letterus: Add link to development tools.

Introduction to GNUstep

2020-04-14T07:33:46Z

Letterus: /* ...a desktop */ Updated current desktop approaches

GNUstep is a free, object-oriented, cross-platform development environment that strives for simplicity and elegance. GNUstep is based on and completely compatible with the [[OpenStep]] specification developed by NeXT (now Apple Computer Inc.) as well as implementing many extensions included in Mac OS X/Cocoa.

* [http://www.gnustep.org/information/GNUstep-brochure.pdf Summary brochure] (2Mb PDF)
* [http://www.gnustep.org/information/Booklet.pdf Summary Booklet] (3Mb PDF)
* Our [[Mission]]

== GNUstep is... ==

=== ...an object-oriented tool development kit ===

The first two packages (GNUstep-make and GNUstep-base) that make up the core libraries contain a complete system for writing non-graphic tools in Objective-C. The make package allows you to setup a simple and powerful system for building, installing and packaging your tools. The base package includes all the classes necessary for writing an incredible array of tools, from wrappers for system tools to tools for communicating with web and other types of servers.

=== ...a graphical development kit ===

The core libraries contain classes for developing a complete graphical application for almost any purpose. Along with our object-oriented, graphical development applications, [[ProjectCenter]] and [[Gorm]] it's simple to write very complex commercial applications in weeks or months, rather than years (or often, never) in the case of other development environments.

=== ...a desktop ===

Many GNUstep [[:Category:Applications|applications]] have been written to provide a powerful user experience for working on your computer. These include our workspace manager, [[GWorkspace]], and mail client, [[GNUMail]]. GNUstep does NOT have a window manager. You can use any window manager you want, although we recommend that you use [[WindowMaker]] for a better experience -- the WindowMaker project, however, is not associated with GNUstep. Many other applications that are useful for a desktop are not contained on this web site, nor are they controlled by the GNUstep project - there are too many ideas about what a desktop should look like that we have not made up our minds about which one to endorse yet.

Here are some current ones:

* [http://www.nongnu.org/gap/ GNUstep Application Project]
* [https://trunkmaster.github.io/ Nextspace]

== GNUstep is not a window manager ==

GNUstep is [[GNUstepIsNotWindowMaker|not a window manager]]. And the libraries are not used by WindowMaker at present, although WindowMaker shares a similar look.

At no stage will you ever 'run' GNUstep - you will run applications and tools and will make use of its services. At some point you may well find packages distributed as 'GNUstep' systems in the way that you get 'GNU/Linux' systems packaged today. Look at the [http://io.debian.net/~tar/gnustep/ GNUstep Live CD] for example.

== Additions to OpenStep ==

In addition to the OpenStep API, GNUstep also implements many additional classes and methods, some from the Cocoa API for the sake of compatibility. GNUstep is written in the object-oriented language [[Objective-C]], a superset of C which adds object-orientation to C. Objective-C is very simple, yet very powerful. GNUstep also includes bindings to other languages such as Java (JIGS) and Ruby (RIGS).

For more information, see the following [http://www.gnustep.org/information/statement.html testimonial] from a GNUstep user.

== Why should I learn Objective-C? ==

[[Objective-C]] gives you the full power of a true object-oriented language with exactly one syntax addition to C and a dozen additional keywords. Its power lies in its elegance and simplicity. Don't like [[Objective-C]]? You can use Java (See [http://www.gnustep.it/jigs/index.html JIGS]) or Ruby (See [http://www.gnustep.org/experience/RIGS.html RIGS]).

== Why should I use GNUstep? ==

GNUstep provides an excellent, mature framework for writing good applications. There's good [http://www.stepwise.com/Articles/Business/NextOrderOfBusiness.html anecdotal] [http://www.stepwise.com/Articles/Business/NuclearStrike.html evidence] that [[OpenStep]] developers have written very complex commercial applications in weeks or months, rather than years (or often, never) in the case of other development environments. Using the visual interface modeling application, you can construct a decent user interface skeleton in a day or so with no coding.

== Why not just use GNOME/KDE, X11, and C/C++? ==

GNUstep works with GNOME, KDE (See [[IconManager.app]]), as well as many X11-based window managers. GNUstep runs on top of X11. You can still do programming in C (since Objective-C is a pure superset of C), and GCC version 4.1 and newer even supports the mixing of C++ and Objective-C. GNUstep frees you to develop cross-platform applications without the work of developing an OS independent framework from scratch. It gives you lots of functionality, including Font Panels, Unicode strings, and even Distributed Objects.

== License ==

The GNUstep libraries are covered under the [http://www.gnu.org/copyleft/lesser.html GNU Lesser (Library) Public License]. This generally means you can use these libraries in any program (even non-free programs) without affecting the license of your program or any other libraries GNUstep is linked with. If you distribute the GNUstep libraries along with your program, you must make the improvements you have made to the GNUstep libraries freely available. The stand-alone tools in GNUstep are under the standard [http://www.gnu.org/copyleft/gpl.html GPL].

With GNUstep-Base, we recommend the use of the ffcall libraries, which provides stack frame handling for NSInvocation and NSConnection. "Ffcall is under GNU GPL. As a special exception, if used in GNUstep or in derivate works of GNUstep, the included parts of ffcall are under GNU LGPL" (Text in quotes provided by the author of ffcall).

== Design ==

The GNUstep logo has been designed by Ayis Theseas Pyrros. It stands for the "yin-yang" of objects taking you "a couple of steps" further.

Integrated Development Environments for Objective C

2020-04-13T19:18:26Z

Letterus: /* JetBrains CLion */

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you may want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known to Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

=== Xcode ===

You are not able to install Xcode using a Free Software environment. But of course it is possible to use Apple's Xcode to develop apps that are based on Foundation and AppKit. Xcode won't create a proper makefile for you. You will have to do that yourself or let ProjectCenter do the work for you. But if you use Xcode's interface builder (formerly "Interface Builder") to create graphical user interfaces utilizing [[XIB]] files instead of storyboards, GNUstep will be able to load and execute these [[XIB]] files as well.

XIB

2020-04-13T18:41:47Z

Letterus: /* gnustep-gui/AppKit compatibility to Cocoa/AppKit regarding xib files */

As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions. As of 10.9 (Xcode 5) Apple changed the xib file format totally. Support of "XIB 5" files and above by Gorm is currently prepared.

== Xib file format ==

The xib file format is actually quite easy to understand as it is a human readable xml file. For a reference see [http://www.monobjc.net/xib-file-format.html XIB File Format Definition as understod by MonoObjc].

== Gorm compatibility to Xcode ==

As of version 1.2.24 Gorm is able to read xib and nib files from Xcode up to file version of Xcode 4 (to some extend). Gorm can save nib files, but these nib files currently cannot be read by Xcode 3 and above. This means for development of xibs/nibs you want to open using Gorm you need to use Xcode up to version 5 (Xcode 5 can save xibs in file version of Xcode 4). So you can use a Mac OS X version up to 10.10. macOS 10.11 and newer won't run Xcode 5 anymore.

Gorm did not yet follow up the changes of gnustep-gui described below.

== gnustep-gui/AppKit compatibility to Cocoa/AppKit regarding xib files ==

As of release [https://github.com/gnustep/libs-gui/releases/tag/gui-0_28_0 0.28.0] gnustep-gui is able to interpret xib files created by a recent version of Xcode (Xcode 11 at the time writing this). Even [https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.html Cocoa bindings] (using KVC/KVO) will work to some extend.

=== See Also ===
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueCoding/Articles/Overview.html Apple on KVC]
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueObserving/KeyValueObserving.html#//apple_ref/doc/uid/10000177i Apple on KVO]

== Using .nib and .gorm files in parallel ==

You can use .nib and .gorm files in parallel to develop cross platform applications. GNUstep will load a .gorm file over a .nib file given the same name.

XIB

2020-04-13T18:41:03Z

Letterus: /* gnustep-gui/AppKit compatibility to Cocoa/AppKit regarding xib files */ Update due to changes now released

As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions. As of 10.9 (Xcode 5) Apple changed the xib file format totally. Support of "XIB 5" files and above by Gorm is currently prepared.

== Xib file format ==

The xib file format is actually quite easy to understand as it is a human readable xml file. For a reference see [http://www.monobjc.net/xib-file-format.html XIB File Format Definition as understod by MonoObjc].

== Gorm compatibility to Xcode ==

As of version 1.2.24 Gorm is able to read xib and nib files from Xcode up to file version of Xcode 4 (to some extend). Gorm can save nib files, but these nib files currently cannot be read by Xcode 3 and above. This means for development of xibs/nibs you want to open using Gorm you need to use Xcode up to version 5 (Xcode 5 can save xibs in file version of Xcode 4). So you can use a Mac OS X version up to 10.10. macOS 10.11 and newer won't run Xcode 5 anymore.

Gorm did not yet follow up the changes of gnustep-gui described below.

== gnustep-gui/AppKit compatibility to Cocoa/AppKit regarding xib files ==

As of release [https://github.com/gnustep/libs-gui/releases/tag/gui-0_28_0 0.28.0] gnustep-gui is able to interpret xib files created by a concurrent version of Xcode (Xcode 11 at the time writing this). Even [https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.html Cocoa bindings] (using KVC/KVO) will work to some extend.

=== See Also ===
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueCoding/Articles/Overview.html Apple on KVC]
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueObserving/KeyValueObserving.html#//apple_ref/doc/uid/10000177i Apple on KVO]

== Using .nib and .gorm files in parallel ==

You can use .nib and .gorm files in parallel to develop cross platform applications. GNUstep will load a .gorm file over a .nib file given the same name.

Integrated Development Environments for Objective C

2020-04-13T18:38:29Z

Letterus: /* Proprietary */ Added information about Xcode

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you may want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

=== Xcode ===

You are not able to install Xcode using a Free Software environment. But of course it is possible to use Apple's Xcode to develop apps that are based on Foundation and AppKit. Xcode won't create a proper makefile for you. You will have to do that yourself or let ProjectCenter do the work for you. But if you use Xcode's interface builder (formerly "Interface Builder") to create graphical user interfaces utilizing [[XIB]] files instead of storyboards, GNUstep will be able to load and execute these [[XIB]] files as well.

Integrated Development Environments for Objective C

2020-04-13T18:32:37Z

Letterus: /* Tools from the GNUstep project */

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you may want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

Integrated Development Environments for Objective C

2020-04-13T18:30:04Z

Letterus: /* Tools from the GNUstep project */ Added link to ProjectCenter FAQ

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed. For its up- and downsides you may consult the [[ProjectCenter FAQ]].

Independent of the IDE you want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

Integrated Development Environments for Objective C

2020-04-13T18:26:09Z

Letterus: /* KDevelop */

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed.

Independent of the IDE you want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that might offer some features more, run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are built upon GNUmakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

Integrated Development Environments for Objective C

2020-04-13T18:25:39Z

Letterus: /* Tools from the GNUstep project */

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed.

Independent of the IDE you want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that might offer some features more, run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime ([[ObjC2_FAQ]] | [[Building GNUstep under Debian FreeBSD]]).

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are build upon GNUMakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

Developer Guides

2020-04-13T18:18:00Z

Letterus: /* General */ Added the new article about Objective C IDEs

This page is intended as a collection of guides for developers.

== Introductory Articles on GNUstep Development ==

{{Stub}}

=== [[Installation]] ===
How to get started using GNUStep, because it is not immediately obvious, and we appologize for that.

=== [[GNUstep Suite|GNUstep Libraries and Tools]] ===

A general overview of GNUstep.

=== [http://www.gnustep.org/resources/documentation/Developer/Base/ProgrammingManual/manual_toc.html GNUstep Base Programming Manual] ===

The aim of this manual is to introduce you to the Objective-C language and the GNUstep development environment, in particular the Base library. The manual is organised to give you a tutorial introduction to the language and APIs, by using examples whenever possible, rather than providing a lengthy abstract description.

While Objective-C is not a difficult language to learn or use, some of the terms may be unfamiliar, especially to those that have not programmed using an object-oriented programming language before. Whenever possible, concepts will be explained in simple terms rather than in more advanced programming terms, and comparisons to other languages will be used to aid in illustration.

===[[GNUStep Macros]]===
See a define, but don't know what it's for, you are not alone. See this article for a reference to various macros, or otherwise unusual language extensions that you may see when reading the GNUStep Code.

=== [http://www.roard.com/docs/lmf2.article/en.html (GUI) Programming under GNUstep] ===

This tutorial will introduce you to the [[AppKit]] classes and how to use [[Gorm]] to create graphical interfaces.

=== [[Writing Makefiles]] ===

The Makefile package is a system of make commands that is designed to encapsulate all the complex details of building and installing various types of projects from libraries to applications to documentation. This frees the developer to focus on the details of their particular project. Only a fairly simple main makefile need to be written which specifies the type of project and files involved in the project.

=== Sample GNUstep Programs ===

This isn't really an article but rather a collection of small "codified guides" for the pragmatic programmer who wants to explore GNUstep by looking at and messing around with example code. This is best done while reading about basic concepts of OpenStep or Cocoa with the API documentation ([[Foundation]], [[AppKit]]) open in the background. Get the gnustep-examples package from [ftp://ftp.gnustep.org/pub/gnustep/core/ here]

== General ==

=== [[Writing portable code|Coding for Portability]] ===

Writing code that will compile and then run on different platforms can be surprisingly easy. This guide describes
some straight-forward steps to take to make your program easy to port to new platforms.

=== [[Property Lists|Using Property Lists]] ===

A regular issue that programmers face is storing structured configuration information, and reading it back. GNUstep has a standard mechanism that can be used for this task, amongst others: Property Lists.

=== [[Deployment on Windows]] ===

This article will tell you how to deploy GNUstep applications on Windows.

=== [[Adding a new Natural Language to GNUstep|Translating GNUstep]] ===

Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.

=== [[Contributing to GNUstep core libraries]] ===

Contributing to the core libraries is what everyone loves you for the most ... but it's quite a step to go from simple bug fixes/patches to major new code contributions. Follow the link above to see how.

When you read the information on [[Contributing to GNUstep core libraries]], please keep in mind that while it was written primarily form the point of view of contributing code to the gnustep-base library, the principles all apply to the gnustep-gui library (and other library code too). Also, a lot of the information is also relevant to contributions to application/tool code, not just library code.

=== [[Integrated Development Environments for Objective C]] ===

Besides the official GNUstep project tools there are some more IDEs that can help you to get into developing GNUstep and Objective C very easily.

== Graphical Applications ==

=== Simple Graphical Application Design ===
GNUstep includes two development tools. GNUstep GUI interfaces are designed using [[Gorm]] (Graphical Object Relationship Modeler), an elegant application developed by Gregory Casamento. (See his [http://heronsperch.blogspot.com/ blog] for the latest news on GORM.) There is a proto-IDE, [[ProjectCenter]].

There are several introductory tutorials for using these development tools. The first [http://www.gnustep.it/pierre-yves/index.html tutorial] by Pierre-Yves Rivaille is a classic demonstrating the process used to create the ubiquitous currency converter application. A second [http://www.nongnu.org/gstutorial/ tutorial] by Yen-Ju Chen is somewhat more in-depth and extensive.

=== [[Document based applications|Document-based Application Design]] ===

One of the most common use-patterns of applications on modern platforms is that of document-based applications --- applications which can have several active user-controlled contexts. Some familar examples might be a word processor where the user may have multiple document windows concurrently, or a web browser which allows a user to have a number of different browser windows open at the same time. This guide provides information and tips on how to code this style of application.

== Web Applications ==

Please have a look at [[Creating A Simple GSWeb Application]] to learn how to create a [[GNUstepWeb|GNUstep Web]] application.

== Other Information ==

=== Developer sites ===

* [http://www.roard.com/docs/ GNUstep HelpCenter]

[[Category:Development]]

Developer Guides

2020-04-13T18:15:22Z

Letterus: /* Simple Graphical Application Design */ Updated the paragraph to make it reflect the current status more precisely

This page is intended as a collection of guides for developers.

== Introductory Articles on GNUstep Development ==

{{Stub}}

=== [[Installation]] ===
How to get started using GNUStep, because it is not immediately obvious, and we appologize for that.

=== [[GNUstep Suite|GNUstep Libraries and Tools]] ===

A general overview of GNUstep.

=== [http://www.gnustep.org/resources/documentation/Developer/Base/ProgrammingManual/manual_toc.html GNUstep Base Programming Manual] ===

The aim of this manual is to introduce you to the Objective-C language and the GNUstep development environment, in particular the Base library. The manual is organised to give you a tutorial introduction to the language and APIs, by using examples whenever possible, rather than providing a lengthy abstract description.

While Objective-C is not a difficult language to learn or use, some of the terms may be unfamiliar, especially to those that have not programmed using an object-oriented programming language before. Whenever possible, concepts will be explained in simple terms rather than in more advanced programming terms, and comparisons to other languages will be used to aid in illustration.

===[[GNUStep Macros]]===
See a define, but don't know what it's for, you are not alone. See this article for a reference to various macros, or otherwise unusual language extensions that you may see when reading the GNUStep Code.

=== [http://www.roard.com/docs/lmf2.article/en.html (GUI) Programming under GNUstep] ===

This tutorial will introduce you to the [[AppKit]] classes and how to use [[Gorm]] to create graphical interfaces.

=== [[Writing Makefiles]] ===

The Makefile package is a system of make commands that is designed to encapsulate all the complex details of building and installing various types of projects from libraries to applications to documentation. This frees the developer to focus on the details of their particular project. Only a fairly simple main makefile need to be written which specifies the type of project and files involved in the project.

=== Sample GNUstep Programs ===

This isn't really an article but rather a collection of small "codified guides" for the pragmatic programmer who wants to explore GNUstep by looking at and messing around with example code. This is best done while reading about basic concepts of OpenStep or Cocoa with the API documentation ([[Foundation]], [[AppKit]]) open in the background. Get the gnustep-examples package from [ftp://ftp.gnustep.org/pub/gnustep/core/ here]

== General ==

=== [[Writing portable code|Coding for Portability]] ===

Writing code that will compile and then run on different platforms can be surprisingly easy. This guide describes
some straight-forward steps to take to make your program easy to port to new platforms.

=== [[Property Lists|Using Property Lists]] ===

A regular issue that programmers face is storing structured configuration information, and reading it back. GNUstep has a standard mechanism that can be used for this task, amongst others: Property Lists.

=== [[Deployment on Windows]] ===

This article will tell you how to deploy GNUstep applications on Windows.

=== [[Adding a new Natural Language to GNUstep|Translating GNUstep]] ===

Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.

=== [[Contributing to GNUstep core libraries]] ===

Contributing to the core libraries is what everyone loves you for the most ... but it's quite a step to go from simple bug fixes/patches to major new code contributions. Follow the link above to see how.

When you read the information on [[Contributing to GNUstep core libraries]], please keep in mind that while it was written primarily form the point of view of contributing code to the gnustep-base library, the principles all apply to the gnustep-gui library (and other library code too). Also, a lot of the information is also relevant to contributions to application/tool code, not just library code.

== Graphical Applications ==

=== Simple Graphical Application Design ===
GNUstep includes two development tools. GNUstep GUI interfaces are designed using [[Gorm]] (Graphical Object Relationship Modeler), an elegant application developed by Gregory Casamento. (See his [http://heronsperch.blogspot.com/ blog] for the latest news on GORM.) There is a proto-IDE, [[ProjectCenter]].

There are several introductory tutorials for using these development tools. The first [http://www.gnustep.it/pierre-yves/index.html tutorial] by Pierre-Yves Rivaille is a classic demonstrating the process used to create the ubiquitous currency converter application. A second [http://www.nongnu.org/gstutorial/ tutorial] by Yen-Ju Chen is somewhat more in-depth and extensive.

=== [[Document based applications|Document-based Application Design]] ===

One of the most common use-patterns of applications on modern platforms is that of document-based applications --- applications which can have several active user-controlled contexts. Some familar examples might be a word processor where the user may have multiple document windows concurrently, or a web browser which allows a user to have a number of different browser windows open at the same time. This guide provides information and tips on how to code this style of application.

== Web Applications ==

Please have a look at [[Creating A Simple GSWeb Application]] to learn how to create a [[GNUstepWeb|GNUstep Web]] application.

== Other Information ==

=== Developer sites ===

* [http://www.roard.com/docs/ GNUstep HelpCenter]

[[Category:Development]]

Integrated Development Environments for Objective C

2020-04-13T18:12:44Z

Letterus:

== Tools from the GNUstep project ==

There is an official IDE from the GNUstep project, which is [[ProjectCenter]]. It is actively maintained and developed.

Independent of the IDE you want to use you probably want to rely on [[Gorm]] or [[Renaissance]] for developing graphical user interfaces.

Besides ProjectCenter there are some more IDEs, that might offer some features more, run under Free Software environments and offer support for developing with Objective C.

The IDEs below usually rely on clang. So you benefit most from using them if you develop your applications using clang and the new (ng) GNUstep runtime.

== Free Software or Open Source ==

=== KDevelop ===

[https://www.kdevelop.org/ KDevelop] is the official IDE from the KDE project based on Qt and the KDE libraries. Besides many other languages it supports Objective C. It supports projects that are build upon GNUMakefiles and thus should support GNUstep projects quite well. It is GPL 2 licensed and easily available via the package managers of most distributions and operating systems.

=== Visual Studio Code ===

[https://code.visualstudio.com/ Visual Studio Code] is a relatively small electron (JavaScript) app, shipped as Open Source Software from Microsoft. Besides many other languages it supports Objective C very well. It is MIT licensed and you are expected to obtain it from Microsoft.

== Proprietary ==

=== JetBrains CLion ===

[https://www.jetbrains.com/clion/ JetBrains CLion] is a proprietary, full featured IDE for C and C++ (the framework is well known for Java developers), but also [https://www.jetbrains.com/help/clion/objective-c-c-support.html supporting Objective C].

Developer Guides

2020-04-13T17:42:26Z

Letterus: /* Simple Graphical Application Design */ Deleted dead links to tutorial videos.

This page is intended as a collection of guides for developers.

== Introductory Articles on GNUstep Development ==

{{Stub}}

=== [[Installation]] ===
How to get started using GNUStep, because it is not immediately obvious, and we appologize for that.

=== [[GNUstep Suite|GNUstep Libraries and Tools]] ===

A general overview of GNUstep.

=== [http://www.gnustep.org/resources/documentation/Developer/Base/ProgrammingManual/manual_toc.html GNUstep Base Programming Manual] ===

The aim of this manual is to introduce you to the Objective-C language and the GNUstep development environment, in particular the Base library. The manual is organised to give you a tutorial introduction to the language and APIs, by using examples whenever possible, rather than providing a lengthy abstract description.

While Objective-C is not a difficult language to learn or use, some of the terms may be unfamiliar, especially to those that have not programmed using an object-oriented programming language before. Whenever possible, concepts will be explained in simple terms rather than in more advanced programming terms, and comparisons to other languages will be used to aid in illustration.

===[[GNUStep Macros]]===
See a define, but don't know what it's for, you are not alone. See this article for a reference to various macros, or otherwise unusual language extensions that you may see when reading the GNUStep Code.

=== [http://www.roard.com/docs/lmf2.article/en.html (GUI) Programming under GNUstep] ===

This tutorial will introduce you to the [[AppKit]] classes and how to use [[Gorm]] to create graphical interfaces.

=== [[Writing Makefiles]] ===

The Makefile package is a system of make commands that is designed to encapsulate all the complex details of building and installing various types of projects from libraries to applications to documentation. This frees the developer to focus on the details of their particular project. Only a fairly simple main makefile need to be written which specifies the type of project and files involved in the project.

=== Sample GNUstep Programs ===

This isn't really an article but rather a collection of small "codified guides" for the pragmatic programmer who wants to explore GNUstep by looking at and messing around with example code. This is best done while reading about basic concepts of OpenStep or Cocoa with the API documentation ([[Foundation]], [[AppKit]]) open in the background. Get the gnustep-examples package from [ftp://ftp.gnustep.org/pub/gnustep/core/ here]

== General ==

=== [[Writing portable code|Coding for Portability]] ===

Writing code that will compile and then run on different platforms can be surprisingly easy. This guide describes
some straight-forward steps to take to make your program easy to port to new platforms.

=== [[Property Lists|Using Property Lists]] ===

A regular issue that programmers face is storing structured configuration information, and reading it back. GNUstep has a standard mechanism that can be used for this task, amongst others: Property Lists.

=== [[Deployment on Windows]] ===

This article will tell you how to deploy GNUstep applications on Windows.

=== [[Adding a new Natural Language to GNUstep|Translating GNUstep]] ===

Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.

=== [[Contributing to GNUstep core libraries]] ===

Contributing to the core libraries is what everyone loves you for the most ... but it's quite a step to go from simple bug fixes/patches to major new code contributions. Follow the link above to see how.

When you read the information on [[Contributing to GNUstep core libraries]], please keep in mind that while it was written primarily form the point of view of contributing code to the gnustep-base library, the principles all apply to the gnustep-gui library (and other library code too). Also, a lot of the information is also relevant to contributions to application/tool code, not just library code.

== Graphical Applications ==

=== Simple Graphical Application Design ===
GNUstep includes several sophisticated development tools. GNUstep GUI interfaces are designed using [[Gorm]] (Graphical Object Relationship Modeler), an elegant application developed by Gregory Casamento. (See his [http://heronsperch.blogspot.com/ blog] for the latest news on GORM.) There are two proto-IDEs, [[ProjectCenter]] and [[ProjectManager]].

There are several introductory tutorials for using these development tools. The first [http://www.gnustep.it/pierre-yves/index.html tutorial] by Pierre-Yves Rivaille is a classic demonstrating the process used to create the ubiquitous currency converter application. A second [http://www.nongnu.org/gstutorial/ tutorial] by Yen-Ju Chen is somewhat more in-depth and extensive.

=== [[Document based applications|Document-based Application Design]] ===

One of the most common use-patterns of applications on modern platforms is that of document-based applications --- applications which can have several active user-controlled contexts. Some familar examples might be a word processor where the user may have multiple document windows concurrently, or a web browser which allows a user to have a number of different browser windows open at the same time. This guide provides information and tips on how to code this style of application.

== Web Applications ==

Please have a look at [[Creating A Simple GSWeb Application]] to learn how to create a [[GNUstepWeb|GNUstep Web]] application.

== Other Information ==

=== Developer sites ===

* [http://www.roard.com/docs/ GNUstep HelpCenter]

[[Category:Development]]

User Guides

2020-04-13T17:36:59Z

Letterus: /* Other Info */ Added Nextspace

This page is intended as a collection of guides for users.

== Installing GNUstep ==

Installation can be easy or complex, depending on the system you use. If you encounter problems that aren't discussed here, please [[Get Help|ask for help on the mailing lists]].

* [[Installation | Installation introduction]]
* Instructions on how to install on [[Platform:BSD|BSD]] or [[Platform:Linux|Linux]]. There are other [[Platform_compatibility|platform-specific]] instructions as well.
* Comprehensive [http://gnustep.made-it.com/BuildGuide/ build guide] for GNUstep on GNU/Linux.

== Configuration ==

* [http://www.gnustep.org/resources/documentation/User/Gui/KeyboardSetup.html User Keyboard Setup]
* [http://www.gnustep.org/resources/documentation/User/Gui/LanguageSetup.html Setup for East Asian Languages]
* User Defaults ([http://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html GUI]) ([http://www.gnustep.org/resources/documentation/Developer/Back/General/DefaultsSummary.html Back])

== Advanced installation ==

* [[GNUstep SVN Installation Guide]]
* [http://svn.gna.org/svn/etoile/trunk/Etoile/INSTALL.Ubuntu GNUstep and Étoilé dependency list]
* [[Building GNUstep with Clang]]
* [[Building GNUstep under Debian FreeBSD|Building GNUstep under Debian and FreeBSD using runtime 2.0 with clang and support for blocks, Grand Central Dispatch and ARC]]
* [http://artinamessage.wordpress.com/2013/06/03/gnustep-install-with-clang-blocks-and-grand-central-dispatch-gcd/ Building GNUstep with clang, blocks, and Grand Central Dispatch]
* [[Raspbian Install| Raspbian Install]]

== Using GNUstep ==

* [[:Category:Applications|User Applications]]
* [http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem_toc.html Filesystem Layout] ([http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem.pdf PDF])
* [[User_FAQ|GNUstep Users' FAQ]] ([http://www.gnustep.org/resources/documentation/User/GNUstep/userfaq.pdf PDF])
* [[Get Help|Mailing Lists, IRC and Newsgroups]]
* [[Cross Compiling]]
* [http://gnustep.files.wordpress.com/2010/11/objective-c_gnustep.pdf Manual de Objective-C y GNUstep (PDF en español)]
* [[Themes|Changing GNUstep Theme]]

== Other Info ==

* News and info:
** [http://freecode.com/tags/objective-c Freshmeat] ->Freecode Effective 2014-06-18 Freecode is no longer being updated (content may be stale).
** [http://www.gnustep.wordpress.com/ GNUstep en español] - Noticias e información
* Projects:
** [[:Category:Desktop Environments|Desktop Environments]]
*** [http://www.nongnu.org/backbone/ Backbone] - GNUstep Desktop project
*** [http://www.etoile-project.org/ Étoilé] - GNUstep based user environment
*** [http://www.nongnu.org/gap/ GAP] - GNUstep Application Project
*** [https://trunkmaster.github.io/ Nextspace] - GNUstep based Desktop project
** Live CDs
*** [http://livecd.gnustep.org/ GNUSTEP Live CD] - based on Debian
*** ALT Linux based (i586/x86_64, BIOS/UEFI, considerable number of GNUstep/Étoilé apps):
**** [http://en.altlinux.org/Starterkits/gnustep GNUstep starterkit] - updated quarterly (as of June 2014) using stable package branch
**** [http://en.altlinux.org/Regular#experimental Regular GNUstep] - updated [http://nightly.altlinux.org/sisyphus/flavours/gnustep/ weekly] using unstable development branch
* Developer sites:
** [[For_Developers | Developers]] - List of developers
** [http://www.gnustep.it/ GNUstep.it] - Italian developer site
** [http://www.collaboration-world.com/ Collaboration World] - home to GNUMail, Affiche and more
** [http://www.roard.com/docs/ GNUstep HelpCenter]
** [http://www.aiei.ch/gnustep/icons/icons.html GNUstep Icons project]
* [[Success_Stories | GNUstep Success Stories]]

== Stores ==

Building GNUstep under Debian FreeBSD

2020-02-20T07:45:11Z

Letterus: /* libiconv */

Here's a tutorial on how to to build gnustep and its dependencies if you want to run it using GNUstep runtime 2.0 (ng), which has to be built using clang 8.0.

You'll find these steps bundled in a script which you can execute under Debian 9 at https://github.com/plaurent/gnustep-build/tree/master/debian-9-clang-8.0-runtime-2.0.

== Install empty VM ==

We start with an empty Debian9 or FreeBSD 12 VM.

== Dependencies under Debian 9 ==

we install these packages under Debian as they are coming up as dependencies anyhow

apt-get install dirmngr
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com \
15CF4D18AF4F7421
sudo apt -y install build-essential git subversion \
libpthread-workqueue0 libpthread-workqueue-dev \
libxml2 libxml2-dev \
libffi6 libffi-dev \
libicu-dev \
libuuid1 uuid-dev uuid-runtime \
libsctp1 libsctp-dev lksctp-tools \
libavahi-core7 libavahi-core-dev \
libavahi-client3 libavahi-client-dev \
libavahi-common3 libavahi-common-dev libavahi-common-data \
libgcrypt20 libgcrypt20-dev \
libtiff5 libtiff5-dev \
libbsd0 libbsd-dev \
util-linux-locales \
locales-all \
libjpeg-dev \
libtiff-dev \
libcups2-dev \
libfreetype6-dev \
libcairo2-dev \
libxt-dev \
libgl1-mesa-dev \
libpcap-dev \
libc-dev libc++-dev libc++1 \
python-dev swig \
libedit-dev libeditline0 libeditline-dev readline-common \
binfmt-support libtinfo-dev \
bison flex m4 wget \
libicns1 libicns-dev \
libxslt1.1 libxslt1-dev \
libxft2 libxft-dev \
libflite1 flite1-dev \
libxmu6 libxpm4 wmaker-common \
libgnutls30 libgnutls28-dev \
libpng-dev libpng16-16 \
default-libmysqlclient-dev \
libpq-dev \
libstdc++-6-dev \
libreadline7 libreadline-dev \gobjc-6 gobjc++-6 \
libgif7 libgif-dev libwings3 libwings-dev libwraster5 \
libwraster-dev libwutil5 \
libcups2-dev libicu57 libicu-dev \
gobjc++ \
xorg \
libfreetype6 libfreetype6-dev \
libpango1.0-dev \
libcairo2-dev \
libxt-dev libssl-dev \
libasound2-dev libjack-dev libjack0 libportaudio2 \
libportaudiocpp0 portaudio19-dev \
libstdc++-6-dev libstdc++-6-doc libstdc++-6-pic \
libstdc++6 wmaker cmake cmake-curses-gui xpdf

== Dependencies under FeeBSD 12 ==

pkg install git \
autoconf \
automake \
cmake \
subversion \
wget \
bash \
pkgconf \
sudo \
gmake \
windowmaker \
jpeg \
tiff \
png \
libxml2 \
libxslt \
gnutls \
libffi \
icu \
cairo \
avahi \
portaudio \
flite \
pngwriter \
mariadb103-client \
postgresql96-client \
bash \
clang \
lldb

== We install a decent clang compiler. ==

clang-8: from clang8 repository: Add a file /etc/apt/sources.d/llvm.list with content

deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main

To install you call it like this:

apt-get update
apt-get install clang-8 lldb-8 lld-8

Note: clang-7 has a bug which makes gnustep-base fail during its ./configure phase.

(Note today clang-8 was no longer in the llvm repo for some reason. Maybe temporary issue. I also tried the bleeding edge clang-9 and that worked similarly)

Under FreeBSD we use the clang compiler which comes with FreeBSD12.
If you use CentOS 7 or the like, you probably have to compile the clang compiler from source. this is time consuming and can be done like tis:

git clone https://git.llvm.org/git/llvm.git/
cd llvm/tools
git clone https://git.llvm.org/git/clang.git/
cd ../projects
git clone https://git.llvm.org/git/compiler-rt.git/
cd ..
mkdir BUILD
cd BUILD
cmake .. -DCMAKE_BUILD_TYPE=Release make -j8
make install

(note this installs your compiler in /usr/local/bin so you have to change the path on the later stages below)

== Download GNUSTEP ==

We download the sources we need:

mkdir gnustep
cd gnustep
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.15.tar.gz
git clone https://github.com/apple/swift-corelibs-libdispatch
git clone https://github.com/gnustep/scripts
git clone https://github.com/gnustep/make
git clone https://github.com/gnustep/libobjc2
git clone https://github.com/gnustep/base
git clone https://github.com/gnustep/corebase
git clone https://github.com/gnustep/gui
git clone https://github.com/gnustep/back
./scripts/install-dependencies

The last step should basically not show any additional dependency we have not already covered. On FreeBSD , the last step has to be skipped as the script is not prepared for FreeBSD yet.

== libiconv ==

This applies for Debian 9 (or maybe older). From Debian 10 upwards you won't need to install libiconv. You do not have to do this when installing for Ubuntu.

For Debian 9 (and older?): We compile libiconv. Debian comes standard with version 1.14 but there was an issue in 1.14 which got fixed in 1.15 which was relevant to us so using 1.15 is recommended.

tar -xvzf libiconv-1.15.tar.gz
cd libiconv-1.15
./configure --enable-static --enable-dynamic
make
make install
cd ..

== Defaults ==

We set some environment defaults for the remainder of the session

# we set the C and C++ compiler version
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export RUNTIME_VERSION=gnustep-2.0
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD=/usr/bin/ld.gold
export LDFLAGS=-fuse-ld=/usr/bin/ld.gold
export OBJCFLAGS="-fblocks"

Using the ld.gold linker is important as otherwise strange things happens. old ld does stuff wrong, newer lld from clang optimises stuff away it shouldn't.

== libdispatch ==

The libdispatch is an open source library supplied by Apple which takes care of running multiple background tasks. Apple calls it "Grand Central Dispatch". The Swift language also uses it, hence the repo name. We're not really directly using it but other objc code might use it or benefit from it so we compile it as well.

cd swift-corelibs-libdispatch
mkdir build
cd build
cmake .. -DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_BUILD_TYPE=Release \
-DUSE_GOLD_LINKER=YES
make -j40
make install
ldconfig

== libobjc2 / gnustep-base ==

Now we have reached a point where the magic triple libobjc2 + gnustep-make + gnustep-base comes into play. To understand the context here. The objectiveC compiler needs a runtime. The runtime is taking care of the basic functionality of objectiveC objects such as their memory allocation and release and other stuff. The compiler calls the runtime when specific stuff happens. When a method is called, the compiler puts a call into the runtime which then looks up the dynamic methods and calls the method etc. When a block ends and certain objects are no longer needed, the compiler calls the runtime so it can release the objects accordingly.

There are different runtimes around. The original objectiveC runtime supplied by the gcc compiler. It's old, outdated and doesn't deal with automatic reference counting and a lot of other things. So it's not recommended. The libobjc2 is the "modern" rewrite for a runtime and is actually based on a project called Etoile. It's ABI has different variants. There is a fragile and a non fragile ABI.

Read this blogpost to understand what the difference is: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_explain_Non-fragile_ivars.html
If you get this is wrong, you might end up with objects no longer using the right position of variables in the data of super or subclasses and things can get totally out of control. So the new non-fragile-ABI is really the way to go. There are also different versions of the ABI on how the compiler calls the runtime. So the compiler and the runtime are working together as a team.

So once we have a runtime library which is a requirement for any objectiveC code, there is also the base library gnustep-base which corresponds to Apple's Foundation framework. This one implements basic functionality which is used in almost all ObjC code.. It brings stuff like dealing with strings, arrays, dictionaries, and lots of other things you need day in day out. It does not supply any GUI code. All NextStep/Apple ObjectiveC code is derived from a base class called NSObject which is defined in gnustep-base. GnuStep is an open source reimplementation of NextStep and the Apple Foundation/AppKit classes.

There are 3 other libraries in GnuStep which are gnustep-gui which does all the graphical interface, gnustep-back which is the backend for the GUI (so there's a variant for X-windows, one for Windows, one for MacOS aqua etc) which is like a driver for the gui to do the displaying on actual hardware and there is gnustep-corebase which is a glue library to use objective C objects from C and to deal with the fundamental data types of objective C like NSData, NSArray etc.

== compiling libobjc2 ==

cd libobjc2
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DBUILD_STATIC_LIBOBJC=1 \
-DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_LINKER=${LD} \
-DCMAKE_MODULE_LINKER_FLAGS=${LDFLAGS}
make -j40
make install
ldconfig
make test
cd ../..

this should pass everywhere except these two which according to David Chisnal are corner cases which shouldn't affect real software:

18 - AssociatedObject_optimised (OTHER_FAULT)
20 - AssociatedObject_legacy_optimised (OTHER_FAULT)

== installing gnustep-make ==

Gnustep Make is a package of makefiles to be used inside Gnustep projects. This way some common settings can be shared along all projects such as the location of certain runtime files (defaults, file layouts etc). It does not have any compiled code but its needed for the rest.
Edit the file library-combo.make and on line 47 replace

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-1.8
endif

with

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-2.0
endif

Please note: Instead of editing the make file you can set the runtime version using the env variable as well:

export RUNTIME_VERSION=gnustep-2.0

or

export RUNTIME_VERSION=gnustep-1.9

For the older runtime.
Then you can install make

cd make
./configure \
--with-layout=fhs \
--disable-importing-config-file \
--enable-native-objc-exceptions \
--enable-objc-arc \
--enable-install-ld-so-conf \
--with-library-combo=ng-gnu-gnu \
--with-config-file=/usr/local/etc/GNUstep/GNUstep.conf \
--with-user-config-file='.GNUstep.conf' \
--with-user-defaults-dir='GNUstep/Library/Defaults'
make
make install

== installing gnustep-base ==

cd base
./configure --with-config-file=/usr/local/etc/GNUstep/GNUstep.conf
make -j8
make install
ldconfig
make check
cd ..

There is one test which will fail. For our usage this is not vital.

Failed test: basic.m:31 ... Expiration date can be retrieved

== installing gnustep-corebase ==

cd corebase
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-gui ==

cd gui
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-back ==

cd back
./configure
make -j8
make install
ldconfig
cd ..

Author: Andreas Fink as of 2019-05-05.

Building GNUstep under Debian FreeBSD

2020-02-20T07:44:43Z

Letterus: /* libiconv */ Added hints for newer versions of Debian

Here's a tutorial on how to to build gnustep and its dependencies if you want to run it using GNUstep runtime 2.0 (ng), which has to be built using clang 8.0.

You'll find these steps bundled in a script which you can execute under Debian 9 at https://github.com/plaurent/gnustep-build/tree/master/debian-9-clang-8.0-runtime-2.0.

== Install empty VM ==

We start with an empty Debian9 or FreeBSD 12 VM.

== Dependencies under Debian 9 ==

we install these packages under Debian as they are coming up as dependencies anyhow

apt-get install dirmngr
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com \
15CF4D18AF4F7421
sudo apt -y install build-essential git subversion \
libpthread-workqueue0 libpthread-workqueue-dev \
libxml2 libxml2-dev \
libffi6 libffi-dev \
libicu-dev \
libuuid1 uuid-dev uuid-runtime \
libsctp1 libsctp-dev lksctp-tools \
libavahi-core7 libavahi-core-dev \
libavahi-client3 libavahi-client-dev \
libavahi-common3 libavahi-common-dev libavahi-common-data \
libgcrypt20 libgcrypt20-dev \
libtiff5 libtiff5-dev \
libbsd0 libbsd-dev \
util-linux-locales \
locales-all \
libjpeg-dev \
libtiff-dev \
libcups2-dev \
libfreetype6-dev \
libcairo2-dev \
libxt-dev \
libgl1-mesa-dev \
libpcap-dev \
libc-dev libc++-dev libc++1 \
python-dev swig \
libedit-dev libeditline0 libeditline-dev readline-common \
binfmt-support libtinfo-dev \
bison flex m4 wget \
libicns1 libicns-dev \
libxslt1.1 libxslt1-dev \
libxft2 libxft-dev \
libflite1 flite1-dev \
libxmu6 libxpm4 wmaker-common \
libgnutls30 libgnutls28-dev \
libpng-dev libpng16-16 \
default-libmysqlclient-dev \
libpq-dev \
libstdc++-6-dev \
libreadline7 libreadline-dev \gobjc-6 gobjc++-6 \
libgif7 libgif-dev libwings3 libwings-dev libwraster5 \
libwraster-dev libwutil5 \
libcups2-dev libicu57 libicu-dev \
gobjc++ \
xorg \
libfreetype6 libfreetype6-dev \
libpango1.0-dev \
libcairo2-dev \
libxt-dev libssl-dev \
libasound2-dev libjack-dev libjack0 libportaudio2 \
libportaudiocpp0 portaudio19-dev \
libstdc++-6-dev libstdc++-6-doc libstdc++-6-pic \
libstdc++6 wmaker cmake cmake-curses-gui xpdf

== Dependencies under FeeBSD 12 ==

pkg install git \
autoconf \
automake \
cmake \
subversion \
wget \
bash \
pkgconf \
sudo \
gmake \
windowmaker \
jpeg \
tiff \
png \
libxml2 \
libxslt \
gnutls \
libffi \
icu \
cairo \
avahi \
portaudio \
flite \
pngwriter \
mariadb103-client \
postgresql96-client \
bash \
clang \
lldb

== We install a decent clang compiler. ==

clang-8: from clang8 repository: Add a file /etc/apt/sources.d/llvm.list with content

deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main

To install you call it like this:

apt-get update
apt-get install clang-8 lldb-8 lld-8

Note: clang-7 has a bug which makes gnustep-base fail during its ./configure phase.

(Note today clang-8 was no longer in the llvm repo for some reason. Maybe temporary issue. I also tried the bleeding edge clang-9 and that worked similarly)

Under FreeBSD we use the clang compiler which comes with FreeBSD12.
If you use CentOS 7 or the like, you probably have to compile the clang compiler from source. this is time consuming and can be done like tis:

git clone https://git.llvm.org/git/llvm.git/
cd llvm/tools
git clone https://git.llvm.org/git/clang.git/
cd ../projects
git clone https://git.llvm.org/git/compiler-rt.git/
cd ..
mkdir BUILD
cd BUILD
cmake .. -DCMAKE_BUILD_TYPE=Release make -j8
make install

(note this installs your compiler in /usr/local/bin so you have to change the path on the later stages below)

== Download GNUSTEP ==

We download the sources we need:

mkdir gnustep
cd gnustep
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.15.tar.gz
git clone https://github.com/apple/swift-corelibs-libdispatch
git clone https://github.com/gnustep/scripts
git clone https://github.com/gnustep/make
git clone https://github.com/gnustep/libobjc2
git clone https://github.com/gnustep/base
git clone https://github.com/gnustep/corebase
git clone https://github.com/gnustep/gui
git clone https://github.com/gnustep/back
./scripts/install-dependencies

The last step should basically not show any additional dependency we have not already covered. On FreeBSD , the last step has to be skipped as the script is not prepared for FreeBSD yet.

== libiconv ==

This applies for Debian 9 (or maybe older). From Debian 10 upwards you won't need to install libiconv. You do not have to do this when installing for Ubuntu.

We compile libiconv. Debian comes standard with version 1.14 but there was an issue in 1.14 which got fixed in 1.15 which was relevant to us so using 1.15 is recommended.

tar -xvzf libiconv-1.15.tar.gz
cd libiconv-1.15
./configure --enable-static --enable-dynamic
make
make install
cd ..

== Defaults ==

We set some environment defaults for the remainder of the session

# we set the C and C++ compiler version
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export RUNTIME_VERSION=gnustep-2.0
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD=/usr/bin/ld.gold
export LDFLAGS=-fuse-ld=/usr/bin/ld.gold
export OBJCFLAGS="-fblocks"

Using the ld.gold linker is important as otherwise strange things happens. old ld does stuff wrong, newer lld from clang optimises stuff away it shouldn't.

== libdispatch ==

The libdispatch is an open source library supplied by Apple which takes care of running multiple background tasks. Apple calls it "Grand Central Dispatch". The Swift language also uses it, hence the repo name. We're not really directly using it but other objc code might use it or benefit from it so we compile it as well.

cd swift-corelibs-libdispatch
mkdir build
cd build
cmake .. -DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_BUILD_TYPE=Release \
-DUSE_GOLD_LINKER=YES
make -j40
make install
ldconfig

== libobjc2 / gnustep-base ==

Now we have reached a point where the magic triple libobjc2 + gnustep-make + gnustep-base comes into play. To understand the context here. The objectiveC compiler needs a runtime. The runtime is taking care of the basic functionality of objectiveC objects such as their memory allocation and release and other stuff. The compiler calls the runtime when specific stuff happens. When a method is called, the compiler puts a call into the runtime which then looks up the dynamic methods and calls the method etc. When a block ends and certain objects are no longer needed, the compiler calls the runtime so it can release the objects accordingly.

There are different runtimes around. The original objectiveC runtime supplied by the gcc compiler. It's old, outdated and doesn't deal with automatic reference counting and a lot of other things. So it's not recommended. The libobjc2 is the "modern" rewrite for a runtime and is actually based on a project called Etoile. It's ABI has different variants. There is a fragile and a non fragile ABI.

Read this blogpost to understand what the difference is: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_explain_Non-fragile_ivars.html
If you get this is wrong, you might end up with objects no longer using the right position of variables in the data of super or subclasses and things can get totally out of control. So the new non-fragile-ABI is really the way to go. There are also different versions of the ABI on how the compiler calls the runtime. So the compiler and the runtime are working together as a team.

So once we have a runtime library which is a requirement for any objectiveC code, there is also the base library gnustep-base which corresponds to Apple's Foundation framework. This one implements basic functionality which is used in almost all ObjC code.. It brings stuff like dealing with strings, arrays, dictionaries, and lots of other things you need day in day out. It does not supply any GUI code. All NextStep/Apple ObjectiveC code is derived from a base class called NSObject which is defined in gnustep-base. GnuStep is an open source reimplementation of NextStep and the Apple Foundation/AppKit classes.

There are 3 other libraries in GnuStep which are gnustep-gui which does all the graphical interface, gnustep-back which is the backend for the GUI (so there's a variant for X-windows, one for Windows, one for MacOS aqua etc) which is like a driver for the gui to do the displaying on actual hardware and there is gnustep-corebase which is a glue library to use objective C objects from C and to deal with the fundamental data types of objective C like NSData, NSArray etc.

== compiling libobjc2 ==

cd libobjc2
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DBUILD_STATIC_LIBOBJC=1 \
-DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_LINKER=${LD} \
-DCMAKE_MODULE_LINKER_FLAGS=${LDFLAGS}
make -j40
make install
ldconfig
make test
cd ../..

this should pass everywhere except these two which according to David Chisnal are corner cases which shouldn't affect real software:

18 - AssociatedObject_optimised (OTHER_FAULT)
20 - AssociatedObject_legacy_optimised (OTHER_FAULT)

== installing gnustep-make ==

Gnustep Make is a package of makefiles to be used inside Gnustep projects. This way some common settings can be shared along all projects such as the location of certain runtime files (defaults, file layouts etc). It does not have any compiled code but its needed for the rest.
Edit the file library-combo.make and on line 47 replace

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-1.8
endif

with

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-2.0
endif

Please note: Instead of editing the make file you can set the runtime version using the env variable as well:

export RUNTIME_VERSION=gnustep-2.0

or

export RUNTIME_VERSION=gnustep-1.9

For the older runtime.
Then you can install make

cd make
./configure \
--with-layout=fhs \
--disable-importing-config-file \
--enable-native-objc-exceptions \
--enable-objc-arc \
--enable-install-ld-so-conf \
--with-library-combo=ng-gnu-gnu \
--with-config-file=/usr/local/etc/GNUstep/GNUstep.conf \
--with-user-config-file='.GNUstep.conf' \
--with-user-defaults-dir='GNUstep/Library/Defaults'
make
make install

== installing gnustep-base ==

cd base
./configure --with-config-file=/usr/local/etc/GNUstep/GNUstep.conf
make -j8
make install
ldconfig
make check
cd ..

There is one test which will fail. For our usage this is not vital.

Failed test: basic.m:31 ... Expiration date can be retrieved

== installing gnustep-corebase ==

cd corebase
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-gui ==

cd gui
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-back ==

cd back
./configure
make -j8
make install
ldconfig
cd ..

Author: Andreas Fink as of 2019-05-05.

Building GNUstep under Debian FreeBSD

2020-02-20T07:42:01Z

Letterus: /* installing gnustep-make */

Here's a tutorial on how to to build gnustep and its dependencies if you want to run it using GNUstep runtime 2.0 (ng), which has to be built using clang 8.0.

You'll find these steps bundled in a script which you can execute under Debian 9 at https://github.com/plaurent/gnustep-build/tree/master/debian-9-clang-8.0-runtime-2.0.

== Install empty VM ==

We start with an empty Debian9 or FreeBSD 12 VM.

== Dependencies under Debian 9 ==

we install these packages under Debian as they are coming up as dependencies anyhow

apt-get install dirmngr
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com \
15CF4D18AF4F7421
sudo apt -y install build-essential git subversion \
libpthread-workqueue0 libpthread-workqueue-dev \
libxml2 libxml2-dev \
libffi6 libffi-dev \
libicu-dev \
libuuid1 uuid-dev uuid-runtime \
libsctp1 libsctp-dev lksctp-tools \
libavahi-core7 libavahi-core-dev \
libavahi-client3 libavahi-client-dev \
libavahi-common3 libavahi-common-dev libavahi-common-data \
libgcrypt20 libgcrypt20-dev \
libtiff5 libtiff5-dev \
libbsd0 libbsd-dev \
util-linux-locales \
locales-all \
libjpeg-dev \
libtiff-dev \
libcups2-dev \
libfreetype6-dev \
libcairo2-dev \
libxt-dev \
libgl1-mesa-dev \
libpcap-dev \
libc-dev libc++-dev libc++1 \
python-dev swig \
libedit-dev libeditline0 libeditline-dev readline-common \
binfmt-support libtinfo-dev \
bison flex m4 wget \
libicns1 libicns-dev \
libxslt1.1 libxslt1-dev \
libxft2 libxft-dev \
libflite1 flite1-dev \
libxmu6 libxpm4 wmaker-common \
libgnutls30 libgnutls28-dev \
libpng-dev libpng16-16 \
default-libmysqlclient-dev \
libpq-dev \
libstdc++-6-dev \
libreadline7 libreadline-dev \gobjc-6 gobjc++-6 \
libgif7 libgif-dev libwings3 libwings-dev libwraster5 \
libwraster-dev libwutil5 \
libcups2-dev libicu57 libicu-dev \
gobjc++ \
xorg \
libfreetype6 libfreetype6-dev \
libpango1.0-dev \
libcairo2-dev \
libxt-dev libssl-dev \
libasound2-dev libjack-dev libjack0 libportaudio2 \
libportaudiocpp0 portaudio19-dev \
libstdc++-6-dev libstdc++-6-doc libstdc++-6-pic \
libstdc++6 wmaker cmake cmake-curses-gui xpdf

== Dependencies under FeeBSD 12 ==

pkg install git \
autoconf \
automake \
cmake \
subversion \
wget \
bash \
pkgconf \
sudo \
gmake \
windowmaker \
jpeg \
tiff \
png \
libxml2 \
libxslt \
gnutls \
libffi \
icu \
cairo \
avahi \
portaudio \
flite \
pngwriter \
mariadb103-client \
postgresql96-client \
bash \
clang \
lldb

== We install a decent clang compiler. ==

clang-8: from clang8 repository: Add a file /etc/apt/sources.d/llvm.list with content

deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch main
deb http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main
deb-src http://apt.llvm.org/stretch/ llvm-toolchain-stretch-8 main

To install you call it like this:

apt-get update
apt-get install clang-8 lldb-8 lld-8

Note: clang-7 has a bug which makes gnustep-base fail during its ./configure phase.

(Note today clang-8 was no longer in the llvm repo for some reason. Maybe temporary issue. I also tried the bleeding edge clang-9 and that worked similarly)

Under FreeBSD we use the clang compiler which comes with FreeBSD12.
If you use CentOS 7 or the like, you probably have to compile the clang compiler from source. this is time consuming and can be done like tis:

git clone https://git.llvm.org/git/llvm.git/
cd llvm/tools
git clone https://git.llvm.org/git/clang.git/
cd ../projects
git clone https://git.llvm.org/git/compiler-rt.git/
cd ..
mkdir BUILD
cd BUILD
cmake .. -DCMAKE_BUILD_TYPE=Release make -j8
make install

(note this installs your compiler in /usr/local/bin so you have to change the path on the later stages below)

== Download GNUSTEP ==

We download the sources we need:

mkdir gnustep
cd gnustep
wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.15.tar.gz
git clone https://github.com/apple/swift-corelibs-libdispatch
git clone https://github.com/gnustep/scripts
git clone https://github.com/gnustep/make
git clone https://github.com/gnustep/libobjc2
git clone https://github.com/gnustep/base
git clone https://github.com/gnustep/corebase
git clone https://github.com/gnustep/gui
git clone https://github.com/gnustep/back
./scripts/install-dependencies

The last step should basically not show any additional dependency we have not already covered. On FreeBSD , the last step has to be skipped as the script is not prepared for FreeBSD yet.

== libiconv ==

We compile libiconv. Debian comes standard with version 1.14 but there was an issue in 1.14 which got fixed in 1.15 which was relevant to us so using 1.15 is recommended.

tar -xvzf libiconv-1.15.tar.gz
cd libiconv-1.15
./configure --enable-static --enable-dynamic
make
make install
cd ..

== Defaults ==

We set some environment defaults for the remainder of the session

# we set the C and C++ compiler version
export CC=/usr/bin/clang-8
export CXX=/usr/bin/clang++-8
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export RUNTIME_VERSION=gnustep-2.0
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD=/usr/bin/ld.gold
export LDFLAGS=-fuse-ld=/usr/bin/ld.gold
export OBJCFLAGS="-fblocks"

Using the ld.gold linker is important as otherwise strange things happens. old ld does stuff wrong, newer lld from clang optimises stuff away it shouldn't.

== libdispatch ==

The libdispatch is an open source library supplied by Apple which takes care of running multiple background tasks. Apple calls it "Grand Central Dispatch". The Swift language also uses it, hence the repo name. We're not really directly using it but other objc code might use it or benefit from it so we compile it as well.

cd swift-corelibs-libdispatch
mkdir build
cd build
cmake .. -DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_BUILD_TYPE=Release \
-DUSE_GOLD_LINKER=YES
make -j40
make install
ldconfig

== libobjc2 / gnustep-base ==

Now we have reached a point where the magic triple libobjc2 + gnustep-make + gnustep-base comes into play. To understand the context here. The objectiveC compiler needs a runtime. The runtime is taking care of the basic functionality of objectiveC objects such as their memory allocation and release and other stuff. The compiler calls the runtime when specific stuff happens. When a method is called, the compiler puts a call into the runtime which then looks up the dynamic methods and calls the method etc. When a block ends and certain objects are no longer needed, the compiler calls the runtime so it can release the objects accordingly.

There are different runtimes around. The original objectiveC runtime supplied by the gcc compiler. It's old, outdated and doesn't deal with automatic reference counting and a lot of other things. So it's not recommended. The libobjc2 is the "modern" rewrite for a runtime and is actually based on a project called Etoile. It's ABI has different variants. There is a fragile and a non fragile ABI.

Read this blogpost to understand what the difference is: http://www.sealiesoftware.com/blog/archive/2009/01/27/objc_explain_Non-fragile_ivars.html
If you get this is wrong, you might end up with objects no longer using the right position of variables in the data of super or subclasses and things can get totally out of control. So the new non-fragile-ABI is really the way to go. There are also different versions of the ABI on how the compiler calls the runtime. So the compiler and the runtime are working together as a team.

So once we have a runtime library which is a requirement for any objectiveC code, there is also the base library gnustep-base which corresponds to Apple's Foundation framework. This one implements basic functionality which is used in almost all ObjC code.. It brings stuff like dealing with strings, arrays, dictionaries, and lots of other things you need day in day out. It does not supply any GUI code. All NextStep/Apple ObjectiveC code is derived from a base class called NSObject which is defined in gnustep-base. GnuStep is an open source reimplementation of NextStep and the Apple Foundation/AppKit classes.

There are 3 other libraries in GnuStep which are gnustep-gui which does all the graphical interface, gnustep-back which is the backend for the GUI (so there's a variant for X-windows, one for Windows, one for MacOS aqua etc) which is like a driver for the gui to do the displaying on actual hardware and there is gnustep-corebase which is a glue library to use objective C objects from C and to deal with the fundamental data types of objective C like NSData, NSArray etc.

== compiling libobjc2 ==

cd libobjc2
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release \
-DBUILD_STATIC_LIBOBJC=1 \
-DCMAKE_C_COMPILER=${CC} \
-DCMAKE_CXX_COMPILER=${CXX} \
-DCMAKE_LINKER=${LD} \
-DCMAKE_MODULE_LINKER_FLAGS=${LDFLAGS}
make -j40
make install
ldconfig
make test
cd ../..

this should pass everywhere except these two which according to David Chisnal are corner cases which shouldn't affect real software:

18 - AssociatedObject_optimised (OTHER_FAULT)
20 - AssociatedObject_legacy_optimised (OTHER_FAULT)

== installing gnustep-make ==

Gnustep Make is a package of makefiles to be used inside Gnustep projects. This way some common settings can be shared along all projects such as the location of certain runtime files (defaults, file layouts etc). It does not have any compiled code but its needed for the rest.
Edit the file library-combo.make and on line 47 replace

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-1.8
endif

with

ifeq ($(RUNTIME_VERSION),)
RUNTIME_VERSION=gnustep-2.0
endif

Please note: Instead of editing the make file you can set the runtime version using the env variable as well:

export RUNTIME_VERSION=gnustep-2.0

or

export RUNTIME_VERSION=gnustep-1.9

For the older runtime.
Then you can install make

cd make
./configure \
--with-layout=fhs \
--disable-importing-config-file \
--enable-native-objc-exceptions \
--enable-objc-arc \
--enable-install-ld-so-conf \
--with-library-combo=ng-gnu-gnu \
--with-config-file=/usr/local/etc/GNUstep/GNUstep.conf \
--with-user-config-file='.GNUstep.conf' \
--with-user-defaults-dir='GNUstep/Library/Defaults'
make
make install

== installing gnustep-base ==

cd base
./configure --with-config-file=/usr/local/etc/GNUstep/GNUstep.conf
make -j8
make install
ldconfig
make check
cd ..

There is one test which will fail. For our usage this is not vital.

Failed test: basic.m:31 ... Expiration date can be retrieved

== installing gnustep-corebase ==

cd corebase
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-gui ==

cd gui
./configure
make -j8
make install
ldconfig
cd ..

== installing gnustep-back ==

cd back
./configure
make -j8
make install
ldconfig
cd ..

Author: Andreas Fink as of 2019-05-05.