* Documentation/README.MinGW: Mention Windows installer. Update links

* Documentation/gnustep-howto.texi: Some setup no longer needed.
* Documentation/gnustep.init: Don't add links - currently not
referenced correctly.
* Documentation/machines.texi: Add compilers section.


git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@20236 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Adam Fedor 2004-10-18 15:32:39 +00:00
parent ec2bd95164
commit f53278d735
6 changed files with 114 additions and 115 deletions

View file

@ -1,3 +1,11 @@
2004-10-18 Adam Fedor <fedor@gnu.org>
* Documentation/README.MinGW: Mention Windows installer. Update links
* Documentation/gnustep-howto.texi: Some setup no longer needed.
* Documentation/gnustep.init: Don't add links - currently not
referenced correctly.
* Documentation/machines.texi: Add compilers section.
2004-09-07 Adam Fedor <fedor@gnu.org>
* Version 1.10.0

View file

@ -20,41 +20,29 @@ 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 only recently ported to run on MinGW. While most
stuff works, including networking/distributed objects, there are probably
bits that have been overlooked or are untested as yet. The only *known*
areas of code not yet ported are the zlib, SSL and XML extensions.
The gui library is only partially ported to run under MinGW ... you can
play with it, but expect to have to work on porting the library rather
than developing user applications.
environment, please read README.Cygwin instead.
The gui library is only partially ported to run under MinGW. The look
and behavior may not be consistant.
PRELIMINARIES
-------------
Before we start, we need to get some preliminary Windows software -
a tool for fetching source code via CVS.
One way to vastly simplify installing GNUstep, is to use the Windows-based
GNUstep installer. Currently, this installer only installs the non-gui
portion of GNUstep. Get it from
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.
http://www.gnustep.org/resources/sources.html#windows
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 set to the unix option.
If you have already installed this, you can skip to the section
'Additional gui libraries '. Although you may want to read the rest of
the instructions for other helpful information.
Installing and setting up MINGW and MSYS
----------------------------------------
Next, download msys-1.08 or later from
Download msys-1.08 or later from
http://sourceforge.net/projects/mingw
and install it.
@ -119,12 +107,7 @@ libffcall (http://ftp.gnustep.org/pub/gnustep/lib)
GNUstep-objc (release, snapshot, or cvs dev-apps module)
GNUstep-base (snapshot, or cvs core module)
For gui ... GNUstep-back (snapshot, or cvs core module)
NB. Ensure that the GNUstep code you are attempting to use has a date
later than the date at the top of this document! The instructions do
not apply to earlier code.
For gui, GNUstep-gui and GNUstep-back (snapshot, or cvs core module)
Setting up the GNUstep make environment
---------------------------------------
@ -189,8 +172,7 @@ 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
http://ftp.gnustep.org/pub/gnustep/libs.
Ignore any other instructions for building this ...
@ -208,7 +190,7 @@ Now you can now build and install it simply by typing:
Additional libraries
Additional non-gui libraries
--------------------
There are some optional (but very strongly recommended) libraries you
@ -226,19 +208,14 @@ libiconv
cp lib/iconv.lib $GNUSTEP_SYSTEM_ROOT/Library/Libraries/libiconv.a
cp lib/iconv.dll $GNUSTEP_SYSTEM_ROOT/Tools/iconv.dll
libtiff, libjpeg, and zlib
Needed for image handling support in the GNUstep gui libary
zlib
(not required for GNUstep-base, though zlib can be used by the base library).
Get the binary packages from -
http://prdownloads.sourceforge.net/gnuwin32/tiff-3.5.7-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/tiff-3.5.7-bin.zip
http://prdownloads.sourceforge.net/gnuwin32/libjpeg-6b-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/libjpeg-6b-bin.zip
http://prdownloads.sourceforge.net/gnuwin32/zlib-1.1.4-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/zlib-1.1.4-bin.zip
Unpack and install
Unpack and install in the standard place, or:
the header (.h) files in $GNUSTEP_SYSTEM_ROOT/Library/Headers
the library (.lib) files in $GNUSTEP_SYSTEM_ROOT/Library/Libraries
the dll files in $GNUSTEP_SYSTEM_ROOT/Tools
@ -289,23 +266,44 @@ system resources).
Additional gui libraries
--------------------
These are additional libraries required or at least highly recommended when
installing the gui portion of GNUstep.
libtiff, libjpeg, zlib, libpng
Needed for image handling support in the GNUstep gui libary
(not required for GNUstep-base, though zlib can be used by the base library).
Get these binary packages (or later versions) from -
http://prdownloads.sourceforge.net/gnuwin32/tiff-3.5.7-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/tiff-3.5.7-bin.zip
http://prdownloads.sourceforge.net/gnuwin32/libjpeg-6b-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/libjpeg-6b-bin.zip
http://prdownloads.sourceforge.net/gnuwin32/zlib-1.1.4-lib.zip
http://prdownloads.sourceforge.net/gnuwin32/zlib-1.1.4-bin.zip
Unpack and install. You can put them in the standard locations, or also:
the header (.h) files in $GNUSTEP_SYSTEM_ROOT/Library/Headers
the library (.lib) files in $GNUSTEP_SYSTEM_ROOT/Library/Libraries
the dll files in $GNUSTEP_SYSTEM_ROOT/Tools
Building and installing GNUstep-gui
-----------------------------------
To build the gui, you need to have libtiff installed ...
Go to gnustep-gui (or from CVS into the core/gui directory), and type
make install
Building and installing GNUstep-back
------------------------------------
This software is PRE-ALPHA ... it is present in CVS for people who wish to
help porting the GNUstep backend to Windows!
This software is ALPHA ... please help porting the GNUstep backend to
Windows!
In the back directory, type
@ -313,8 +311,6 @@ In the back directory, type
Troubleshooting
---------------

