Date:	17-Sep-2002 (tested under windows-xp)
Author: Ildar Mulyukov <ildar@users.sourceforge.net>
Update:	23-Oct-2004 (tested under windows-2000)
Author: Adam Fedor <fedor@gnu.org>


PURPOSE
-------

This document may be treated as just an appendix to GNUstep-HOWTO. You
can find GNUstep-HOWTO link here:
http://gnustep.org/experience/documentation.html

This document is intended to provide a step by step instruction on how
to get the GNUstep base library into a usable state on a recent windows
operating system (XP, 2000, and probably NT) within Cygwin environment.

Cygwin is unix-like environment working on top of Win32 (Windows, Windows
NT/2k/XP). You can find complete information about it on the website
http://cygwin.org

For the moment GNUstep can be built with GUI support. (Native Win32
GUI, not X11) The gui library is only partially ported to run under
Win32 API so be warned.

Several people have reported that GNUstep installation on Cygwin works
fine, but as always, a slightly different Window's setup can cause
unforseen problems. You should be relatively confident at working with
Cygwin before attempting to install GNUstep.

ADDITIONAL COMMENTS
-------------------

Note: These comments are just my experience. You don't need these to build
GNUstep. If you don't understand something don't worry.

Cygwin project is now in a very advanced stage. It's ready to be used by
end-users and in commercial purposes and very convenient for programmers.

Cygwin provides "General UNIX" environment and APIs. In fact
GNUstep-base is compiled using Unix alternatives of classes (like
NSConcreteUnixTask). But it has several particularities that must been
taken into consideration. There is a very good documentation on Cygwin
website on these questions. See e.g.
http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html I would like to
mention two of them:

1. Filesystem is case-insensitive. Now it's (luckily) supports
soft-links. But case-insensitivity hinders quite a lot.

2. Dynamic libraries mechanism is not so good. (Windows DLL). It does
not support several features (and this makes so hard to port some
software e.g. licq) And it has those ugly __declspec(dllexport) /
__declspec(dllimport) . But (Cygwin hackers are just cool!) in later
releases of binutils ld is capable to link wrongly declared exports!
This eliminates a lot of problems when dealing with DLLs (including
objc.dll and gnustep-*.dll)

PRELIMINARIES
-------------

Before you start, you need Cygwin in some programming-oriented
configuration (full configuration is OK but it's VERY big
now). Installation instructions are on Cygwin site.

Cygwin already contains every package needed for GNUstep. The default
installation, however, does not include every package needed. See the
GNUstep-HOWTO lists all the packages you might need. A probably incomplete
list is given below:

For base (non-GUI):
gcc-objc
libxml2
libxslt

For GUI:
X11 installation
libtiff
libtiff-devel
libjpg
libpng


Obtaining GNUstep
-----------------

The main GNUstep project pages tell you how to get hold of this. You
can get the latest release of the following libraries.

You need these packages:

GNUstep-make
ffcall
GNUstep-objc
GNUstep-base

GNUstep-gui
GNUstep-back


Building and installing libraries
---------------------------------

FFCALL: Unpack, configure, make, make install. See GNUstep-HOWTO for details.
Note again: you can make package. See APPENDIX A


Building and installing gnustep-make
------------------------------------

As ususal. e.g.

./configure
make
make install


Building and installing libobjc
-------------------------------

You need to install gnustep-objc as it properly exports symbols for
DLLs and it's DLL.

Unpack gnustep-objc, and type:

  make install

Note: do not use configure.


Building and installing GNUstep-base
------------------------------------

Unpack gnustep-base, and type:

  make install

This should automatically run the configure script for you, build the
base library and some tools, and install the whole lot.


Building and installing GNUstep-gui
-----------------------------------

Unpack to gnustep-gui, and type:

  make install


Building and installing GNUstep-back
------------------------------------

In the back directory, type

  make install



Troubleshooting
---------------

APPENDIX A
----------

This is mkpkg.sh script for making packages from sources.

#!/bin/bash
# make a cygwin package
#   launch this script in the building dir

TMPDIR=/tmp/__TMP_$RANDOM
FLIST=$TMPDIR/files.list

rm -rf $TMPDIR
mkdir $TMPDIR

touch /usr/time.stamp
make install

pushd .
cd /
find usr ! -type d -newer /usr/time.stamp > $FLIST
rm /usr/time.stamp

# Don't forget to rename it to real package name
tar cjf $TMPDIR/package.tar.bz2 `cat $FLIST`
popd

unset TMPDIR FLIST

--- *** CUT *** ---

Date : 15-Jan-2004
Last update: 20071229
Authors: Adam Fedor <fedor@gnu.org>
         Quentin Math� <qmathe@club-internet.fr>
         Lars S.-Helldorf <lars.sonchocky-helldorf@hamburg.de>

PURPOSE
-------

This document is intended to provide a step by step instruction on how to get
the GNUstep installed on Mac OS X and Darwin.

COMMONLY USED SYMBOLS
---------------------

<> denotes a variable depending on your preferences. To be replaced with the
actual values from your system. For instance, if you installed GCC in /opt/local

     ./configure CC=<gcc install dir>/bin/gcc

will become:

     ./configure CC=/opt/local/bin/gcc

[] denotes an optional parameter. For instance:

     ./configure [--enable-graphics=art]

can be either:

     ./configure

or:

     ./configure --enable-graphics=art

PRELIMINAIRES
-------------

For all targets, get the following software. I'd recommend installing
Fink (and FinkCommander on Mac OS X) or MacPorts to get all this
software. Make sure that Fink or MacPorts is in your path; newer
versions do a good job of doing this for you. It's quite possible for
libraries installed via Fink/Macports to conflict with Apple
libraries, which cause strange errors running GNUstep apps (like odd
crashes and seg faults).  In that cause you might want to hand-compile
the libraries you need (only the tiff and libffi libraries are REALLY needed,
everything else is basically optional).

