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

Version 1.9.2

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@19491 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Adam Fedor 2004-06-10 15:07:36 +00:00
parent 4dac07b5be
commit 12f3667aea
13 changed files with 355 additions and 252 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
ANNOUNCE
View file

@ -1,33 +1,31 @@
Announcement
************
The GNUstep Makefile Package version 1.9.1 is now available.
The GNUstep Makefile Package version 1.9.2 is now available.
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.
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.
Changes in version `1.9.1'
Changes in version `1.9.2'
==========================
* Remove `--disable-import' option
* Application and Bundles use the latest convention on Apple.
* README.Darwin for darwin/MacOSX install
* Framework version and naming clarified.
* Improve/Simplify dependency checking when making docs
Obtaining gnustep-make
======================
You can get the gstep-make-1.9.1.tar.gz distribution file at
You can get the gstep-make-1.9.2.tar.gz distribution file at
<ftp://ftp.gnustep.org/pub/gnustep/core>
Please log bug reports on the GNUstep project page
<http://savannah.gnu.org/support/?group=gnustep> or send bug reports to
<http://savannah.gnu.org/bugs/?group=gnustep> or send bug reports to
<bug-gnustep@gnu.org>.

7
ChangeLog
View file

@ -1,3 +1,10 @@
2004-06-09 Adam Fedor <fedor@gnu.org>
* Version 1.9.2
* Documentation/GNUmakefile: Include ../Version
* Documentation/README.Cygwin: minor updates.
* Documentation/gnustep-howto.texi, Documentation/machines.texi: Update
2004-06-05 Adam Fedor <fedor@gnu.org>
* ld_lib_path.[c]sh: Allow seting of GNUstep framework location on

2
Documentation/GNUmakefile
View file

@ -130,6 +130,8 @@ MAN7_PAGES = GNUstep.7
include $(GNUSTEP_MAKEFILES)/documentation.make
include ../Version
GNUSTEP_TEXI2HTML_FLAGS += -init_file gnustep.init
# Typing 'make regenerate' should build all, then install the files

6
Documentation/README.Cygwin
View file

@ -20,8 +20,10 @@ 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.
Generally Cygwin port of GNUstep has a lot of issues and therefore is not
suitable for end-users yet but only for [experienced] programmers.
Several people have reported that GNUstep installation on Cygwin works
fine, but as always, a slightly different Window's setup can cause
unforseen problems. Yo should be relatively confident at working with
Cygwin before attempting to install GNUstep.
ADDITIONAL COMMENTS
-------------------

12
Documentation/gnustep-howto.texi
View file

@ -109,6 +109,9 @@ The libxml library (Version 2) is used to translate some of the
documentation for GNUstep and to provide suport for MacOS-X compatible
XML-based property-lists. It is recommended but not currently required.
@item libxslt (OPTIONAL)
Stylesheet support for use with XML.
@item openssl (OPTIONAL)
The openssl library is used to provide support for https connections by
the NSURL and HSURLHandle classes. This functionality is
@ -140,7 +143,7 @@ The GUI library uses this for the sound server
@item freetype2 (RECOMMENDED, REQUIRED for art backend)
This is used for font information
@item libart_lgpl2 (REQUIRED for are backend only)
@item libart_lgpl2 (REQUIRED for art backend only)
Drawing library for the art backend.
@item WindowMaker (Version >= 0.62) (OPTIONAL)
@ -186,10 +189,11 @@ Get the following individual packages:
See @url{http://www.gnustep.org} for information on where to get these
packages.
Make sure you install all the previously mentioned libraries first
before configuring and building GNUstep.
Make sure you install (if necessary) all the previously mentioned
libraries first before configuring and building GNUstep.
You should be able to install these packages as root.
You should install these packages as root (read special note for the
gnustep-base library, below, if you cannot do this).
For installation on specific systems, read the machine specific
instructions at the end of this document or appropriate README files in

22
Documentation/machines.texi
View file

@ -12,6 +12,10 @@ Below is a list of machines that people have attempted to compile
GNUstep on. GNUstep compiles with little or no trouble on many of the
more popular operating systems. Some machines marked with
@emph{Unstable} may have some trouble or may not work at all.
Platforms marked @emph{Needs Testing} are not actively tested by developers
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.
@menu
* Darwin/ix86::
@ -72,6 +76,8 @@ Pretty good. Recommended.
@item gcc 3.3.x
Recommended. Fixes some bugs relating to protocols as well as other
improvements.
@item gcc 3.4
No info yet.
@end table
If you have compiled GNUstep on a specific machine, please send information
@ -289,7 +295,7 @@ flags to configure: @code{CFLAGS="-I/usr/local/include"} and
@c -----------------------------------------
@node FreeBSD 2.x, Irix 6.5/MIPS, FreeBSD 3.x, Machine Specific
@section FreeBSD 2.x (@emph{Unstable!})
@section FreeBSD 2.x (@emph{Obsolete,Unstable})
@table @samp
@item Recommended compiler
@ -361,11 +367,11 @@ exist, but they may not be up-to-date. Try:
@example
cd make
./configure --with-library-combo=apple-apple-apple
make install debug=yes
make install
cd ../base
./configure --with-xml-prefix=/usr --disable-xmltest
make install debug=yes
make debug=yes install
@end example
@end table
@ -408,7 +414,7 @@ See the @url{README.NetBSD} file located in the gnustep-make package.
@c -----------------------------------------
@node Netwinder, OpenBSD 3.x, NetBSD, Machine Specific
@section Netwinder (@emph{Unstable!})
@section Netwinder (@emph{Unstable})
@table @samp
@item Recommended compiler
@ -423,7 +429,7 @@ See @url{http://www.netwinder.org/~patrix}
@c -----------------------------------------
@node OpenBSD 3.x, OSF/Alpha, Netwinder, Machine Specific
@section OpenBSD 3.x (@emph{Unstable!})
@section OpenBSD 3.x (@emph{Needs Testing})
@table @samp
@item Recommended compiler
@ -438,7 +444,7 @@ Try reading the @url{README.NetBSD} which might work the same on OpenBSD.
@c -----------------------------------------
@node OSF/Alpha, RedHat/Intel, OpenBSD 3.x, Machine Specific
@section OSF Alpha (@emph{Unstable!})
@section OSF Alpha (@emph{Unstable})
@c Contact: suzukis@file.phys.tohoku.ac.jp
Information is for Version 3.2C
@ -732,7 +738,7 @@ work.
@c -----------------------------------------
@node Windows with CYGWIN, Windows with MinGW, Unixware-2.1.3/Intel, Machine Specific
@section Windows with CYGWIN (@emph{Unstable!})
@section Windows with CYGWIN (@emph{Needs Testing})
@table @samp
@item Recommended compiler
@ -756,7 +762,7 @@ See @url{README.Cygwin} for information on compiling.
@c -----------------------------------------
@node Windows with MinGW, Yellowdog/PowerPC, Windows with CYGWIN, Machine Specific
@section Windows with MinGW (@emph{Unstable! As always...})
@section Windows with MinGW
@table @samp
@item Recommended compiler

1
Documentation/news.texi
View file

@ -13,6 +13,7 @@ The currently released version is @samp{@value{GNUSTEP-MAKE-VERSION}}.
@itemize @bullet
@item Application and Bundles use the latest convention on Apple.
@item Improve/Simplify dependency checking when making docs
@end itemize
@ifclear ANNOUNCE-ONLY

148
FAQ
View file

@ -1,7 +1,7 @@
GNUstep Frequently Asked Questions with Answers
***********************************************
Last updated 27 February 2004. Please send corrections to
Last updated 9 June 2004. Please send corrections to
<gnustep-maintainer@gnu.org>. Also look at the user FAQ for more user
oriented questions.
@ -11,7 +11,7 @@ Compatibility
Is it easy to port OPENSTEP programs to GNUstep?
------------------------------------------------
It is probably easy for simple programs. There are some portability
It is probably easy for simple programs. There are some portability
tools to make this easier, or rewrite the Makefiles yourself. You will
also have to translate the NIB files (if there are any) to GNUstep
model files using the nib2gmodel program (from
@ -20,7 +20,7 @@ model files using the nib2gmodel program (from
How about porting between Cocoa and GNUstep?
--------------------------------------------
It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is
It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is
constantly changing, much faster than GNUstep could hope to keep up.
They have added extensions and new classes that aren't available in
GNUstep yet. Plus there are some other issues. If you start with Cocoa:
@ -42,7 +42,7 @@ GNUstep yet. Plus there are some other issues. If you start with Cocoa:
Tools for porting
-----------------
While the programming interface should be almost transparent between
While the programming interface should be almost transparent between
systems (expect for the unimplemented parts, of course), there are a
variety of other files and tools that are necessary for porting
programs.
@ -72,10 +72,11 @@ programs.
A portable scripting environment that lets your do scripting in
almost any language you like.
Can I transfer archived data from GNUstep to Cocoa?
---------------------------------------------------
Apple's archiving format is proprietary and not documented, so this
Apple's archiving format is proprietary and not documented, so this
poses a problem for anyone wanting to implement compatibility with it.
However, even if we reverse engineered the format, there are enough
differences between the class and ivar layouts to make this sort of
@ -95,13 +96,13 @@ make it easier for other people to do the same thing.
Does distributed objects work between GNUstep and Cocoa?
--------------------------------------------------------
See the answer to the previous question (on archive compatibility)
for why this won't work either.
See the answer to the previous question (on archive compatibility) for
why this won't work either.
Is there an Interface Builder for GNUstep?
------------------------------------------
There is an Interface Builder for GNUstep called Gorm, but it is in
There is an Interface Builder for GNUstep called Gorm, but it is in
alpha release, so it may not work perfectly. You can download it from
the ftp site or via http. The Project Manager ProjectCenter is also
available.
@ -109,8 +110,8 @@ available.
Can I use my original NIB files?
--------------------------------
No - NeXT/Apple never documented their nib format, so GNUstep
supports both the 'gmodel' format (which stores information as text
No - NeXT/Apple never documented their nib format, so GNUstep supports
both the 'gmodel' format (which stores information as text
(property-lists) and can therefore be edited 'by hand') and binary
archive format (which can be edited by Gorm). There IS a conversion
tool called nib2gmodel that can be compiled under OPENSTEP to convert
@ -119,31 +120,30 @@ nib files to GNUstep gmodel files.
Can one use the hybrid "Objective-C++"
--------------------------------------
No. at present the GNU compiler (gcc) does not support
"Objective-C++". Apple is interested in adding back their implementation
to gcc and is slowly adding parts of it to the mainline gcc
implementation.
No. at present the GNU compiler (gcc) does not support "Objective-C++".
Apple is interested in adding back their implementation to gcc and is
slowly adding parts of it to the mainline gcc implementation.
Is there a plan to support the Java/YellowBox Bindings?
-------------------------------------------------------
Yes. The GNustep Java library/bridge called JIGS is available now.
JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically
wrap Objective-C libraries based on GNUstep, making them accessible
directly to the Java programmer as if they were Java libraries. As a
side effect, it is also possible to use the whole engine in the reverse
way: JIGS provides a high level API to allow Objective-C programmers to
start java virtual machines inside GNUstep Objective-C code and access
java objects in the java virtual machine transparently, as if they were
objective-C objects.
Yes. The GNustep Java library/bridge called JIGS is available now. JIGS
is a free (LGPL) Java Interface for GNUstep; it can automatically wrap
Objective-C libraries based on GNUstep, making them accessible directly
to the Java programmer as if they were Java libraries. As a side effect,
it is also possible to use the whole engine in the reverse way: JIGS
provides a high level API to allow Objective-C programmers to start java
virtual machines inside GNUstep Objective-C code and access java objects
in the java virtual machine transparently, as if they were objective-C
objects.
What if I compile GNUstep under OPENSTEP/MacOS X?
-------------------------------------------------
GNUstep uses the X-windows display postscript extension. The
interface to that is not the same as the interface to the
OPENSTEP/MacOS-X windows server. While someone could write a backend
library to provide the interface, nobody has bothered to date.
GNUstep uses the X-windows display postscript extension. The interface
to that is not the same as the interface to the OPENSTEP/MacOS-X
windows server. While someone could write a backend library to provide
the interface, nobody has bothered to date.
You should, however, be able to use a GNUstep program with an X11
server running on MacOSX.
@ -151,8 +151,8 @@ server running on MacOSX.
Is the Objective C API for GTK related?
---------------------------------------
No. GNUstep applications provide their GUI via the OpenStep API,
which provides fully object-oriented access to GUI manipulation.
No. GNUstep applications provide their GUI via the OpenStep API, which
provides fully object-oriented access to GUI manipulation.
The object-oriented nature of the libraries and language make it
much easier for new users to create their own subclasses rather than
@ -161,7 +161,7 @@ simply using the supplied widgets as in other frameworks.
How about implementing parts of the Application Kit with GTK?
-------------------------------------------------------------
Yes and No - The GNUstep architecture provides a single,
Yes and No - The GNUstep architecture provides a single,
platform-independent, API for handling all aspects of GUI interaction
(implemented in the gstep-gui library), with a backend architecture
that permits you to have different display models (display postscript,
@ -183,9 +183,9 @@ Compiling and Developing
How can I get started programming?
----------------------------------
Good question. Read the tutorials at the GNUstep web site. Also
look at Apple's documentation (pointers in the Resources section on the
GNUstep web site.)
Good question. Read the tutorials at the GNUstep web site. Also look at
Apple's documentation (pointers in the Resources section on the GNUstep
web site.)
How can I help with GNUstep?
----------------------------
@ -226,9 +226,9 @@ the Apple documentation or any other copyrighted documentation.
Helping develop GNUstep
-----------------------
There is plenty of unimplemented stuff in the gui library and
backend libraries that volunteers can work on - just browse through the
code and see if it conforms to the documentation.
There is plenty of unimplemented stuff in the gui library and backend
libraries that volunteers can work on - just browse through the code
and see if it conforms to the documentation.
Specific tasks are noted in the developers section on the GNUstep
website.
@ -239,7 +239,7 @@ documentation for it :-)
Helping document GNUstep
------------------------
All class documentation is written directly in the source code itself
All class documentation is written directly in the source code itself
and translated using the autogsdoc program. See the source code and
documentation for autogsdoc for information on documenting the classes.
@ -262,10 +262,10 @@ Software Foundation.
How do I update the task list?
------------------------------
The task list (<http://savannah.gnu.org/pm/?group_id=99>) is
supposed to tell people what jobs are waiting to be done. Feel free to
add to it or update the tasks that are there (you need to create a login
for yourself first).
The task list (<http://savannah.gnu.org/pm/?group_id=99>) is supposed
to tell people what jobs are waiting to be done. Feel free to add to it
or update the tasks that are there (you need to create a login for
yourself first).
One job of major importance that pretty much anyone can do is to
look for jobs to add to the task list. In the case of methods from the
@ -297,7 +297,7 @@ idea to get in touch with Adam or Richard to coordinate efforts.
How do I start writing tests?
-----------------------------
You can write testcases - where the libraries fail tests, you could
You can write testcases - where the libraries fail tests, you could
either fix the problem, or add it to the task list.
To write testcases, you need to use anonymous CVS to install the
@ -311,14 +311,14 @@ GNUstep CVS repository.
How do I start writing applications?
------------------------------------
You can either look at the links on the GNUstep website for
You can either look at the links on the GNUstep website for
applications that have been started, and email their owners to
volunteer to help, or you can start your own project.
How can I help with the GNUstep website?
----------------------------------------
Talk to Adam Fedor <fedor@gnu.org>, the maintainer.
Talk to Adam Fedor <fedor@gnu.org>, the maintainer.
The GNUstep website is kept as a CVS module, but the largest portions
of it (the FAQ and the Documentation) are actually generated from files
@ -340,7 +340,7 @@ out-of-date (or wrong) and update/mark-as-outdated as required.
Why doesn't GDB support Objective-C?
------------------------------------
Update: GDB 6.0, which should come out sometime in September 2003
Update: GDB 6.0, which should come out sometime in September 2003
supports debugging of Objective-C code.
There are patches available on the gnustep web site for earlier
@ -352,8 +352,8 @@ GNU Objective C Compiler and Runtime
What is the Objective C Runtime?
--------------------------------
The Objective C Runtime Library provides C functions and data
structures required to execute an Objective C program.
The Objective C Runtime Library provides C functions and data structures
required to execute an Objective C program.
The GNU Objective C Runtime Library offers everything NeXT's runtime
does, including Categories, Protocols, `+poseAs:', thread-safety, class
@ -381,13 +381,13 @@ initialization of static instances (such as @""-style string objects).
Does it allow a mixture of Objective C and C++?
-----------------------------------------------
No. See *note Can one use the hybrid "Objective-C++"::
No. See *note Can one use the hybrid "Objective-C++"::
Where can I find more information?
----------------------------------
The FAQ associated with the newsgroup `comp.lang.objective-c'
contains more information about GNU Objective C.
The FAQ associated with the newsgroup `comp.lang.objective-c' contains
more information about GNU Objective C.
GNUstep Base Library
====================
@ -395,12 +395,12 @@ GNUstep Base Library
What is the GNUstep Base Library?
---------------------------------
The GNUstep Base Library is a library of general-purpose,
non-graphical Objective C objects. For example, it includes classes
for strings, object collections, byte streams, typed coders,
invocations, notifications, notification dispatchers, moments in time,
network ports, remote object messaging support (distributed objects),
event loops, and random number generators.
The GNUstep Base Library is a library of general-purpose, non-graphical
Objective C objects. For example, it includes classes for strings,
object collections, byte streams, typed coders, invocations,
notifications, notification dispatchers, moments in time, network ports,
remote object messaging support (distributed objects), event loops, and
random number generators.
It provides functionality that aims to implement the non-graphical
portion of the OpenStep standard (the Foundation library).
@ -408,7 +408,7 @@ portion of the OpenStep standard (the Foundation library).
What is its current state of development?
-----------------------------------------
GNUstep base is currently stable and, to the best of our knowledge,
GNUstep base is currently stable and, to the best of our knowledge,
implements all of the OpenStep functionality (except for a few classes
that we feel are not useful). It also implements most all of the new
Cocoa classes. However we do some things, like scripting, differently,
@ -417,7 +417,7 @@ so we don't implement all the Cocoa classes.
What are the features of GNU Distributed Objects?
-------------------------------------------------
GNU Distributed Objects has many of the features of other distributed
GNU Distributed Objects has many of the features of other distributed
objects implementations, but, since it is free software, it can be
ported to platforms for which other distributed objects implementations
are not available.
@ -447,7 +447,7 @@ GNUstep GUI Library
What is the GUI Library?
------------------------
The GNUstep GUI Library is a library of objects useful for writing
The GNUstep GUI Library is a library of objects useful for writing
graphical applications. For example, it includes classes for drawing
and manipulating graphics objects on the screen: windows, menus,
buttons, sliders, text fields, and events. There are also many
@ -463,7 +463,7 @@ written to take advantage of GNUstep enhancements wherever possible.
Explain the organization of the front- and back-ends
----------------------------------------------------
The GNUstep GUI Library is divided into a front- and back-end. The
The GNUstep GUI Library is divided into a front- and back-end. The
front-end contains the majority of implementation, but leaves out the
low-level drawing and event code. A back-end can override whatever
methods necessary in order to implement low-level drawing event
@ -477,14 +477,14 @@ platforms to share the large amount of front-end code.
What is the current state of development of the front-end?
----------------------------------------------------------
Many of the classes are well implemented, if not thoroughly tested.
Many of the classes are well implemented, if not thoroughly tested.
See the GNUstep web sites and read status information contained in the
distribution for the most up-to-date information.
What is the current state of development of the back-ends?
----------------------------------------------------------
There are several backends currently available:
There are several backends currently available:
`xlib'
This is the standard backend that runs on X11 and uses standard
@ -505,9 +505,9 @@ GNUstep DisplayGhostScript Server
What is the Display Ghostscript Server?
---------------------------------------
It is a free implementation of a Display PostScript server based on
the GNU Ghostscript program developed by Aladdin Enterprises and now
owned by artofcode LLC.
It is a free implementation of a Display PostScript server based on the
GNU Ghostscript program developed by Aladdin Enterprises and now owned
by artofcode LLC.
At one point, GNUstep was using this for display purposes. However
the development of DGS has stopped as it is too difficult to maintain
@ -517,17 +517,17 @@ drawing.
What is its current state of development?
-----------------------------------------
GNU contracted with Aladdin Enterprises to add some key features to
GNU Ghostscript so it could be used as a DPS server. This work has
mostly been done, although Aladdin did not completely finish the work
that they were contracted for. (Because the work took longer than
specified and was not completed, Aladdin agreed to waive approximately
$10,000 in promised fees for the work that was actually done and
delivered.) DGS works fairly well with a single context. Alpha
channel and compositing currently doesn't work.
GNU contracted with Aladdin Enterprises to add some key features to GNU
Ghostscript so it could be used as a DPS server. This work has mostly
been done, although Aladdin did not completely finish the work that they
were contracted for. (Because the work took longer than specified and
was not completed, Aladdin agreed to waive approximately $10,000 in
promised fees for the work that was actually done and delivered.) DGS
works fairly well with a single context. Alpha channel and compositing
currently doesn't work.
What is the relationship between the Display Ghostscript Server and X Windows?
------------------------------------------------------------------------------
Display Ghostscript runs on top of X Windows.
Display Ghostscript runs on top of X Windows.

259
GNUstep-HOWTO
View file

@ -1,7 +1,7 @@
GNUstep HOWTO
*************
Last Update: 27 February 2004
Last Update: 9 June 2004
This document explains how to build the different components of the
GNUstep core libraries and GNUstep Launchpad.
@ -15,7 +15,7 @@
Introduction
************
This document explains how to build the GNUstep core libraries. The
This document explains how to build the GNUstep core libraries. The
core libraries, along with associated tools and other files provide
everything necessary for a working GNUstep system.
@ -29,14 +29,15 @@ order to compile the GNUstep core libraries.
Summary
*******
In order to compile the libraries, you need to compile and install
the following packages first (if you don't already have them):
In order to compile the libraries, you need to compile and install the
following packages first (if you don't already have them):
* gcc (Version 2.95 or greater, 3.0.4 or greater recommended)
* GNU make (Version 3.75 or greater)
* gdb, if you plan to do any debugging
* gdb (Version 6.0 or greater recommended), if you plan to do any
debugging
You may also need to install some of the following libraries and
packages described below. Most of these packages are optional, but some
@ -61,6 +62,9 @@ are required.
compatible XML-based property-lists. It is recommended but not
currently required.
`libxslt (OPTIONAL)'
Stylesheet support for use with XML.
`openssl (OPTIONAL)'
The openssl library is used to provide support for https
connections by the NSURL and HSURLHandle classes. This
@ -87,6 +91,15 @@ are required.
`The PNG library (libpng) (RECOMMENDED)'
The GUI library uses this to handle loading PNG images.
`libaudiofile (RECOMMENDED)'
The GUI library uses this for the sound server
`freetype2 (RECOMMENDED, REQUIRED for art backend)'
This is used for font information
`libart_lgpl2 (REQUIRED for art backend only)'
Drawing library for the art backend.
`WindowMaker (Version >= 0.62) (OPTIONAL)'
GNUstep and WindowMaker work together to provide a consistant
interface. Although it is not required, GNUstep will work much
@ -117,7 +130,7 @@ are required.
Compiling and Installing the packages
*************************************
Get the following individual packages:
Get the following individual packages:
* gnustep-make
@ -130,10 +143,11 @@ Compiling and Installing the packages
See <http://www.gnustep.org> for information on where to get these
packages.
Make sure you install all the previously mentioned libraries first
before configuring and building GNUstep.
Make sure you install (if necessary) all the previously mentioned
libraries first before configuring and building GNUstep.
You should be able to install these packages as root.
You should install these packages as root (read special note for the
gnustep-base library, below, if you cannot do this).
For installation on specific systems, read the machine specific
instructions at the end of this document or appropriate README files in
@ -143,8 +157,8 @@ Windows).
Installing the Core Libraries
=============================
The GNUstep packages uses the Autoconf mechanism for configuration;
it checks some host capabilties which are used by all GNUstep software.
The GNUstep packages uses the Autoconf mechanism for configuration; it
checks some host capabilties which are used by all GNUstep software.
To configure just type:
./configure
@ -165,15 +179,15 @@ configure will use /usr/GNUstep as the default root directory.
Alternate Library Setup
-----------------------
Read the installation instructions in the Makefile package (make)
for more installation options. Make sure you use the same configuration
Read the installation instructions in the Makefile package (make) for
more installation options. Make sure you use the same configuration
options when configuring each GNUstep library.
Building the Package
--------------------
To build the individual packages, use this familiar set of commands
for each pacakge (add any additional options you decide upon):
To build the individual packages, use this familiar set of commands for
each pacakge (add any additional options you decide upon):
./configure
make
@ -213,7 +227,7 @@ Additional Installation
Environment Setup
=================
Add the shell script `GNUstep.sh' located in the Makefile package to
Add the shell script `GNUstep.sh' located in the Makefile package to
your shell startup file (such as `.profile'). For instance, if your
GNUSTEP_SYSTEM_ROOT is `/usr/GNUstep/System',
@ -236,7 +250,7 @@ tcsh, try
GNUstep Home
============
Set up your home GNUstep directory. This should be done automatically
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
other user configuration files. User installed apps, libraries, etc are
also here (if the default user directory is used).
@ -247,7 +261,7 @@ also here (if the default user directory is used).
Time Zone
=========
Next, set your local time zone. There are four ways to do this, pick
Next, set your local time zone. There are four ways to do this, pick
one (see
`$GNUSTEP_SYSTEM_ROOT/Library/Libraries/Resources/gnustep-bsae/NSTimeZones/zones'
for typical time zones):
@ -269,7 +283,7 @@ for typical time zones):
GNUstep deamons
===============
Set up your system to execute some GNUstep deamons. If you don't do
Set up your system to execute some GNUstep deamons. If you don't do
this, they will be started automatically when you run your first GNUstep
app:
@ -293,7 +307,7 @@ app:
Test Tools and Applications
***************************
Test programs for the base library are in `base/Testing'. Example
Test programs for the base library are in `base/Testing'. 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
@ -310,12 +324,16 @@ Usage is:
Machine Specific Instructions
*****************************
\input texinfo
\input texinfo
Below is a list of machines that people have attempted to compile
GNUstep on. GNUstep compiles with little or no trouble on many of the
more popular operating systems. Some machines marked with _Unstable_
may have some trouble or may not work at all.
may have some trouble or may not work at all. Platforms marked _Needs
Testing_ are not actively tested by developers and need someone to help
with reporting problems and fixes. Platforms marked _Obsolete_ are
very old distributions. No one really knows if GNUstep works on these
although they may.
A recommended compiler is listed for each machine, if known. You
should try to use the recommended compiler for compiling GNUstep, as
@ -327,7 +345,7 @@ 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.
`egcs or gcc < 2.95'
Probably will work, but few people use these now.
Might work, but few people use these now.
`gcc 2.95.x'
Probably the oldest compiler that GNUstep is regularly tested with.
@ -351,6 +369,9 @@ of the following information before choosing the compiler you use.
Recommended. Fixes some bugs relating to protocols as well as other
improvements.
`gcc 3.4'
No info yet.
If you have compiled GNUstep on a specific machine, please send
information about what you needed and any special instructions needed to
GNUstep <bug-gnustep@gnu.org>.
@ -367,40 +388,49 @@ compiling and installing gcc and make. If you had GNUstep previously
installed, make sure you completely remove all of it, including
installed init scripts.
Darwin 6.x/PowerPC
==================
Darwin/ix86
===========
Currently tested on Darwin 7.x
`Recommended compiler'
gcc 3.3.2. Older versions will not compile on Darwin.
Default compiler has some odd memory(?) related problems. Use the
GNU runtime. Download the gcc compiler and configure it with
Default compiler has unknown problems. Use the GNU runtime.
Download the gcc compiler and configure it with
-enable-threads=posix. You don't need binutils or anything else.
Optional: Usually the installed compiler will produce object files
for the NeXT runtime if you don't say gcc -fgnu-runtime. To change
this behaviour, edit src-dir/gcc/config/darwin.h: You have to
change the word #define in line 73 to #undef. Then the runtime
default is gnu. When bootstrapping the compiler a nice working
objective C gnu-runtime library (which is a little bit faster than
Apple's runtime) will be compiled and installed when make install.
To use it, there is one (important) thing left: After installing
the compiler, you have to go to install-dir/lib and produce the
following dynamic link:
ln -s libobjc.a libobjc.dylib
This might seem senseless, but it forces the linker to use this
library instead of the NeXT-runtime!
`Extra libs needed'
`Special Instructions'
Read the <README.Darwin> file in the gnustep-make/Documentation
directory for complete instructions.
Darwin/PowerPC
==============
Currently tested on Darwin 6.x, 7.x
`Recommended compiler'
gcc 3.3.2. Older versions will not compile on Darwin.
Default compiler has unknown problems. Use the GNU runtime.
Download the gcc compiler and configure it with
-enable-threads=posix. You don't need binutils or anything else.
`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. Also you
need the dlcompat library (from <www.opendarwin.org>) to load
bundles (like the backend bundle).
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'
Make sure to configure gnustep-make with ./configure
-with-library-combo=gnu-gnu-gnu if you want to use all the GNUstep
libraries.
Read the <README.Darwin> file in the gnustep-make/Documentation
directory for complete instructions.
See also the MacOSX/PowerPC section
Debian/DEC-Alpha
================
@ -417,7 +447,7 @@ Debian/DEC-Alpha
Debian/i386
===========
Tested on sid.
Tested on sid.
`Recommended compiler'
Unknown
@ -430,7 +460,7 @@ Debian/i386
Debian/PowerPC
==============
Tested on sid.
Tested on sid.
`Recommended compiler'
Unknown
@ -443,7 +473,7 @@ Debian/PowerPC
Debian/SPARC
============
Tested on sid.
Tested on sid.
`Recommended compiler'
Unknown
@ -453,6 +483,21 @@ Debian/SPARC
`Special Instructions'
None
FreeBSD 5.x
===========
Tested on 5.0 and 5.1
`Recommended compiler'
`Extra libs needed'
None.
`Special Instructions'
Can install via /usr/ports/devel/gnustep, but not all required
dependancies are installed. See the GNUstep-HOWTO for list of
libraries.
FreeBSD 4.x
===========
@ -471,10 +516,11 @@ FreeBSD 4.x
For libxml2 2.4.24, make WITHOUT_PYTHON=YES
FreeBSD 3.x
===========
Compiles "out of the box" on FreeBSD 3.4.
Compiles "out of the box" on FreeBSD 3.4.
`Recommended compiler'
gcc 2.95.2
@ -512,8 +558,9 @@ FreeBSD 3.x
need to pass these flags to configure:
`CFLAGS="-I/usr/local/include"' and `LDFLAGS="-L/usr/local/lib"'.
FreeBSD 2.x (_Unstable!_)
=========================
FreeBSD 2.x (_Obsolete,Unstable_)
=================================
`Recommended compiler'
gcc 2.8.x
@ -533,6 +580,7 @@ FreeBSD 2.x (_Unstable!_)
FreeBSD 3.x. You need to use gmake not make to compile the
GNUstep packages.
Irix 6.5/MIPS
=============
@ -553,10 +601,38 @@ Irix 6.5/MIPS
use systune ncargs to increase the value (maximum is 262144) or
link the library by hand. No libffi-support: Use ffcall
MkLinux/PowerPC (_Obsolete_)
============================
This configuration is no longer being tested, but it may still work.
MacOSX/PowerPC
==============
Currently tested on MacOSX 10.2, 10.3
`Recommended compiler'
Default.
`Extra libs needed'
None.
`Special Instructions'
By default, on Mac OS X, only the GNUstep extensions are built.
This is if you want to build gdl2, etc on Mac OS X. Xcode project
files exist, but they may not be up-to-date. Try:
cd make
./configure --with-library-combo=apple-apple-apple
make install
cd ../base
./configure --with-xml-prefix=/usr --disable-xmltest
make debug=yes install
See also the Darwin/PowerPC section.
MkLinux/PowerPC
===============
Tested with R2 RC2 (2004/03/04).
`Recommended compiler'
gcc 3.x allthough earlier ones should work if you also install
@ -566,15 +642,8 @@ MkLinux/PowerPC (_Obsolete_)
None.
`Special Instructions'
DR3 comes with a good version of gcc. Seems to compile and
install ok, althouth DR3 has an old version of glibc, which
requires some workarounds which should be taken care of in the
configuration. Not completely tested, so some aspects, particular
object invocations and DO may not work properly.
Unknown.
If you want threads, you'll probably have to get the latest gcc
compiler and glibc library (which has the threads library) and
install both.
NetBSD
======
@ -586,10 +655,11 @@ NetBSD
libiconv
`Special Instructions'
See the README.NetBSD file located in the gnustep-make package.
See the <README.NetBSD> file located in the gnustep-make package.
Netwinder (_Unstable!_)
=======================
Netwinder (_Unstable_)
======================
`Recommended compiler'
Build #12 of the system.
@ -600,8 +670,8 @@ Netwinder (_Unstable!_)
`Special Instructions'
See <http://www.netwinder.org/~patrix>
OpenBSD 3.x (_Unstable!_)
==========================
OpenBSD 3.x (_Needs Testing_)
==============================
`Recommended compiler'
Unknown
@ -610,12 +680,13 @@ OpenBSD 3.x (_Unstable!_)
Unknown
`Special Instructions'
Try reading the README.NetBSD which might work the same on OpenBSD.
Try reading the <README.NetBSD> which might work the same on
OpenBSD.
OSF Alpha (_Unstable!_)
========================
OSF Alpha (_Unstable_)
=======================
Information is for Version 3.2C
Information is for Version 3.2C
`Recommended compiler'
egcs-1.1.1/1.1.2, gcc-2.95
@ -632,6 +703,7 @@ OSF Alpha (_Unstable!_)
extra -lgnustep-gui in ADDTIONAL_TOOL_LIBS in the
GNUmakefile(.preamble).
RedHat/Intel
============
@ -656,10 +728,11 @@ Slackware/Intel
`Special Instructions'
Unknown.
Solaris 2.5.1/Sparc (_Obsolete_)
================================
This configuration is no longer being tested, but it may still work.
This configuration is no longer being tested, but it may still work.
`Recommended compiler'
Unknown
@ -689,6 +762,7 @@ Solaris 2.[67]/Sparc
is highly recommended. In fact, some functions, such as compiling
frameworks, will not work without it.
Some people have reported problems when using binutils assembler and
linker. Using the native Solaris assmebler and linker should work fine.
@ -718,10 +792,11 @@ Solaris 2.7/Intel
warnings, which probably can be ignored. See the other Solaris
instructions above for more information.
Suse 6.x/Intel
==============
GNUstep has been tested on version 6.2-6.4 of Suse
GNUstep has been tested on version 6.2-6.4 of Suse
`Recommended compiler'
Standard
@ -735,10 +810,11 @@ Suse 6.x/Intel
gdnc doesn't work. If you recompile the kernel then it starts
working.
Suse/Intel
==========
GNUstep has been tested on version 7.0, 8.0, 8.1, 8.2, and 9.0 of
GNUstep has been tested on version 7.0, 8.0, 8.1, 8.2, 9.0, and 9.1 of
Suse
`Recommended compiler'
@ -752,10 +828,11 @@ Suse
`Special Instructions'
None.
Suse 7.x/PPC
============
GNUstep has been tested on version 7.0 of Suse/PPC
GNUstep has been tested on version 7.0 of Suse/PPC
`Recommended compiler'
Standard. gcc2.95.x, gcc3.0.x and gc3.1 work, but 2.95 is faster.
@ -765,6 +842,7 @@ Suse 7.x/PPC
None
`Special Instructions'
Unixware-2.1.3/Intel
====================
@ -774,6 +852,7 @@ Unixware-2.1.3/Intel
`Extra libs needed'
Unknown
Special Instructions for GNUstep installation on Unixware 2.1 systems
1
@ -852,14 +931,15 @@ Unixware-2.1.3/Intel
. /usr/local/GNUstep/Library/Makefiles/GNUstep.sh
gdomap -a /etc/gdomap_addresses
If you don't set gdomap up correctly, Distributed Objects will not
work.
Windows with CYGWIN (_Unstable!_)
=================================
Windows with CYGWIN (_Needs Testing_)
=====================================
`Recommended compiler'
gcc 2.95.3 (Cygwin release 1.1.8) or later
gcc 3.3.1 or later (with libobjc and libjava (if using libffi))
`Extra libs needed'
Objective-C library DLL
@ -868,21 +948,17 @@ Windows with CYGWIN (_Unstable!_)
(gcc -v for location) so that it isn't accidentally found. For
ffcall, you should get version 1.8b or above (the earlier ones
don't compile). There are still some problems with structure
passing, but that is generally not supportred on any architecture.
passing, but that is generally not supported on any architecture.
libffi also works.
`Special Instructions'
On later versions of Cygwin you may be required to include the
win32api directory in CPPFLAGS when configuring:
Make sure you have good shared libraries for everthing. Sometimes
a bad shared library (like libtiff) will cause odd and untraceable
problems. See <README.Cygwin> for information on compiling.
CPPFLAGS=-I/usr/include/win32api ./configure
Make sure you have good shared libraries for everthing. Sometimes a
bad shared library (like libtiff) will cause odd and untraceable
problems. See `README.Cygwin' for information on compiling.
Windows with MinGW (_Unstable! As always..._)
=============================================
Windows with MinGW
==================
`Recommended compiler'
See below.
@ -891,7 +967,7 @@ Windows with MinGW (_Unstable! As always..._)
See below.
`Special Instructions'
See the `README.MinGW' file located in the gnustep-make
See the <README.MinGW> file located in the gnustep-make
Documentation directory for instructions. Windows NT/2000/XP only.
Win98 machines and earlier are very buggy and are not supported.
Native GUI backend is alpha version.
@ -906,10 +982,11 @@ Yellowdog/PowerPC
Standard (ffcall or libffi)
`Special Instructions'
Getting Libraries via Anonymous CVS
***********************************
If you didn't get one of the snapshots, or if you want to be sure to
If you didn't get one of the snapshots, or if you want to be sure to
stay on the bleading edge, then you should get the libraries via CVS. Go
to <http://savannah.gnu.org/cvs/?group_id=99> for information on how to
get anonymous CVS access.

48
INSTALL
View file

@ -4,7 +4,7 @@ GNUstep makefile package installation
Introduction
============
If you are installing this package as part of the GNUstep core
If you are installing this package as part of the GNUstep core
libraries, read the file GNUstep-HOWTO for more complete instructions on
how to install the entire GNUstep package (including this package).
GNUstep-HOWTO comes with this distribution.
@ -38,8 +38,8 @@ GNUstep-HOWTO and are also located at the GNUstep web site at
Configuration
=============
The GNUstep packages uses the Autoconf mechanism for configuration;
it checks some host capabilties which are used by all GNUstep software.
The GNUstep packages uses the Autoconf mechanism for configuration; it
checks some host capabilties which are used by all GNUstep software.
To configure just type:
./configure
@ -73,7 +73,7 @@ also when you install).
Backend Bundles
---------------
By default, the gnustep-make package specifies that GUI backends are
By default, the gnustep-make package specifies that GUI backends are
built as a bundle and loaded in at runtime. This allows one to switch
backends by simply redefining a user default. If you do not want this
behavior (for instance, if bundles do not work on your platform), it
@ -86,7 +86,7 @@ can be disabled using
Alternate Library Setup
-----------------------
You can specify compilation of alternate libraries by using the
You can specify compilation of alternate libraries by using the
with-library-combo option.
./configure --with-library-combo=apple-gnu-gnu
@ -97,8 +97,8 @@ DESIGN document for more examples of the variety of library combos.
Alternate Thread Library
------------------------
You can specify compilation of an alternate thread library from the
one that is normally used (or if GNUstep does not know what your normal
You can specify compilation of an alternate thread library from the one
that is normally used (or if GNUstep does not know what your normal
library is) with the with-thread-lib option.
./configure --with-thread-lib="-L/usr/local/lib -lgthread -lglib"
@ -115,19 +115,19 @@ variable when calling configure:
Warnings for #import
--------------------
Up until gcc 3.4, the #import directive was not implemented
correctly. As a result, the GCC compiler automatically emitted a
warning whenever #import was used. As of gcc 3.4, this problem has
been fixed, so presumable, this warning is no longer emitted when code
is compiled. If you are using an early compiler, you can supress these
warnings by adding `-Wno-import' to `CPPFLAGS' in the config.make file.
Up until gcc 3.4, the #import directive was not implemented correctly.
As a result, the GCC compiler automatically emitted a warning whenever
#import was used. As of gcc 3.4, this problem has been fixed, so
presumable, this warning is no longer emitted when code is compiled. If
you are using an early compiler, you can supress these warnings by
adding `-Wno-import' to `CPPFLAGS' in the config.make file.
Configuring for a non-flattened structure
-----------------------------------------
GNUstep is normally configured to support a single target/combo. If
you are interested in supporting more than one target and/or combo,
it's possible to configure GNUstep to use a non-'flattened' directory
GNUstep is normally configured to support a single target/combo. If you
are interested in supporting more than one target and/or combo, it's
possible to configure GNUstep to use a non-'flattened' directory
structure. You do this by supplying the `--disable-flattened' argument
to configure. You might also want to supply the
`--enable-multi-platform' option.
@ -138,7 +138,7 @@ than in a `$(GNUSTEP_CPU)/$(GNUSTEP_OS)/$(LIBRARY_COMBO)' subdirectory.
Configuring for a cross-compile target
--------------------------------------
By default when you run configure, it assumes that you want to create
By default when you run configure, it assumes that you want to create
executables for the same host that you are compiling on; however, the
GNUstep makefile package has been designed to support cross-compiling
just as easily as normal compiling. In order to add a cross-compile
@ -168,7 +168,7 @@ the make package several times.
Installation
============
After you configure the GNUstep makefile package, then you need to
After you configure the GNUstep makefile package, then you need to
compile the programs that come with the package. Currently there is
only a single C program which needs to be compiled; all of the other
files are either shell scripts or makefile fragments, so you can
@ -187,9 +187,9 @@ Setting up the GNUstep environment
Setting up the GNUstep environment for all users
------------------------------------------------
The GNUstep environment and thus usage of the makefile package is
based almost solely upon the GNUSTEP_SYSTEM_ROOT environment variable.
So essentially the setup involved is to make sure that the variable is
The GNUstep environment and thus usage of the makefile package is based
almost solely upon the GNUSTEP_SYSTEM_ROOT environment variable. So
essentially the setup involved is to make sure that the variable is
defined for all users. The GNUstep.sh file within the makefile package
contains all of the environment variable settings required, so you want
to call that shell. Some systems, like GNU/Linux have an
@ -222,9 +222,9 @@ NSSearchPathForDirectoriesInDomains() to locate files instead.
Setting up the GNUstep environment for a single user
----------------------------------------------------
The GNUstep environment and thus usage of the makefile package is
based almost solely upon the GNUSTEP_SYSTEM_ROOT environment variable.
So essentially the setup involved is to make sure that the variable is
The GNUstep environment and thus usage of the makefile package is based
almost solely upon the GNUSTEP_SYSTEM_ROOT environment variable. So
essentially the setup involved is to make sure that the variable is
defined for the user. The GNUstep.sh file within the makefile package
contains all of the environment variable settings required, so you want
to call that shell when the user logs in to the system. Most shells

51
NEWS
View file

@ -1,7 +1,14 @@
NEWS
****
The currently released version is `1.9.1'.
The currently released version is `1.9.2'.
Changes in version `1.9.2'
==========================
* Application and Bundles use the latest convention on Apple.
* Improve/Simplify dependency checking when making docs
Changes in version `1.9.1'
==========================
@ -24,16 +31,16 @@ Changes in version `1.9.0'
Changes in version `1.8.0'
==========================
Read the NEWS file for a complete list of changes since the last
stable release. The major difference from 1.6.0 is that the locations
of certain directories have changed. Generally this will not cause a
Read the NEWS file for a complete list of changes since the last stable
release. The major difference from 1.6.0 is that the locations of
certain directories have changed. Generally this will not cause a
problem unless your GNUstep directory is shared by multiple machines
running this and earlier (1.6.x) versions of the software.
Changes in version `1.7.4'
==========================
Bug fixes.
Bug fixes.
Changes in version `1.7.3'
==========================
@ -45,7 +52,7 @@ Changes in version `1.7.3'
Changes in version `1.7.2'
==========================
-enable-flattened (Flat directory structure) is on by default.
-enable-flattened (Flat directory structure) is on by default.
* On WIN32 use HOMEPATH in preference to USERPROFILE
@ -54,12 +61,12 @@ Changes in version `1.7.2'
Changes in version `1.7.1'
==========================
Bug fixes.
Bug fixes.
Changes in version `1.7.0'
==========================
This version contains a major change in the location of certain
This version contains a major change in the location of certain
directories and installed files as detailed in the `filesystem.texi'
document. When installing this version for the first time, all old
directories and files in those directories will be moved to the new
@ -74,8 +81,8 @@ incompatibilities.
Changes in version `1.6.0'
==========================
Make now configures by default for only one system. To compile and
run GNUstep for multiple platforms from the same directory, use the
Make now configures by default for only one system. To compile and run
GNUstep for multiple platforms from the same directory, use the
configure argument -enable-multi-platform.
* Auto-build def file for DLLs
@ -118,7 +125,7 @@ Changes in version `1.4.0'
Changes in version `1.3.4'
==========================
This is a first prerelease version for 1.4.
This is a first prerelease version for 1.4.
* Use gnugc-gnu-gnu library combo for garbage collecting version.
@ -149,7 +156,7 @@ Changes in version `1.3.2'
Changes in version `1.3.0'
==========================
The package has gone through an extensive reorganization to break up
The package has gone through an extensive reorganization to break up
each sub-make into two separate components. This allows for much
simplified code and lots of code sharing between components. As a side
effect, it also increased the speed of the code by at least a factor of
@ -247,8 +254,8 @@ Changes in version `0.9.2'
Changes in version `0.9.1'
==========================
Make has been reoganized so that it only relies on libraries and
other things that are necessary for the Makefile package itself. Any
Make has been reoganized so that it only relies on libraries and other
things that are necessary for the Makefile package itself. Any
libraries wanting to add extra package information can do so by
installing a make stub in the `Additional' directory. This greatly
simplifies compilation and packaging.
@ -262,7 +269,7 @@ simplifies compilation and packaging.
Changes in version `0.9.0'
==========================
ffcall library is highly recommended for use with the GNUstep base
ffcall library is highly recommended for use with the GNUstep base
library. You need to have installed it prior to configuring the Makefile
package. See the INSTALL file.
@ -279,13 +286,13 @@ package. See the INSTALL file.
Noteworthy changes in version `0.6.6'
=====================================
The GNUstep system libraries are now installed in a separate system
root directory (default /usr/GNUstep/System) rather than the GNUstep
root directory (default /usr/GNUstep). You can revert to the old
behavior using a configure option `--without-system-root'. We also
recommend removing any previous GNUstep versions before installing the
new one in order to avoid problems with the system finding the correct
binary and/or library.
The GNUstep system libraries are now installed in a separate system root
directory (default /usr/GNUstep/System) rather than the GNUstep root
directory (default /usr/GNUstep). You can revert to the old behavior
using a configure option `--without-system-root'. We also recommend
removing any previous GNUstep versions before installing the new one in
order to avoid problems with the system finding the correct binary
and/or library.
* Support for Windows compilation (cygwin and mingw) and DLL creation
and usage.

25
README
View file

@ -6,16 +6,16 @@ Here is some introductory info to get you started:
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.
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.
Information
===========
The file `NEWS' has this packages feature history.
The file `NEWS' has this packages feature history.
The files `INSTALL' or `GNUstep-HOWTO' give instructions for
installing the packages. Also see the `machines' documentation and
@ -28,12 +28,11 @@ work with it.
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.
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,
@ -49,7 +48,7 @@ are under GNU LGPL" (Text in quotes provided by the author of ffcall).
History
=======
The GNUstep makefile package was designed by Scott Christley
The GNUstep makefile package was designed by Scott Christley
<scottc@net-community.com> and Ovidiu Predescu
<ovidiu@net-community.com>.

2
Version
View file

@ -4,7 +4,7 @@
# The version number of this release.
GNUSTEP_MAKE_MAJOR_VERSION=1
GNUSTEP_MAKE_MINOR_VERSION=9
GNUSTEP_MAKE_SUBMINOR_VERSION=1
GNUSTEP_MAKE_SUBMINOR_VERSION=2
GNUSTEP_MAKE_VERSION=${GNUSTEP_MAKE_MAJOR_VERSION}.${GNUSTEP_MAKE_MINOR_VERSION}.${GNUSTEP_MAKE_SUBMINOR_VERSION}