View file

@ -322,36 +322,26 @@ source /usr/GNUstep/System/Library/Makefiles/GNUstep.csh
@node GNUstep Home, Time Zone, Environment Setup, Additional Installation
@section GNUstep Home
Set up your home GNUstep directory. This should be done automatically
if you don't do it. This is where user defaults are kept as well as
Your home GNUstep directory should be created automatically the first
time you use a GNUstep tool or application.
This is where user defaults are kept as well as
other user configuration files. User installed apps, libraries, etc
are also here (if the default user directory is used).
@example
cd
mkdir GNUstep
@end example
are also here (if the default user directory is used). By default this
is the directory @file{GNUstep} under your home directory, but you can change
this (see the gnustep-make installation documentation).
@node Time Zone, GNUstep deamons, GNUstep Home, Additional Installation
@section Time Zone
Next, set your local time zone. There are four ways to do this, pick
one (see
@file{$GNUSTEP_SYSTEM_ROOT/Library/Libraries/Resources/gnustep-bsae/NSTimeZones/zones} for
typical time zones):
In most cases, GNUstep should be able to determine your time zone, if
you have already set it up correctly when setting up your
computer. However, in some cases this might fail or the correct
information may not be available. You can set it manually using the
GNUstep defaults utility to set @kbd{Local Time Zone} to your local time
zone. Type something like @kbd{defaults write NSGlobalDomain "Local
Time Zone" GB}. Where @kbd{GB} is a time zone abbreviation.
@enumerate
@item Use the defaults utility to set ``Local Time Zone'' to your local
time zone (defaults is installed with GNUstep in the Tools directory). Type
something like ``defaults write NSGlobalDomain "Local Time Zone" GB''.
@item Set the @var{GNUSTEP_TZ} environment variable.
@item Create the file @file{$GNUSTEP_SYSTEM_ROOT/Library/Libraries/Resources/gnustep-base/NSTimeZones/localtime} with the name of the local time zone in it.
@item Set the @var{TZ} environment variable (this may conflict with other
software on your system though).
@end enumerate
See @file{$GNUSTEP_SYSTEM_ROOT/Library/Libraries/Resources/gnustep-bsae/NSTimeZones/zones} for typical time zones):
@node GNUstep deamons, , Time Zone, Additional Installation
@section GNUstep deamons
@ -384,8 +374,7 @@ fi
@node Tools and Applications, Machine Specific, Additional Installation, Top
@chapter Test Tools and Applications
Test programs for the base library are in @file{base/Testing}. Example
applications are located in the gstep-examples package. To make these,
Example applications are located in the gstep-examples package. To make these,
just uncompress and untar this package, cd to the appropriate
directory, and type make. You will need to install the GNUstep core libraries
first before doing this.

