gnustep/tools-make
0
0
Fork 0
mirror of https://github.com/gnustep/tools-make.git synced 2025-04-22 22:00:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

un as daemon under windoze.

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@13166 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Richard Frith-Macdonald 2002-03-20 11:02:23 +00:00
parent d7f8cd457b
commit 0324f75aca
1 changed files with 260 additions and 234 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

494
Documentation/README.MinGW
View file

@ -1,234 +1,260 @@
Date: 15-March-2002
Author: Richard Frith-Macdonald <rfm@gnu.org>
PURPOSE
-------
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).
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.
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.
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.
PRELIMINARIES
-------------
Before we start, we need to get some preliminary windoze software -
a tool for fetching source code via CVS.
If you don't want to use windows tools for this, you can get the
latest cygwin distribution and use the cvs client in that. The following is
for people who don't want to download all that cygwin stuff.
To get stuff from CVS you can download and install WinCVS ... which
you can find at http://sourceforge.net/projects/cvsgui You will need
to be a system administrator on your machine to install this software.
You should be able to use it without changing/setting any special
configuration options.
Installing and setting up MINGW and MSYS
----------------------------------------
Next, download msys-1.06 or later from
http://sourceforge.net/project/mingw
and install it.
Next, download MinGW-1.1 or later from
http://sourceforge.net/project/mingw
and extract this into c:/msys/version-number/mingw
This will unpack the mingw source tree within the msys hierarchy.
Unpacking mingw into the correct location within msys will ensure that the
path set up in /etc/profile in msys picks up the mingw tools too.
Remove the mingw make.exe file - mingw make is not good.
Rename the msys gmake.exe to make.exe, so we will use this make program.
It's a good idea to remove the libobjc.a and include/objc header that come
with gcc (gcc -v for location) so that they are not accidentally found
instead of the libobjc DLL that you will compile below.
Now you can double click on the c:/msys/version-number/bin/sh program to
open a window containing a shell.
In the shell window, type '. /etc/profile' to set up your path.
You may also want to set the HOMEDRIVE and HOMEPATH environment variables
to point to the home directory you wish to work from (though the defaults
may be ok for you).
NB. This home directory for building software must *not* contain spaces.
From this window we can now start building things.
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. However, since MinGW support
is currently evolving, we recommend that you get the latest snapshot
or code from CVS.
You need things in the following order:
GNUstep-make (release, snapshot, or cvs core module)
libffcall (http://ftp.gnustep.org/pub/gnustep/lib)
GNUstep-libobjc (release, snapshot, or cvs dev-apps module)
GNUstep-base (release, snapshot, or cvs core module)
Setting up the GNUstep make environment
---------------------------------------
In the GNUstep-make (core/make) package, do 'configure
--prefix=C:/GNUstep' You can of course use a different prefix to
install the GNUstep system in an alternative location, but it is
important that the path you use is a full windows style path with a
drive letter and colon at the start of it. This is because, while the
msys shell and other tools automatically map unix style paths to
windows paths, the mingw compiler does not!
IMPORTANT: The msys tools all handle unix style paths and map them to
windows style paths internally. The mingw tools only handle windows
style paths. In particular this means that where absolute paths are
given for commands within makefiles, and where paths for headers and
libraries are supplied to the compiler, these paths must be in windows
format, not unix format!!! The big place where things go wrong is
with configure. The configure script may use the msys shell and other
tools to locate binaries etc, and the msys tools will supply those
locations as unix style paths. If the configure script then causes
those paths to be built in to makefiles, the make process is likely to
fall over.
Now you can type 'make install' to build and install the make package.
Once this is done, type '. GNUstep.sh' to set up your GNUstep
environment. The environment for building software is now completely
set up, but for ease of use later, you might set up a script to be
used to set up any new shell windows you create. Something like this:
. /etc/profile
export HOMEDRIVE=C:
export HOMEPATH=/home/myname
export GNUSTEP_SYSTEM_DIR=C:/GNUstep/System
. $GNUSTEP_SYSTEM_DIR/Makefiles/GNUstep.sh
Building and installing FFCALL
------------------------------
The next priority is to get the ffcall library built and installed.
You should get the latest ffcall archive from
http://ftp.gnustep.org/pub/gnustep/libs. Currently this is
ffcall-1.8d.tar.gz
Ignore any other instructions for builting this ...
First, rename the msys/version-number/bin/ln.exe file ... this
program creates 'symbolic links' using windows 'shortcuts' ... but
some tools like the compiler won't follow them - so renaming this
program forces configure scripts to use the 'cp' program instead. If
you don't do this, the configure scripts for ffcall will produce
makefiles which won't work properly!
Next, in the shell window in which you have set up your GNUstep
environment, type
RANLIB=touch ./configure --prefix=`$GNUSTEP_MAKEFILES/fixpath.sh -u $GNUSTEP_SYSTEM_ROOT`
We use 'touch' as a substitute for 'ranlib', as windows does not have
(and does not need) ranlib. We provided the installation prefix as a
unix style pathname, since the libtool scripts barf on windows style
paths.
Having configured the ffcall library, you can now build and install
it simply by typing:
make install
Finally, rename the ln.exe program back into place.
Building and installing libobjc
-------------------------------
Despite the statement in the GNUstep-HOWTO, even if you have a 3.x
compiler, you still need to install gnustep-objc as it properly
exports symbols for DLLs.
Go to gnustep-objc (or from CVS, into dev-apps/libobjc), and type
make install
This should build and install the ObjectiveC runtime and headers for you.
Optional libraries
------------------
There are some optional (but very strongly recommended) libraries you
can install to make GNUstep work better.
libiconv
Needed for multilingual character support (unicode etc)
Get the binary package from
http://www.fh-frankfurt.de/~igor/projects/libxml
Unpack this and
cp iconv.h $GNUSTEP_SYSTEM_ROOT/Headers
cp iconv.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32/libiconv.a
cp iconv.dll $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32/iconv.dll
libxml2
Needed for XML parsing support, for MacOS-X compatible
property lists, and for documentation processing.
NB. at the time of writing, XML support in GNUstep base has *not*
been ported to windows - but when it is, you will need this package.
Get the binary package from
http://www.fh-frankfurt.de/~igor/projects/libxml
Unpack this and
tar -cf - libxml | (cd $GNUSTEP_SYSTEM_ROOT/Headers; tar -xvf -)
cp libxml2.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32/libxml2.a
cp libxml2.dll $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32
openssl
Needed for the SSL bundle, providing HTTPS support for NSURL.
NB. at the time of writing, SSL support in GNUstep base has *not*
been ported to windows - but when it is, you will need this package.
Get the binary package from
http://www.kix.or.jp/~fujino/openssl
Unpack this and
tar -cf - openssl | (cd $GNUSTEP_SYSTEM_ROOT/Headers; tar -xvf -)
cp *.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32
cp *.dll *.exe $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32
Building and installing GNUstep-base
------------------------------------
Go gnustep-base (or from CVS into the core/base directory), 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 (along with some
system resources).
Date: 15-March-2002
Author: Richard Frith-Macdonald <rfm@gnu.org>
PURPOSE
-------
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).
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.
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.
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.
PRELIMINARIES
-------------
Before we start, we need to get some preliminary windoze software -
a tool for fetching source code via CVS.
If you don't want to use windows tools for this, you can get the
latest cygwin distribution and use the cvs client in that. The following is
for people who don't want to download all that cygwin stuff.
To get stuff from CVS you can download and install WinCVS ... which
you can find at http://sourceforge.net/projects/cvsgui You will need
to be a system administrator on your machine to install this software.
You should be able to use it without changing/setting any special
configuration options. The one thing to remember is that the checkbox
to select whether to use unix line terminators instead of windows/DOS
line terminators should be se to the unix option.
Installing and setting up MINGW and MSYS
----------------------------------------
Next, download msys-1.06 or later from
http://sourceforge.net/project/mingw
and install it.
Next, download MinGW-1.1 or later from
http://sourceforge.net/project/mingw
and extract this into c:/msys/version-number/mingw
This will unpack the mingw source tree within the msys hierarchy.
Unpacking mingw into the correct location within msys will ensure that the
path set up in /etc/profile in msys picks up the mingw tools too.
Remove the mingw make.exe file - mingw make is not good.
Rename the msys gmake.exe to make.exe, so we will use this make program.
It's a good idea to remove the libobjc.a and include/objc header that come
with gcc (gcc -v for location) so that they are not accidentally found
instead of the libobjc DLL that you will compile below.
Now you can double click on the c:/msys/version-number/bin/sh program to
open a window containing a shell.
In the shell window, type '. /etc/profile' to set up your path.
You may also want to set the HOMEDRIVE and HOMEPATH environment variables
to point to the home directory you wish to work from (though the defaults
may be ok for you).
NB. This home directory for building software must *not* contain spaces.
(aside - MSYS uses the unix-style HOME environment variable, but windows
programs, including GNUstep programs under windows, use the HOMEDRIVE and
HOMEPATH environment variables to build a windows-style path for the home
directory. eg. if HOMEDRIVE is C: and HOMEPATH is \MyHome then the path
to the home directory is C:\MyHome).
From this window we can now start building things.
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. However, since MinGW support
is currently evolving, we recommend that you get the latest snapshot
or code from CVS.
You need things in the following order:
GNUstep-make (release, snapshot, or cvs core module)
libffcall (http://ftp.gnustep.org/pub/gnustep/lib)
GNUstep-libobjc (release, snapshot, or cvs dev-apps module)
GNUstep-base (release, snapshot, or cvs core module)
Setting up the GNUstep make environment
---------------------------------------
In the GNUstep-make (core/make) package, do 'configure
--prefix=C:/GNUstep' You can of course use a different prefix to
install the GNUstep system in an alternative location, but it is
important that the path you use is a full windows style path with a
drive letter and colon at the start of it. This is because, while the
msys shell and other tools automatically map unix style paths to
windows paths, the mingw compiler does not!
IMPORTANT: The msys tools all handle unix style paths and map them to
windows style paths internally. The mingw tools only handle windows
style paths. In particular this means that where absolute paths are
given for commands within makefiles, and where paths for headers and
libraries are supplied to the compiler, these paths must be in windows
format, not unix format!!! The big place where things go wrong is
with configure. The configure script may use the msys shell and other
tools to locate binaries etc, and the msys tools will supply those
locations as unix style paths. If the configure script then causes
those paths to be built in to makefiles, the make process is likely to
fall over.
Now you can type 'make install' to build and install the make package.
Once this is done, type '. GNUstep.sh' to set up your GNUstep
environment. The environment for building software is now completely
set up, but for ease of use later, you might set up a script to be
used to set up any new shell windows you create. Something like this:
. /etc/profile
export HOMEDRIVE=C:
export HOMEPATH=/home/myname
export GNUSTEP_SYSTEM_DIR=C:/GNUstep/System
. $GNUSTEP_SYSTEM_DIR/Makefiles/GNUstep.sh
Building and installing FFCALL
------------------------------
The next priority is to get the ffcall library built and installed.
You should get the latest ffcall archive from
http://ftp.gnustep.org/pub/gnustep/libs. Currently this is
ffcall-1.8d.tar.gz
Ignore any other instructions for builting this ...
First, rename the msys/version-number/bin/ln.exe file ... this
program creates 'symbolic links' using windows 'shortcuts' ... but
some tools like the compiler won't follow them - so renaming this
program forces configure scripts to use the 'cp' program instead. If
you don't do this, the configure scripts for ffcall will produce
makefiles which won't work properly!
Next, in the shell window in which you have set up your GNUstep
environment, type
RANLIB=touch ./configure --prefix=`$GNUSTEP_MAKEFILES/fixpath.sh -u $GNUSTEP_SYSTEM_ROOT`
We use 'touch' as a substitute for 'ranlib', as windows does not have
(and does not need) ranlib. We provided the installation prefix as a
unix style pathname, since the libtool scripts barf on windows style
paths.
Having configured the ffcall library, you can now build and install
it simply by typing:
make install
Finally, rename the ln.exe program back into place.
Building and installing libobjc
-------------------------------
Despite the statement in the GNUstep-HOWTO, even if you have a 3.x
compiler, you still need to install gnustep-objc as it properly
exports symbols for DLLs.
Go to gnustep-objc (or from CVS, into dev-apps/libobjc), and type
make install
This should build and install the ObjectiveC runtime and headers for you.
Optional libraries
------------------
There are some optional (but very strongly recommended) libraries you
can install to make GNUstep work better.
libiconv
Needed for multilingual character support (unicode etc)
Get the binary package from
http://www.fh-frankfurt.de/~igor/projects/libxml
Unpack this and
cp iconv.h $GNUSTEP_SYSTEM_ROOT/Headers
cp iconv.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32/libiconv.a
cp iconv.dll $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32/iconv.dll
libxml2
Needed for XML parsing support, for MacOS-X compatible
property lists, and for documentation processing.
NB. at the time of writing, XML support in GNUstep base has *not*
been ported to windows - but when it is, you will need this package.
Get the binary package from
http://www.fh-frankfurt.de/~igor/projects/libxml
Unpack this and
tar -cf - libxml | (cd $GNUSTEP_SYSTEM_ROOT/Headers; tar -xvf -)
cp libxml2.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32/libxml2.a
cp libxml2.dll $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32
openssl
Needed for the SSL bundle, providing HTTPS support for NSURL.
NB. at the time of writing, SSL support in GNUstep base has *not*
been ported to windows - but when it is, you will need this package.
Get the binary package from
http://www.kix.or.jp/~fujino/openssl
Unpack this and
tar -cf - openssl | (cd $GNUSTEP_SYSTEM_ROOT/Headers; tar -xvf -)
cp *.lib $GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32
cp *.dll *.exe $GNUSTEP_SYSTEM_ROOT/Tools/ix86/mingw32
Building and installing GNUstep-base
------------------------------------
Go gnustep-base (or from CVS into the core/base directory), 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 (along with some
system resources).
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.