Remember you usually need root access to install software. That means when you
see an instruction like 'make install', you usually need to use sudo
('sudo make install') or be logged in as root (not recommended).

     libxml2  (Optional, highly recommended, already in
               Mac OS X 10.3 / Darwin 7 and later)
     libxslt  (Optional)
     libtiff  (Required)
     libjpeg  (Optional, highly recommended - don't get from fink!)
     libpng   (Optional, highly recommended)

     libffi   (Required, from ftp.gnustep.org/pub/gnustep/libs)
     ffcall   (On Darwin x86 - use instead of libffi)

     Xfree86  (Required, already in Mac OS X 10.3/Darwin 7 and later)

     libart2   (Required for art backend)
     freetype2 (Required for art backend)

     dlcompat (Required, already in Mac OS X 10.3 or later)

Obtaining GNUstep
-----------------

The main GNUstep project pages tell you how to get hold of this. You
can get the latest release of the following libraries.  You need these
gnustep packages:

     GNUstep-make
     GNUstep-base
     GNUstep-gui
     GNUstep-back

Targets
-------

For GNUstep, there are several combinations of Objective-C runtime, Foundation
library and Application Kit library possible, called library combos. The usual
notation is:

     objcruntime-foundation-applicationkit

Theoretically possible are:

     gnu-gnu-gnu       # gnu-objc runtime with gnustep-base and gnustep-gui.
                       # Most widely tested.
     apple-gnu-gnu     # apple-objc runtime with gnustep libraries. Does
                       # not work.
     apple-apple-gnu   # Apple Foundation with gnustep-gui on the top. Only of
                       # academic interest.
     apple-apple-apple # Cocoa with GNUstep additions. For porting GNUstep apps
                       # to Cocoa.

All gnu-*-apple library combos are purely theoretical and only available to the
folks inside Apple since no mortal person ever saw the Cocoa source code. ;-)
You can use either the Apple compiler or compile your own FSF compiler. This
potentially gives two different targets:

     Apple GCC, gnu-gnu-gnu
     FSF   GCC, gnu-gnu-gnu

In addition, if you are on Mac OS X, you can also use the Apple
Foundation and AppKit frameworks to do GNUstep development with Cocoa,
but this only works with the Apple compiler:

     Apple GCC, apple-apple-apple

GNUstep on Darwin x86
---------------------

For GNUstep on Darwin x86, Apple GCC compiles GNUstep-base, but causes strange
problems when running programs (e.g. the program hangs while allocating memory
or executes methods multiple times). So we have to use FSF GCC.  Additionally,
libffi has not been ported to Darwin x86, so you will need to install ffcall
instead. NOTE: Has not been tested in a long time...

GNUstep on Darwin PowerPC
-------------------------

You can use either the Apple compiler of the FSF compiler. For the Apple
compiler, you need at least Mac OS X 10.4 with XCode 2.5 release.

Building FSF-GCC
----------------

The easiest way to get FSF GCC is through Fink or MacPorts. If you
would like to compile by hand, follow these directions:

Darwin x86:

FSF GCC is difficult to compile here. The only way I could do it was like this:

     ln -s /usr/bin/c++filt /usr/bin/c++filt3          # Missing on Darwin 7.0.1
                                                       # x86 but not necessary
                                                       # on OpenDarwin 7.2.1

and then configure GCC with:

     mkdir build                                       # Create a sibling to the
                                                       # toplevel source dir
     cd build
     <dir>/gcc-X.X.X/configure \                       # Don't try to build c++
      --enable-languages=c,objc

     make bootstrap
     make install
     cd /usr/local/lib
     ln -s libobjc.a libobjc.dylib                     # So the linker sees us

(Replace X.X.X with the actual distribution you have).

GCC on Darwin doesn't appear to support threads.

Darwin PowerPC:

Configure and build as follows (tested using gcc-3.3.2 on Mac OS X 10.2 and
10.3):

     mkdir build
     cd build
     <dir>/gcc-x.x.x/configure \                       # The first option
     [--prefix=<gcc install dir>] \                    # permits to change the
     [--enable-languages=c,objc]                       # fact GCC installs by
                                                       # default in /usr/local
                                                       # The second option
                                                       # permits to speed the
                                                       # GCC compilation in the
                                                       # case you will not use
                                                       # languages other than c
                                                       # and objc

     make bootstrap
     make install
     cd <gcc install dir>/lib
     ln -s libobjc.a libobjc.dylib                     # So the linker sees us
     # Note when using gcc 4 or greater, make sure this is libobjc-gnu.dylib

Setting up the GNUstep make environment
---------------------------------------

In the GNUstep-make (core/make) package, do with bourne shell like bash
(Mac OS X 10.3):

     echo 'export CC=<gcc install dir>/bin/gcc' >> ~/.profile

with c shell like tcsh (Mac OS X 10.2):

     echo 'setenv CC <gcc install dir>/bin/gcc' >> ~/.tcshrc

else use [CC=<gcc install dir>/bin/gcc] option when running configure.

then:

     ./configure --with-library-combo=gnu-gnu-gnu \
     [--prefix=<GNUstep install dir>] [CC=<gcc install dir>/bin/gcc]

(apple-apple-apple is the default if you don't specify
gnu-gnu-gnu). If you want to be able to compile for different
targets/platforms together. Do this:

     ./configure --with-library-combo=gnu-gnu-gnu --disable-flattened \
     --enable-multi-platform [--prefix=<GNUstep install dir>] \
     [CC=<gcc install dir>/bin/gcc]

Now:

     make
     make install

Source GNUstep.sh
-----------------

If you are using bourne shell like bash, type:

     . <GNUstep install dir>/System/Library/Makefiles/GNUstep.sh

If you are using c shell like tcsh, type:

     source <GNUstep install dir>/System/Library/Makefiles/GNUstep.csh

Building and installing libobjc (target Apple GCC, gnu-gnu-gnu only !!!)
-------------------------------

Warning ! Don't compile libobjc if you are using FSF GCC.  Go to gnustep-objc
(or from CVS, into dev-libs/libobjc), and type:

     make install
     cd $GNUSTEP_SYSTEM_ROOT/Library/Libraries
     ln -s libobjc.dylib libobjc-gnu.dylib

This should build and install the GNU Objective-C runtime and headers for you.

Building and installing libffi (on Darwin PowerPC only !!!)
------------------------------

There's no official libffi release. Get the one from the GNUstep ftp site

     ./configure --prefix=$GNUSTEP_SYSTEM_ROOT \
     --libdir=$GNUSTEP_SYSTEM_ROOT/Library/Libraries \
     --includedir=$GNUSTEP_SYSTEM_ROOT/Library/Headers
     make
     make install

Building and installing ffcall (on Darwin x86 only (may work on PPC))
------------------------------

     ./configure --prefix=$GNUSTEP_SYSTEM_ROOT \
     --libdir=$GNUSTEP_SYSTEM_ROOT/Library/Libraries \
     --includedir=$GNUSTEP_SYSTEM_ROOT/Library/Headers
     make
     make install