View file

@ -2,7 +2,7 @@ if (defined($ENV{'GNUSTEP_WEB_ROOT'})) {
open(TMPL,"<$ENV{'GNUSTEP_WEB_ROOT'}/secondary.html.template");
$tmpl=join("",<TMPL>);
close(TMPL);
($T2H_EXTRA_HEAD,$T2H_AFTER_BODY_OPEN,$T2H_PRE_BODY_CLOSE) =
($T2H_EXTRA_HEAD,$T2H_AFTER_BODY_OPEN,$T2H_PRE_BODY_CLOSE_BAD) =
($tmpl=~/<\/title>(.*)<\/head>.*<body>(.*<div id="main">).*(<\/div><\/div>.*)<\/body>/sm);
}
else {

View file

@ -3,8 +3,8 @@
@settitle Platform Compatibility
@ifclear HOWTO
@c Machine Specific, Darwin/ix86, , (DIR)
@node Machine Specific, Darwin/ix86, , (DIR)
@c Machine Specific, Compilers, , (DIR)
@node Machine Specific, Compilers, , (DIR)
@chapter Machines
@end ifclear
@ -17,7 +17,12 @@ and need someone to help with reporting problems and fixes.
Platforms marked @emph{Obsolete} are very old distributions. No one really
knows if GNUstep works on these although they may.
If you have compiled GNUstep on a specific machine, please send information
about what you needed and any special instructions needed to
GNUstep @email{bug-gnustep@@gnu.org}.
@menu
* Compilers::
* Darwin/ix86::
* Darwin/PowerPC::
* Debian/DEC-Alpha::
@ -49,6 +54,10 @@ knows if GNUstep works on these although they may.
* Yellowdog/PowerPC::
@end menu
@c -----------------------------------------
@node Compilers, Darwin/ix86, Machine Specific, Machine Specific
@section Compilers
A recommended compiler is listed for each machine, if known. You should try
to use the recommended compiler for compiling GNUstep, as GNUstep is quite
complex and tends provoke a lot of errors in some compilers. Even versions
@ -57,7 +66,7 @@ version of a compiler expecting it to be better than previous versions.
Compiler notes: If a recommended compiler is not listed, take note of the
following information before choosing the compiler you use.
@table @samp
@table @var
@item egcs or gcc < 2.95
Might work, but few people use these now.
@item gcc 2.95.x
@ -77,18 +86,15 @@ Pretty good. Recommended.
Recommended. Fixes some bugs relating to protocols as well as other
improvements.
@item gcc 3.4
No info yet.
Not recommended. There are several reports that GNUstep programs compiled
with this compiler will segfault when unarchiving data.
@end table
If you have compiled GNUstep on a specific machine, please send information
about what you needed and any special instructions needed to
GNUstep @email{bug-gnustep@@gnu.org}.
If your having mysterious trouble with a machine, try compiling GNUstep
without optimization. Particularly in the newer GCC compilers,
optimization can break some code. The easiest way to do this is when
configuring, @samp{CFLAGS="" ./configure}. Or when building,
@samp{make OPTFLAG=""}.
configuring, @kbd{CFLAGS="" ./configure}. Or when building,
@kbd{make OPTFLAG=""}.
Also if you manually upgraded gcc and/or make, we recommend reading the
documentation at @url{http://www.LinuxFromScratch.org} for tips on compiling
@ -96,12 +102,12 @@ and installing gcc and make. If you had GNUstep previously installed, make sure
you completely remove all of it, including installed init scripts.
@c -----------------------------------------
@node Darwin/ix86, Darwin/PowerPC, Machine Specific, Machine Specific
@node Darwin/ix86, Darwin/PowerPC, Compilers, Machine Specific
@section Darwin/ix86
Currently tested on Darwin 7.x
@table @samp
@table @var
@item Recommended compiler
gcc 3.3.2. Older versions will not compile on Darwin.
@ -124,7 +130,7 @@ directory for complete instructions.
Currently tested on Darwin 6.x, 7.x
@table @samp
@table @var
@item Recommended compiler
gcc 3.3.2. Older versions will not compile on Darwin.
@ -150,7 +156,7 @@ See also the MacOSX/PowerPC section
@node Debian/DEC-Alpha, Debian/i386, Darwin/PowerPC, Machine Specific
@section Debian/DEC-Alpha
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -166,7 +172,7 @@ None
@section Debian/i386
Tested on sid.
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -182,7 +188,7 @@ None
@section Debian/PowerPC
Tested on sid.
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -198,7 +204,7 @@ None
@section Debian/SPARC
Tested on sid.
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -214,7 +220,7 @@ None
@section FreeBSD 5.x
Tested on 5.0 and 5.1
@table @samp
@table @var
@item Recommended compiler
@item Extra libs needed
@ -231,7 +237,7 @@ are installed. See the GNUstep-HOWTO for list of libraries.
@node FreeBSD 4.x, FreeBSD 3.x, FreeBSD 5.x, Machine Specific
@section FreeBSD 4.x
@table @samp
@table @var
@item Recommended compiler
@item Extra libs needed
@ -250,7 +256,7 @@ For libxml2 2.4.24, make WITHOUT_PYTHON=YES
Compiles "out of the box" on FreeBSD 3.4.
@table @samp
@table @var
@item Recommended compiler
gcc 2.95.2
@ -292,7 +298,7 @@ flags to configure: @code{CFLAGS="-I/usr/local/include"} and
@node FreeBSD 2.x, Irix 6.5/MIPS, FreeBSD 3.x, Machine Specific
@section FreeBSD 2.x (@emph{Obsolete,Unstable})
@table @samp
@table @var
@item Recommended compiler
gcc 2.8.x
@ -319,7 +325,7 @@ You need to use gmake not make to compile the GNUstep packages.
@node Irix 6.5/MIPS, MacOSX/PowerPC, FreeBSD 2.x, Machine Specific
@section Irix 6.5/MIPS
@table @samp
@table @var
@item Recommended compiler
gcc 3.2.1
@ -347,7 +353,7 @@ No libffi-support: Use ffcall
Currently tested on MacOSX 10.2, 10.3
@table @samp
@table @var
@item Recommended compiler
Default.
@ -379,7 +385,7 @@ See also the Darwin/PowerPC section.
Tested with R2 RC2 (2004/03/04).
@table @samp
@table @var
@item Recommended compiler
gcc 3.x allthough earlier ones should work if you also install gnustep-objc
@ -395,7 +401,7 @@ Unknown.
@node NetBSD, Netwinder, MkLinux/PowerPC, Machine Specific
@section NetBSD
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -411,7 +417,7 @@ See the @url{README.NetBSD} file located in the gnustep-make package.
@node Netwinder, OpenBSD 3.x, NetBSD, Machine Specific
@section Netwinder (@emph{Unstable})
@table @samp
@table @var
@item Recommended compiler
Build #12 of the system.
@ -426,7 +432,7 @@ See @url{http://www.netwinder.org/~patrix}
@node OpenBSD 3.x, OSF/Alpha, Netwinder, Machine Specific
@section OpenBSD 3.x (@emph{Needs Testing})
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -444,7 +450,7 @@ Try reading the @url{README.NetBSD} which might work the same on OpenBSD.
Information is for Version 3.2C
@table @samp
@table @var
@item Recommended compiler
egcs-1.1.1/1.1.2, gcc-2.95
@ -465,7 +471,7 @@ ADDTIONAL_TOOL_LIBS in the GNUmakefile(.preamble).
@node RedHat/Intel, Slackware/Intel, OSF/Alpha, Machine Specific
@section RedHat/Intel
@table @samp
@table @var
@item Recommended compiler
Standard
@ -480,7 +486,7 @@ None
@node Slackware/Intel, Solaris 2.5.1/Sparc, RedHat/Intel, Machine Specific
@section Slackware/Intel
@table @samp
@table @var
@item Recommended compiler
Unknown.
@ -498,7 +504,7 @@ Unknown.
This configuration is no longer being tested, but it may still work.
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -515,7 +521,7 @@ See the Solaris 2.6 section for more instructions.
Tested on Solaris version 6, 7, and 8
@table @samp
@table @var
@item Recommended compiler
gcc 3.2.1 or greater
gcc 2.95.3. Version 2.95.2 has several bugs that GNUstep tickles.
@ -547,7 +553,7 @@ set to 'posix' not 'solaris'.
@section Solaris 2.7/Intel
@c Contact?: Sebastian Niesen <sniesen@niesen.net>
@table @samp
@table @var
@item Recommended compiler
Unknown.
@ -558,7 +564,7 @@ Unknown
Make sure there are no -g compiler flags (i.e. compiling with debug=yes
might be a problem). Unsure of correct bundle flags - You might need
to use the alternate flags listed in target.make, line 989. Also,
configuring gnustep-make with @samp{--disable-backend-bundle} might be
configuring gnustep-make with @option{--disable-backend-bundle} might be
necessary if you can't get bundles to work.
You will probable get a lot of text relocation
warnings, which probably can be ignored. See the other Solaris
@ -572,7 +578,7 @@ instructions above for more information.
GNUstep has been tested on version 6.2-6.4 of Suse
@table @samp
@table @var
@item Recommended compiler
Standard
@ -592,7 +598,7 @@ gdnc doesn't work. If you recompile the kernel then it starts working.
GNUstep has been tested on version 7.0, 8.0, 8.1, 8.2, 9.0, and 9.1 of Suse
@table @samp
@table @var
@item Recommended compiler
The default compiler that comes with Susu is fine. Also
gcc2.95.x, gcc3.0.x, 3.1 and 3.2 work, but 2.95 is faster.
@ -612,7 +618,7 @@ None.
GNUstep has been tested on version 7.0 of Suse/PPC
@table @samp
@table @var
@item Recommended compiler
Standard. gcc2.95.x, gcc3.0.x and gc3.1 work, but 2.95 is faster.
Compile with --threads-enabled (non-standard).
@ -629,7 +635,7 @@ None
@section Unixware-2.1.3/Intel
@c Contact?: Richard Frith-Macdonald <richard@brainstorm.co.uk>
@table @samp
@table @var
@item Recommended compiler
Unknown
@ -734,7 +740,7 @@ work.
@node Windows with CYGWIN, Windows with MinGW, Unixware-2.1.3/Intel, Machine Specific
@section Windows with CYGWIN (@emph{Needs Testing})
@table @samp
@table @var
@item Recommended compiler
gcc 3.3.1 or later (with libobjc and libjava (if using libffi))
@ -758,7 +764,7 @@ See @url{README.Cygwin} for information on compiling.
@node Windows with MinGW, Yellowdog/PowerPC, Windows with CYGWIN, Machine Specific
@section Windows with MinGW
@table @samp
@table @var
@item Recommended compiler
See below.
@ -776,7 +782,7 @@ Native GUI backend is alpha version.
@node Yellowdog/PowerPC, , Windows with MinGW, Machine Specific
@section Yellowdog/PowerPC
@table @samp
@table @var
@item Recommended compiler
Standard

View file

@ -38,7 +38,7 @@ endif
# This is the directory where the tools get installed. If you don't specify a
# directory they will get installed in the GNUstep Local Root.
ifneq ($($(GNUSTEP_INSTANCE)_INSTALL_DIR),)
TOOLD_INSTALL_DIR = $($(GNUSTEP_INSTANCE)_INSTALL_DIR)
TOOL_INSTALL_DIR = $($(GNUSTEP_INSTANCE)_INSTALL_DIR)
endif
ifeq ($(TOOL_INSTALL_DIR),)