Building and installing GNUstep-base
------------------------------------

     ./configure [--with-xml-prefix=/usr] [--disable-xmltest] [--disable-do] \
     [LDFLAGS=-L/sw/lib] [CPPFLAGS=-I/sw/include] [CC=<gcc install dir>/bin/gcc] \
     [CPPFLAGS=-fnested-functions]

To know which options you need to use with your environment:

     --disable-xmltest is needed with Mac OS X 10.3 / Darwin 7
     versions xml2-config tool and libxml2 headers reports differents versions,
     because of this versions conflict the GNUstep xmltest fails.

     --with-xml-prefix=/usr is needed with Mac OS X 10.3 / Darwin 7 when you
     want to build the base library with xslt support and you have installed
     libxslt with Fink (because Fink installs lixml2 without the headers when
     you install lixslt, and by default the base library tries to link Fink
     libxml2 first, then the configuration fails because configure looks for
     the libxml2 headers).

     --disable-do is needed when you decide to not build libffi or ffcall. You
     probably do not want to do this.

     LDFLAGS=-L/sw/lib is needed when you installed libxslt with Fink and you
     want to compile the base library with libxslt support.

     CPPFLAGS=-I/sw/include is needed when you installed libxslt with Fink and
     you want to compile the base library with libxslt support.

     CPPFLAGS=-fnested-functions is required when using Apple gcc

followed by:

     make
     make install

On the apple-apple-apple target, it will only build the GNUstep additions
library that adds extra stuff to Foundation. If you are using the
apple-apple-apple target, there currently is no reason to go on and compile
GNUstep-gui.

Building and installing GNUstep-gui
-----------------------------------

Go to GNUstep-gui (or from CVS into the core/gui directory).

     ./configure --disable-gsnd

followed by:

     make
     make install

Note: The gsnd server hasn't been ported to Mac OS X / Darwin yet.

Some other configure options:
    --with-jpeg-library=<jpeg libdir>
    --with-jpeg-include=<jpeg include dir>
      to have the libjpeg detected.
    --disable-jpeg

Building and installing GNUstep-back
------------------------------------

Warning !  You must have installed X11User.pkg from the Panther
install disc and also X11SDK.pkg from the xCode Tools install disc to
be able to compile GNUstep-back under Mac OS X 10.3.

If you aren't installing GNUstep under Mac OS X 10.3 / Darwin 7, you can use
XDarwin (ftp://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/Darwin-ppc-6.x/) for
the X server, take a look at http://www.xdarwin.org

In the back directory, type:

     ./configure
     make
     make install

In the case, you choose to use the art backend, you will need to have the
freetype2 and libart2 libraries installed, first be sure to have libart2 in your
path, for example, with Fink installation type:

     export DYLD_LIBRARY_PATH=/sw/lib:$DYLD_LIBRARY_PATH

NOTE: I found also that even though the X11SDK.pkg package has freetype2,
it is missing a crucial include file and also has some undefined symbols. I
had to install the freetype2-dev package from fink and add this to my path
so that it could be found:
PATH=/sw/lib/freetype/bin:$PATH
make sure in config.make that -L/sw/lib/freetype2/lib is included before -L/usr/X11R6/lib (Adam Fedor <fedor@gnu.org>) Mac OS X 10.4 doesn't have this problem.

You also need to have /sw/lib in your library path before running GNUstep apps
with the art backend, as it needs to find libart2, so put the above export
DYLD_LIBRARY_PATH somewhere in your .profile (or do the export before launching
an application). The backend architecture which GNUstep-gui is built upon, has
been written to be used within X Windows, then you need to start up an X Server
(like Apple X11) to run the GNUstep-gui applications.

Warning ! With the art backend, before to launch applications based on
GNUstep-gui, in the shell, don't forget to edit the defaults (no need it to redo
it later):

     defaults write NSGlobalDomain XWindowBufferUseXShm NO

because Apple X11 doesn't support well shared memory for buffering (which
libart2 uses by default).

POTENTIAL ERRORS WHEN RUNNING MAKE ESPECIALLY WITH BACK AND GUI
---------------------------------------------------------------

If you get errors like below, just do:

     make clean
     make

The second or the third time, the errors should disappear. It's probably due to
some potential issues between FSF GCC and the libtool/ld Mac OS X / Darwin
versions.

     Linking subproject x11 ...
     /usr/bin/ld: shared_obj/xdnd.o bad magic number (not a Mach-O file)
     collect2: ld returned 1 exit status
     make[3]: *** [shared_obj/subproject.o] Error 1
     make[2]: *** [x11.all.subproject.variables] Error 2
     make[1]: *** [libgnustep-back.all.bundle.variables] Error 2
     make: *** [internal-all] Error 2

More informations on the art backend
------------------------------------

To have a working art backend... You will also need to download and install
fonts, as it uses a specific font format. Use for example the file
http://w1.423.telia.com/~u42308495/alex/backart/ArtResources-0.1.2.tar.bz2 and
put the .nfont directories somewhere in $(GNUSTEP_SYSTEM_ROOT)/Library/Fonts

Other fonts are available on http://www.knuddel.org/Downloads/Fonts/

Window Maker
------------

Window Maker is the traditional window manager for GNUstep.

In the case you choose to use it, don't forget to execute wmaker.inst else
Window Maker will crash with signal 10.

Example with Fink, do:

     /sw/bin/wmaker.inst

GNUstep daemons
---------------

Refer to GNUstep-HOWTO to know how to launch GNUstep daemons.

Note: If you try to start GNUstep daemons by hand with 'sudo opentool dameon',
it won't work, because when you become root on Mac OS X / Darwin with sudo or
su, the DYLD_LIBRARY_PATH environment variable of your user isn't used, then to
start them in the shell, do:

     sudo opentool gdomap                              # gdomap doesn't rely on
                                                       # the GNUstep libraries
                                                       # or other special
                                                       # librairies.
     su root

then with bourne shell like bash (Mac OS X 10.3):

     . $GNUSTEP_SYSTEM_ROOT/Library/Makesfiles/GNUstep.sh

or with c shell like tcsh (Mac OS X 10.2):

     source $GNUSTEP_SYSTEM_ROOT/Library/Makesfiles/GNUstep.csh

and just do:

     opentool gdnc
     opentool gpbs

GNUstep applications
--------------------

Now you can install GNUstep applications like Gorm, ProjectCenter etc.
Remember the fact that when you do 'sudo make install', the $DYLD_LIBRARY_PATH
variable of your user is not used by root. In that case, GNUstep-make could
complain for the undefined library path, the solution is identical to the one we
used to launch the GNUstep daemons above:

     su root

then with bourne shell like bash (Mac OS X 10.3):

     . $GNUSTEP_SYSTEM_ROOT/Library/MakeFiles/GNUstep.sh

or with c shell like tcsh (Mac OS X 10.2):

     . $GNUSTEP_SYSTEM_ROOT/Library/MakeFiles/GNUstep.sh

and just do:

     make install

Note: upon launching applications like Project Center which links a framework,
you will probably get an error message about the library
<Framework name>.framework/<Framework name> which cannot be found, to fix that,
just create a symbolic link to the actual library file, which is installed
deeper in the hierarchy:

     cd $GNUSTEP_SYSTEM_ROOT/Library/Frameworks/<Framework name>.framework
     sudo ln -s Versions/<Current version>/lib<Framework name>.dylib <Framework name>

Example with the ProjectCenter framework (0.4.0 version):

     cd $GNUSTEP_SYSTEM_ROOT/Library/Frameworks/ProjectCenter.framework
     sudo ln -s Versions/0.4.0/libProjectCenter.dylib.0.4.0 ProjectCenter

---

That's all.

Date:	28-Feb-2007
Update: 19-Feb-2015
Author: Nicola Pero <nicola.pero@meta-innovation.com>
        after Richard Frith-Macdonald <rfm@gnu.org>,
	Germán Arias <germanandre@gmx.es> and others.


PURPOSE
-------

This document is intended to provide a step by step instruction on how
to use GNUstep on recent Windows operating systems.

It will get as far as explaining how to build a GNUstep application
and create a standalone version that can be shipped standalone to
Windows end users.

The recommended way to get GNUstep working on Windows is to use MinGW
and MSYS to get a Unix-like environment where you can easily build
your GNUstep software (this is what is described in this file).

Software built in the MinGW/MSYS environment is native Windows
software that you can then run without having to rely on the environment
you used to build.

So, this document is divided in two parts.

In the first part ("STEP BY STEP INSTALLATION INSTRUCTIONS"), we will
describe how to get MinGW/MSYS up and running, and how to build
GNUstep software in this environment.

In the second part ("HOW TO SHIP YOUR GNUSTEP APPLICATION TO WINDOWS
USERS"), we'll show an example of how to package (and use) the .exes,
.dlls and resources (that you can build using the environment
described in the first part) as Windows standalone binaries.


INTRODUCTION TO MINGW
---------------------

MinGW is a collection of header files and import libraries that allow
one to use GCC and produce native Windows32 programs that do not rely
on any 3rd-party DLLs.

MSYS is a very much cut down version of the Cygwin environment ...
providing a minimal set of tools needed to build programs using
MingGW.  If you wish to build for MinGW by cross-compiling from a
Cygwin environment, please read README.Cygwin instead.


PRELIMINARIES
-------------

One way to vastly simplify installing GNUstep, is to use the Windows-based
GNUstep installer. Get it from:

http://www.gnustep.org/windows/installer.html

If you have already installed this, you can skip to the end and just
start compiling and packaging applications!  Although you may want to
read the rest of the instructions for other helpful information.



A. STEP BY STEP INSTALLATION INSTRUCTIONS
-----------------------------------------

1. Install MinGW
================

Download MinGW-Get-Setup.exe from

 http://sourceforge.net/projects/mingw/files/Installer/

Then start it up. Set the installation path to

C:\xxx\

Where \xxx\ is the top-level path you want to use, I use Nicola/GNUstep so
I install it into C:\Nicola\GNUstep\. We will refer to this path as MINGWPATH.


2. Install necessary packages
=============================

MinGW create an access on the desktop to the "MinGW installer", a package
manager you can use to install packages available to MinGW. To build GNUstep
you will need many packages.

At MinGW Installer select "All packages" and then install the following
packages (bin and dev packages when correspond):

(I'm really not sure if all them are necessary)

mingw32-autoconf
mingw32-binutils
mingw32-bzip2
mingw32-gcc
mingw32-gcc-g++
mingw32-gcc-objc
mingw32-gdb
mingw32-gmp
mingw32-libbz2
mingw32-libgmp
mingw32-libiconv
mingw32-libintl
mingw32-libpthread-old
mingw32-libpthreadgc
mingw32-libtool
mingw32-libunistring
mingw32-libz
mingw32-make
mingw32-pkginfo
mingw32-pthreads-w32
mingw32-w32api
msys-base
msys-bash
msys-console
msys-crypt
msys-diffutils
msys-libcrypt
msys-libgmp
msys-libiconv
msys-libminires
msys-m4
msys-minires
msys-zlib


3. Additional Useful Tools
==========================

You will need install GNUstep from Subversion, so you need a Subversion
client. I used:

http://www.sliksvn.com/pub/Slik-Subversion-1.6.9-win32.msi

and then install subversion in a random directory.


You will need and editor, for example Emacs. Get a Windows version for
MinGW from:

https://www.gnu.org/software/emacs/

To install it, simply unpack it in your MINGWPATH, you can now
execute the binary in 'MINGWPATH/bin'.


3. Additional Windows steps
===========================

You may need to edit /MINGWPATH/include/winsock2.h to change the size of the
sa_data field in the sockaddr structure from 14 to 22 ... this is because
some versions of Windows have changed the layout of this structure.
This modification may be needed to be able to correctly determine the
network interface details for your machine.


On Windows Vista and later, an additional problem has been reported
where 'make install' would sometimes fail because of permission
problems.  The problem is discussed here --

http://lists.gnu.org/archive/html/gnustep-dev/2010-06/msg00055.html

you may have to install the additional MinGW files, as explained
there.


4. Mount your MINGWPATH directory
=================================

With Emacs create a file called "fstab" in C:\MINGWPATH\msys\x.x\etc and add
a line like:

  C:\MINGWPATH  /mingw

Remember MINGWPATH is the path where you installed mingw (We assume you
install it at your C: drive, if not change it). "mingw" is the name to
refer to your MINGWPATH directory inside MSYS console, you can use any other
name, but remember it because we will need this later. We will refer to this
name as MOUNTDIR.


5. Launch the MSYS console
==========================

Launch the console at C:\MINGWPATH\msys\x.x\msys.bat (double click).


6. Installing gnustep-make
==========================

Get gnustep-make:

svn co http://svn.gna.org/svn/gnustep/tools/make/trunk make

Then install it (avoid warning about conftest.exe):

cd make
./configure
make
make install


7. Special recommendation
=========================

In next steps don't use "make -j", because can cause problems.


8. Installing libffi
====================

Download libffi-x.x.x.tar.gz from https://sourceware.org/libffi/.
Unpack it, compile and install:

cd libffi-x.x.x
./configure --prefix=/MOUNTDIR
make
make install
mv /MOUNTDIR/lib/libffi-x.x.x/include/* /MOUNTDIR/include/

(if you get a popup about contest.exe failing, just ignore it)
NB. The headers have to be moved manually because the package won't install
them in the right place.


9. Install ICU
==============

Download latest ICU from http://site.icu-project.org/ (zip package).
Unpack it, compile and install as fallow:

cd icu/source
./runConfigureICU --disable-release MinGW --prefix=/MOUNTDIR
make
make install


10. Install GNUtls
==================

Download the latest version from the official page (windows binary). Copy
this at your MINGWPATH directory and unpack it.


11. Install pkg-config
======================

The best option is install pkg-config lite from:

http://sourceforge.net/projects/pkgconfiglite/files/

Download latest version, unpack it an copy the files at corresponding
directories in your MINGWPATH directory.


12. Install xml2
================

There are available binary packages of xml, but all these don't provide an
m4 file to be used with pkg-config. And since gnustep-base use pkg-config to
detect xml we need install it from source. So download the latest version
from http://xmlsoft.org/ and install it:

cd libxml2-x.x.x
./configure --prefix=/MOUNTDIR
make
make install


13. Fix problem with mingwrt
============================

(I you are using mingw32-mingwrt-3.21.1 or above skip this step.
Run MinGW Installer to see what version are you using.)

Launch Emacs and open the file /MINGWPATH/include/unistd.h

And comment the line 95 (#include <parts/time.h>) and all the function
nanosleep (from line 104 to 117). Save the file.


14. Source GNUstep.sh
=====================

Probably you will need source the GNUstep script:

. /local/share/GNUstep/Makefiles/GNUstep.sh


15. Install gnnustep-base
=========================

Get gnustep-base:

svn co http://svn.gna.org/svn/gnustep/libs/base/trunk base

Then compile and install it:

cd base
./configure
make
make install


16. Install jpeg
================

Download the latest version from http://ijg.org/. Then compile and install it
as fallow:

cd jpeg-xx
autoheader
./configure --prefix=/MOUNTDIR
make
make install


17. Install libtiff
===================

Download latest version from http://www.libtiff.org/. Then compile and
install it:

cd tiff-x.x.x
./configure --prefix=/MOUNTDIR
make
make install


18. Install libpng
==================

Download latest version from http://libpng.org/pub/png/libpng.html.
Then compile and install it:

cd lpngXXX
cp scripts/pnglibconf.h.prebuild pnglibconf.h
cp scripts/makefile.msys makefile

Launch Emacs and edit the makefile to set prefix as "prefix=/MOUNTDIR", then:

make
make install


19. Install libungif
====================

From http://gnuwin32.sourceforge.net/ download

  libungif-4.1.4-1.exe

Execute it and install the package into your MINGWPATH directory.


20. Install libao
=================

Download libao from http://xiph.org/ao/. And install it:

cd libao-x.x.x
./cofigure --prefix=/MOUNTDIR
make
make install


21. Install Aspell
==================

Download the windows port http://aspell.net/win32/. And
install it in your MINGWPATH directory (directly in your MINGWPATH directory,
not under the Aspell directory).

Download also the dev package, unpack it and copy the libraries and headers
to the corresponding directories at your MINWGPATH directory.

Download also the installers for the dictionaries you want use, extract and
install them into your MINGWPATH directory (directly in your MINGWPATH
directory, not under the Aspell directory).

Now you need change the name of some libraries, go to directory MINGWPATH/lib
and change the name of these files:

aspell-15.def   ---->  aspell.def
aspell-15.lib   ---->  aspell.lib
libaspell-15-dll.lib  ---->  libaspell-dll.lib


22. Add path to icu libraries
=============================

FIXME: Why this is needed?

Edit the file /MINGWPATH/msys/etc/profile and add the path to ICU libs:

export PATH=$PATH:/MOUNTDIR/lib


23. Install gnustep-gui
=======================

Get gnustep-gui:

svn co http://svn.gna.org/svn/gnustep/libs/gui/trunk gui

Then compile and install it:

cd gui
./configure
make
make install


24. Install gnustep-back
========================

Get gnustep-back:

svn co http://svn.gna.org/svn/gnustep/libs/back/trunk back

Then compile and install it:

cd back
./configure
make
make install


25. Install gnustep-back with cairo graphics (optional but highly recommended)
==============================================================================

Download fallowing packages:

http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/cairo_1.10.2-2_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/cairo-dev_1.10.2-2_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libpng_1.4.3-1_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/freetype_2.4.2-1_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/freetype-dev_2.4.2-1_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/fontconfig_2.8.0-2_win32.zip
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/fontconfig-dev_2.8.0-2_win32.zip


Copy these packages at your MINGWPATH directory and unpack them. Now move some
headers:

mv /MOUNTDIR/include/cairo/* /MOUNTDIR/include/
mv /MOUNTDIR/include/freetype2/freetype/ /MOUNTDIR/include/

Now we need recompile gnustep-back to use cairo backend:

cd back
make distclean
./configure --enable-graphics=cairo --with-name=cairo LIBS=-lcairo
make
make install

Now set defaults to use this backend:

defaults write NSGlobalDomain GSBackend cairo


26. Install WinUXTheme (optional)
=================================

Get WinUXTheme:

svn co http://svn.gna.org/svn/gnustep/plugins/themes/WinUXTheme/ winuxtheme

Then compile and install it:

cd winuxtheme
make
make install

Set it:

defaults write NSGlobalDomain GSTheme WinUXTheme


27. Source the gnustep script when launch the console
=====================================================

Edit the file /MINGWPATH/msys/etc/x.x/profile and add this line to source the
gnustep script:

. /local/share/GNUstep/Makefiles/GNUstep.sh


28. Set up the spell chequer service
====================================

The spell chequer service need be configured. So we need launch it once
to configure it. Run the command:

/local/lib/GNUstep/Services/GSspell.service/GSspell.exe


29. Testing your gui installation
=================================

Get the examples:

svn co http://svn.gna.org/svn/gnustep/tests/examples/trunk/ examples

Go in a simple gui application (examples/gui a very good starting
point), compile and run it. :-). Ink and PowerPaint should work fine
on Windows, test these.

Additionally, you might want to compile and run Gorm or other GNUstep
applications.  Gorm (and hopefully other GNUstep applications too)
should compile and run out of the box.


Troubleshooting
---------------

Issues with updating:
Before attempting to update your GNUstep installation, be sure to stop/kill
all running GNUstep programs or services (i.e. gdomap, gdnc, gpbs) since
Windows cannot overwrite files that are currently in use.

Where we specify specific versions of packages to be used, we have
tested with those versions - later or earlier versions may work, but
may well not.  Generally earlier versions should be assumed not to
work.



B. HOW TO SHIP YOUR GNUSTEP APPLICATION TO WINDOWS USERS
--------------------------------------------------------

You probably want to ship your Windows application as a standalone
.zip file that Windows users can easily download and use.

We will explain what to do with an example: that of packaging
Gomoku.app.  We will first build the application (creating
Gomoku.app), then we'll add to to it all the GNUstep DLLs and
resources that are needed to run the application, and we'll end up
with a single directory, Gomoku.app, that contains a program
(Gomoku.exe) and a bunch of DLLs and various other resources required
to run the program.

The end user just needs to get this directory (from a .zip or .tgz
file, for example) and can double-click on Gomoku.exe to start the
program (no GNUstep installation required).


1. Build the application
========================

Build your application (Gomoku.app in this example) in your
MinGW/GNUstep environment.  Generally, this means getting the source
code and typing 'make' in it.  If you're trying to follow the
Gomoku.app example, the source code is here:

http://www.gnustep.it/nicola/Applications/Gomoku/index.html

Once you have built it, make sure you can run your application from
within mingw by using 'openapp', as in 'openapp ./Gomoku.app'.

2. Copy your application somewhere
==================================

Now take your built application and copy it somewhere -- we'll be
working on it!  Eg, I just copy it in my home directory.

cp -R /home/Nico/Gomoku-1.2.8/Gomoku.app /home/Nico/


3. Copy DLLs into your application
==================================

Now search for MinGW/GNUstep DLL files in /MOUNTDIR/bin, /MOUNTDIR/lib and
/local/bin, and copy them all into Gomoku.app:

cp $(find /MOUNTDIR/bin -name *.dll) /home/Nico/Gomoku.app/
cp $(find /MOUNTDIR/lib -name *.dll) /home/Nico/Gomoku.app/
cp $(find /local/bin -name *.dll) /home/Nico/Gomoku.app/


4. Copy config files into your application
==========================================

Now copy the "etc" directory in /MOUNTDIR to Gomoku.app:

cp -R /MOUNTDIR/etc /home/Nico/Gomoku.app/


5. Copy your GNUstep Library folder
===================================

Now copy all of the GNUstep resources into the application --

mkdir -p /home/Nicola/Gomoku.app/GNUstep/
cp -R /local/lib/GNUstep/* /home/Nico/Gomoku.app/GNUstep/

I put them all into Gomoku.app/GNUstep/, which means that later on
I'll set up the GNUstep.conf file to map GNUSTEP_*_LIBRARY to that
directory.


6. Copy key GNUstep binary programs
===================================

cp /local/bin/gpbs.exe /home/Nicola/Gomoku.app
cp /local/bin/gdnc.exe /home/Nicola/Gomoku.app
cp /local/bin/gdomap.exe /home/Nicola/Gomoku.app
cp /local/bin/make_services.exe /home/Nicola/Gomoku.app
cp /local/bin/defaults.exe /home/Nicola/Gomoku.app

I put them all into Gomoku.app, which means that later
on I'll set up the GNUstep.conf file to map GNUSTEP_*_TOOLS to that
directory.


7. Add a GNUstep.conf
=====================

You need to add a Gomoku.app/GNUstep.conf file to tell gnustep-base
where to find things inside Gomoku.app -- here is the one I use (which
matches the locations where I copied things in the previous steps) --

GNUSTEP_USER_CONFIG_FILE=.GNUstep.conf
GNUSTEP_USER_DIR=GNUstep
GNUSTEP_USER_DEFAULTS_DIR=GNUstep/Defaults

GNUSTEP_SYSTEM_APPS=./GNUstep/Apps
GNUSTEP_SYSTEM_ADMIN_APPS=./GNUstep/Apps
GNUSTEP_SYSTEM_TOOLS=./
GNUSTEP_SYSTEM_ADMIN_TOOLS=./
GNUSTEP_SYSTEM_LIBRARY=./GNUstep
GNUSTEP_SYSTEM_HEADERS=./GNUstep/Headers
GNUSTEP_SYSTEM_LIBRARIES=./GNUstep/Libraries
GNUSTEP_SYSTEM_DOC=./GNUstep/Documentation
GNUSTEP_SYSTEM_DOC_MAN=./GNUstep/Documentation/man
GNUSTEP_SYSTEM_DOC_INFO=./GNUstep/Documentation/info

GNUSTEP_NETWORK_APPS=./GNUstep/Apps
GNUSTEP_NETWORK_ADMIN_APPS=./GNUstep/Apps
GNUSTEP_NETWORK_TOOLS=./
GNUSTEP_NETWORK_ADMIN_TOOLS=./
GNUSTEP_NETWORK_LIBRARY=./GNUstep
GNUSTEP_NETWORK_HEADERS=./GNUstep/Headers
GNUSTEP_NETWORK_LIBRARIES=./GNUstep/Libraries
GNUSTEP_NETWORK_DOC=./GNUstep/Documentation
GNUSTEP_NETWORK_DOC_MAN=./GNUstep/Documentation/man
GNUSTEP_NETWORK_DOC_INFO=./GNUstep/Documentation/info

GNUSTEP_LOCAL_APPS=./GNUstep/Apps
GNUSTEP_LOCAL_ADMIN_APPS=./GNUstep/Apps
GNUSTEP_LOCAL_TOOLS=./
GNUSTEP_LOCAL_ADMIN_TOOLS=./
GNUSTEP_LOCAL_LIBRARY=./GNUstep
GNUSTEP_LOCAL_HEADERS=./GNUstep/Headers
GNUSTEP_LOCAL_LIBRARIES=./GNUstep/Libraries
GNUSTEP_LOCAL_DOC=./GNUstep/Documentation
GNUSTEP_LOCAL_DOC_MAN=./GNUstep/Documentation/man
GNUSTEP_LOCAL_DOC_INFO=./GNUstep/Documentation/info

So, just copy and paste this code into a GNUstep.conf file that you
put into /home/Nico/Gomoku.app/GNUstep.conf.


8. Add a GlobalDefaults.plist
=============================

You need to add a Gomoku.app/GlobalDefaults.plist file to tell GNUstep
the defaults you want use (the theme, backend, etc.), and save this file
with write/read permission only for the owner (chmod 600). For example:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml">
<plist version="0.9">
  <dict>
	<key>GSTheme</key>
	<string>WinUXTheme</string>
	<key>GSBackend</key>
	<string>cairo</string>
  </dict>
</plist>


8. Now the application should be working
========================================

At this stage, everything should be working "standalone".

By that we mean that if you give your Gomoku.app/ to a Windows user
(with no GNUstep installed on their machine), they should be able to
run it by just double-clicking on the Gomoku executable inside of the
Gomoku.app/ directory! :-)

Try it out and make sure that it works.


9. Cleanup
==========

If you look at your Gomoku.app/ directory, you will see that it is
really big.  We mass-copied stuff from the GNUstep/MinGW directories;
but generally, you want to make sure you remove anything that you
don't strictly need.  So go in there and remove anything that you
don't need.

First thing, you should remove the MSYS libraries, which we never use --

rm Gomoku.app/msys-1.0.dll
rm Gomoku.app/msysltdl-3.dll
rm Gomoku.app/libW11.dll
rm Gomoku.app/libperl.dll
rm Gomoku.app/librle3.dll

Then, remove any additional library that your application doesn't use;
for example, I removed --

rm Gomoku.app/Renaissance.dll
rm Gomoku.app/ProjectCenter.dll

Finally, remove Apps and other stuff that you might have copied from
the general GNUstep installation --

rm -Rf Gomoku.app/GNUstep/Apps
rm -Rf Gomoku.app/GNUstep/Frameworks/ProjectCenter.framework

Generally, you may want to build the whole stuff making sure you only
include what you strictly need.


10. Stripping
=============

The resulting directory might still be pretty big.  If you are trying
to distribute it over the internet, your users will probably
appreciate if you stripped it, removing symbols.  Just run 'strip'
on all the .exe and .dll files in your application.

strip $(find /home/Nico/Gomoku.app/ -name '*.exe')
strip $(find /home/Nico/Gomoku.app/ -name '*.dll')

That will reduce the size a lot.  If you're not distributing it over
the internet, you might be happy leaving the symbols in though.


11. Checking Licenses
====================

Finally, before deployment, you need to realize that you are shipping
a lot of GNUstep (and non-GNUstep) software with your application.

This is fine, just make sure you are aware of the licenses, and that
you comply with them.


PACKAGING/WINDOWS TODOS
-----------------------

The gdnc, gpbs processes are somehow a bit of a pain.  They are
automatically started when you start your application, but they are
not automatically stopped when you quit it.  This might have bad
consequences, eg, if you are using your application from a USB flash
disk, Windows doesn't let you unplug the USB disk while gdnc/gpbs are
running, because they are running from the disk!

Also, it's not clear what happens if you have two or three such
GNUstep apps downloaded from the web and you try to run them at the
same time.  What about gdomap etc ?

Cross Compiling GNUstep for MinGW from Cygwin
=============================================

If you wish to build on a native MinGW system (recommended),
please read README.MinGW instead.

MinGW is a collection of header files and import libraries that allow
one to use GCC and produce native Windows32 programs that do not rely
on any 3rd-party DLLs. GNUstep has only partially been ported to MinGW
so expect some problems when trying to compile. Also, there are still
subtle problems with running GNU tools on Windows, so any problems you
may encounter may just as easly have to do with the compilation tools
you are using as with GNUstep.

The base library is not completely ported to run on MinGW yet, but most
stuff works, including networking/distributed objects.
Probably background file handle operations (other than networking) and
advanced parts of NSTask code do not currently work.

Note for compiling with shared libraries (DLLs), it's a good idea to
remove the libobjc.a that comes with gcc (gcc -v for location) so that
it isn't accidentally found instead of the libobjc DLL that you will
compile below. Also note that, despite the statement in the GNUstep-HOWTO,
even if you have 3.x, you still need to install gnustep-objc as it properly
exports symbols for DLLs.

Note also that the //c construct for specifying paths with drives has
been depreciated. You'll need to use /cygwin/path or C: style paths now.

MinGW on Cygwin
---------------

Not recommended. This is a cross compilation solution. Using native
mingw/msys is simpler and less error prone.

Uses the Cygwin tools to help out with the configuration and compilation of
the libraries. It's always good to get the very latest version of
Cygwin and MinGW. These instructions were performed
with Cygwin DLL 1.3.9-1 and MingW gcc 2.95.3-6. If you have more
experience with MinGW than me, please help improve these instructions!

I assume you have installed Cygwin and MinGW, and dowloaded and
unpacked the GNUstep packages:

ffcall
gnustep-make
gnustep-objc
gnustep-base

See the GNUstep-HOWTO file for more information on where to get
various files. You need to build and install each package separately,
as described below.

1. First, start up a Cygwin BASH shell and make sure the MinGW tools
are in your path:

  export PATH=/c/mingw/bin:$PATH

(Put in whatever path you have for the mingw tools).

NB. Using MinGW-1.1 the header file winsock2.h needed to be slightly
updated for 2000 or XP.  The size of the sa_data field in struct sockaddr
had to be increased from 14 to 22.  If you don't do this before building
the gnustep base library, the gdomap tool will not correctly determine the
internet addresses of your machine.

2. Configure and compile gnustep-make.
The default location for GNUstep on Windows systems in C:/GNUstep.
To use another location you can use the --prefix argument to configure.
First, go to the 'gnustep-make' package and configure:

  cd gnustep-make
  ./configure --target=i386-mingw32

2a.  The configure script may not have recognised that you are running in
a cygwin environment ... so you may need to edit 'fixpath.sh' to set the
CYGWIN variable to 'yes' before you build and install the make package.

3. Now build the gnustep-make package. Occationally, the make that comes
with MinGW doesn't like the way GNUstep makefiles are setup (or perhaps
it's that MingW make doesn't work with bash), so you can try
using Cygwin's make instead (/usr/bin/make instead of just make).

  make target=i386-mingw32
  make target=i386-mingw32 install

4. Now source the GNUstep.sh file so the rest of the packages will
compile correctly:

  . C:/GNUstep/System/Library/Makefiles/GNUstep.sh

Also put this command in your shell startup script. Be sure to adjust
this path to match your real GNUstep root directory if you changed it
when configuring gnustep-make.

NOTE for WIN98 users: You should also define the environment variables
HOMEDRIVE and HOMEPATH, since these aren't defined normally.

5. Compile and install the ffcall package (Version 1.8b). It's
simply a C library so it requires no special tools other than the compiler.

LD=ld RANLIB=touch ./configure --target=i386-mingw32 \
	--prefix=`$GNUSTEP_MAKEFILES/fixpath.sh -u $GNUSTEP_SYSTEM_ROOT`

which installs the libraries in the GNUstep directory structure (There is
a script in ffcall-1.8d and higher that automatically configures ffcall
and installs, called compile-mingw). Then

  make				# NOTE: Might need to be 'make LN_S=cp'
  make install

6. Now you can compile the Objective-C runtime DLL, gnustep-objc (unless
you already have one installed):

  cd gnustep-objc
  make target=i386-mingw32 shared=yes
  make target=i386-mingw32 shared=yes install

Make sure to remove libobjc.a that comes with gcc, otherwise it will find that
one instead of the one we want. The libobjc library that comes with gcc-3.x
MAY work if you add some extra lines to the .def file, but I won't go into
that here. It's good just to use gnustep-objc.

7. Now we can configure and build the gnustep-base library.

  cd gnustep-base
  ./configure --target=i386-mingw32
  make target=i386-mingw32 shared=yes
  make target=i386-mingw32 shared=yes install

If you get tired of typing  "target=i386-mingw32" all the time, then before
you exec the GNUstep.sh script, just set the GNUSTEP_HOST:

  export GNUSTEP_HOST=i586-pc-mingw32
  . $GNUSTEP_SYSTEM_ROOT/Library/Makefiles/GNUstep.sh

Problems?
---------

[1] It's really important that all the libraries you link with GNUstep be
shared libraries. Even static libraries based on C (e.g. libtiff) will
prevent Objective-C modules from being loaded in Objective-C libraries.

[2] On Windows XP, at least, there are sometimes spaces in the path to the
user directory. The make program cannot deal with this.
Probably the best solution is to add a .GNUsteprc file in your home
directory with a line of the form -
GNUSTEP_USER_ROOT=/home/myname
setting your personal GNUstep root directory to be '/home/myname' ...
some path which does not contain spaces.

[3] Some users report needing to make gnustep libs like this (perhaps
when using Cygwin's gcc only):

export CC="gcc"
export CFLAGS="-mno-cygwin"
export CPPFLAGS="-mno-cygwin"
find . -name "*.lnk" -print -exec rm {} \;
make target=i386-mingw32 shared=yes LN_S="ln -s" \
  SHARED_LD_PREFLAGS="--driver-flags=\"-mno-cygwin -mdll -Wl,--enable-stdcall-fixup\" --target=i386-mingw32 --export-all-symbols"

[4] Compiling iconv (1.8):

(the part with the most problems - maybe you download it precompiled
but if you want to compile it - here is the guide) Make sure you are
compiling from a mapped drive (eg. d:) not from an UNC Path!!!!

./configure --target=i386-mingw32 --host=i386-mingw32 (ignore warnings here)
edit libtool and libcharset/libtool so that the CC variable reads
"gcc -mno-cygwin -mdll"
make
(After a while make breaks with an error in linking)
find . -name "*.lnk" -print -exec rm {} \;
make
(make breaks now in the src folder, but the DLL is already buildt,
that is what we need)
cp include/iconv.h $GNUSTEP_SYSTEM_ROOT/Headers
cp lib/.libs/libiconv-2.dll $GNUSTEP_SYSTEM_ROOT/Tools/libiconv-2.dll
cp lib/.libs/libiconv.dll.a $GNUSTEP_SYSTEM_ROOT/Libraries/libiconv.a

Good Sites for Pre-Compiled Binaries
------------------------------------

Many libraries, etc from:

<http://sourceforge.net/project/showfiles.php?group_id=7382>
<http://penguin.at0.net/~fredo/files/old/> (for libxml2, more?)
<http://sourceforge.net/project/showfiles.php?group_id=23617> (libtiff)

MingW guile from

<http://www.textsure.net/~ela/devel.html>.

also need guile from

<http://sourceforge.net/project/showfiles.php?group_id=7382>

for guile-config file.

Author
------

Adam Fedor <fedor@gnu.org>

@chapter GNUstep makefile package

Here is some introductory info to get you started:

@section What is the GNUstep makefile package?

The makefile package is a simple, powerful and extensible way to
write makefiles for a GNUstep-based project.  It allows the user to
write a project without having to deal with the complex issues
associated with configuration, building, installation, and packaging.
It also allows the user to easily create cross-compiled binaries.

@section Information

The file @samp{NEWS} has this packages feature history.

The files @samp{INSTALL} or @samp{GNUstep-HOWTO}
give instructions for installing the packages. Also see the @file{machines}
documentation and various machine specific READMEs in the Documentation
directory.

Files in the @samp{Documentation} directory have information on the
design of the Makefile system and how to write your own makefiles that
work with it.

@section License

The GNUstep libraries are covered under the GNU Lesser Public License.
This means you can use these libraries in any program (even non-free
programs). If you distribute the libraries along with your program,
you must make the improvements you have made
to the libraries freely available. You should read the COPYING.LIB file
for more information.

GNUstep tools, test programs, and other files are covered under the GNU
General Public License. The GNU GPL is a free software license, which
requires that all the released improved versions be free software as
well.  You should read the COPYING file for more information.

The GNUstep make package is licensed under the GNU GPL.

@section History

The GNUstep makefile package was designed by Scott Christley
and Ovidiu Predescu.

Flags for building shared libraries and bundles on several systems were
originally identified by Mircea Oancea @email{mircea@@pathcom.com}.

Richard Frith-Macdonald @email{richard@@brainstorm.co.uk} also
contributed with ideas.

Nicola Pero @email{nicola@@brainstorm.co.uk} rewrote much of the rule
procedures to increase the speed of the package by over a factor of 7.
He also rewrote much of the rest of the system to make it simpler and
more effective.

@section How can you help?

@itemize @bullet

@item
Give us feedback!  Tell us what you like; tell us what you think
could be better.  Send bug reports to @email{bug-gnustep@@gnu.org}.

@end itemize