Version 1.2.1

git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@12024 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Adam Fedor 2002-01-07 15:24:55 +00:00
parent 44ae0dc07b
commit cfeb1a4622
11 changed files with 192 additions and 157 deletions

View file

@ -1,7 +1,7 @@
Announcement
************
The GNUstep Makefile Package version 1.2.0 is now available.
The GNUstep Makefile Package version 1.2.1 is now available.
What is the GNUstep makefile package?
=====================================
@ -12,38 +12,28 @@ 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.2.0'
Changes in version `1.2.1'
==========================
* The core rules and internals of gnustep-make have been
fundamentally redesigned and rewritten. notably, gnustep-make now
works using only a single recursive sub-make invocation rather
than two, which makes it consistently faster and simpler in all
circumstances.
* the source distribution code has been rewritten to be more general
and extended. Packages built using gnustep-make now automatically
have handy targets building tarballs from sources or from CVS
imports.
* The clean rules have been heavily optimized - they no longer use
recursive sub-make invocations at all and so they are really fast.
* implemented support for auto-dependencies, which means that any
object file automatically depends on all the header files which
were used to build it. Only works with newer compilers.
* Many improvements to java support. Optimized management of nested
classes
* implemented INSTALL_AS_USER and INSTALL_AS_GROUP.
* Better conformance to make conventions.
* implemented a strip=yes option.
* File specific compilation flags
* Fixed darwin support
* Support for C++ files.
* Made use of library installation dir consistent with other
installation.
* Much improved Windows path support
* various bug fixes and minor improvements.
Obtaining gnustep-make
======================
You can get the gstep-make-1.2.0.tar.gz distribution file at
You can get the gstep-make-1.2.1.tar.gz distribution file at
<ftp://ftp.gnustep.org/pub/gnustep/core>
Please send bug reports to <bug-gnustep@gnu.org>.

View file

@ -1,3 +1,8 @@
2002-01-07 Adam Fedor <fedor@gnu.org>
* Version: 1.2.1
* Documentation/gnustep-howto.texi, install.texi, news.texi: Update.
2002-01-06 Richard Frith-Macdonald <rfm@gnu.org>
* documentation.make: quick hack for agsdoc install to ignore failure

View file

@ -45,9 +45,9 @@ MKDIRS = ../mkinstalldirs
DOCUMENT_NAME = make gnustep-howto machines faq internals
# The text documents to be generated
DOCUMENT_TEXT_NAME = FAQ INSTALL README NEWS GNUstep-HOWTO
DOCUMENT_TEXT_NAME = FAQ INSTALL README NEWS GNUstep-HOWTO ANNOUNCE
TOP_DOC_FILES = FAQ INSTALL README NEWS GNUstep-HOWTO
TOP_DOC_FILES = FAQ INSTALL README NEWS GNUstep-HOWTO ANNOUNCE
GNUstep-HOWTO_TEXI_FILES = version.texi
GNUstep-HOWTO_TEXT_MAIN = gnustep-howto.texi

View file

@ -144,11 +144,10 @@ XML-based property-lists. It is recommended but not currently required.
@item openssl
The openssl library is used to provide support for https connections by
the NSURL and HSURLHandle classes. To enable this option
you need to have the openssl libraries installed and add the option
@code{--enable-openssl} when running the @file{configure} script. Note that
the OpenSSL license is not compatible with GPL, so do not use this option
if you want your programs to be GPL compatible.
the NSURL and HSURLHandle classes. This functionality is
compiled as a separate bundle since the OpenSSL license is not
compatible with GPL, and in the hopes that if someone writes an openssl
replacement, it can quickly be used by creating another bundle.
@item libiconv
Unicode support functions (iconv) come with glibc version 2.1 or greater. If
@ -320,8 +319,9 @@ source $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.csh
@node GNUstep Home, Time Zone, Environment Setup, Additional Installation
@section GNUstep Home
Set up your home GNUstep directory. This is where user defaults are
kept, and in the future, other files may be kept there.
Set up your home GNUstep directory. 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
@ -364,8 +364,8 @@ app:
@item gdomap - Put this in a system startup file, like @file{/etc/rc.local} or @file{/etc/rc.d/rc.local} (customize for your system)
@example
GNUSTEP_SYSTEM_ROOT=/usr/GNUstep
if [ -f $GNUSTEP_SYSTEM_ROOT/Tools/powerpc/linux-gnu/gdomap ]; then
$GNUSTEP_SYSTEM_ROOT/Tools/powerpc/linux-gnu/gdomap
if [ -f $GNUSTEP_SYSTEM_ROOT/Tools/ix86/linux-gnu/gdomap ]; then
$GNUSTEP_SYSTEM_ROOT/Tools/ix86/linux-gnu/gdomap
fi
@end example
@item gdnc - Put this after executing @file{GNUstep.sh} in your local .profile

View file

@ -248,10 +248,12 @@ shells have some file that you read upon login, for example the BASH
shell reads the .bash_profile file in the user's home directory. So
you can add the following lines to that file:
@example
# Setup for the GNUstep environment
if [ -f $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh ]; then
. $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh
fi
@end example
This will source in the GNUstep.sh file and set the environment
variables; thus making them available for the user.

View file

@ -9,6 +9,22 @@
The currently released version is @samp{@value{GNUSTEP-MAKE-VERSION}}.
@end ifclear
@section Changes in version @samp{1.2.1}
@itemize @bullet
@item the source distribution code has been rewritten to be more general
and extended. Packages built using gnustep-make now automatically
have handy targets building tarballs from sources or from CVS imports.
@item implemented support for auto-dependencies, which means that any object
file automatically depends on all the header files which were used to
build it. Only works with newer compilers.
@item implemented INSTALL_AS_USER and INSTALL_AS_GROUP.
@item implemented a strip=yes option.
@item various bug fixes and minor improvements.
@end itemize
@ifclear ANNOUNCE-ONLY
@section Changes in version @samp{1.2.0}
@itemize @bullet
@ -27,8 +43,6 @@ recursive sub-make invocations at all and so they are really fast.
@item Much improved Windows path support
@end itemize
@ifclear ANNOUNCE-ONLY
@section Changes in version @samp{1.0.1}
@itemize @bullet

207
FAQ
View file

@ -1,7 +1,7 @@
GNUstep Frequently Asked Questions with Answers
***********************************************
Last updated 10 December 2001 Please send corrections to
Last updated 1 January 2002 Please send corrections to
<gnustep-maintainer@gnu.org>.
GNUstep General Information
@ -59,17 +59,11 @@ site <http://www.gnustep.org> or it's mirror sites.
What platforms does GNUstep run on?
-----------------------------------
Well tested current builds:
Ix86/GNU-Linux
PPC/GNU-Linux
Recent builds -
Ix86 Unixware-2.? Ix86 FreeBSD-3.0 (ELF) Ix86 OpenBSD-2.4 (static
libraries) Sparc SUNOS-4.1.3 PowerPC GNU/Linux
Probably a few days porting to any other Unix system where current
gcc/egcs compilers and gdb debugger work. See the GNUstep-HOWTO file or
<http://www.gnustep.org/information/machines_toc.html> for more
machines.
See the list of supported platforms at
<http://www.gnustep.org/information/machines_toc.html> for information
on what machines GNUstep builds on and what the status of the ports is.
Probably a few days porting to any other Unix system where current
gcc/egcs compilers and gdb debugger work.
Does GNUstep run on Windows?
----------------------------
@ -228,30 +222,32 @@ window manager) as your window manager.
Is there a web site?
--------------------
See http://www.gnustep.org/ - the main web site.
See <http://www.gnustep.org/>.
When is GNUstep intended to be available?
-----------------------------------------
It's usable now (for an experienced developer). Releases are made
about every six months. However, if you are a serious developer, it's
probably best to use the latest snapshots. See the GNUstep web site
for a release schedule.
It's usable now. Releases are made about every six months. However,
if you are a serious developer, it's probably best to use the latest
snapshots. See the GNUstep web site for a release schedule.
What is usable?
---------------
gstep-make does pretty much what the makefiles in NeXTstep do.
gstep-base (Foundation) stuff should work fine for almost all projects.
gstep-db is only EOF-1.0 compatible but should work ok. gstep-gui
(AppKit) is usable with the xgps backend, and you would probably have
to fix some things in the gui library. Cut-and-paste works, services
work, drag-and-drop works, the NSText classes partially work.
gstep-xgps basic functionality is quite usable. gstep-xdps is mostly
usable. DGS (Display Ghostscript) is usable but slow.
* gstep-make does pretty much what the makefiles in NeXTstep do.
Compiling and Developing
========================
* gstep-base (Foundation) stuff should work fine for almost all
projects.
* gstep-db is only EOF-1.0 compatible but should work ok.
* gstep-gui (AppKit) has a lot working but there is still stuff
missing.
* DGS (Display Ghostscript) is usable but slow.
Compatibility with OPENSTEP/Cocoa/MacOSX
========================================
Can I run NeXT OPENSTEP or Apple Rhapsody programs on GNUstep?
--------------------------------------------------------------
@ -264,20 +260,46 @@ complete GNUstep is at the time.
Is it easy to port OPENSTEP and Rhapsody programs to GNUstep?
-------------------------------------------------------------
It is probably easy for simple programs. You'll have to use nfmake
<http://karl.nfox.com> to translate the PB.prject file to GNUstep
Makefiles, 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
<ftp://ftp.gnustep.org/pub/gnustep/dev-apps>).
It is probably easy for simple programs. There are some portability
tools to make this easier
(<http://www.gnustep.org/resources/source_port.html>), 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 <ftp://ftp.gnustep.org/pub/gnustep/dev-apps>).
Can I transfer archived data from GNUstep to Cocoa?
---------------------------------------------------
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
compatibility difficult. Not to mention the fact that we would
constantly have to keep up with the changes Apple made. Also Apple's
archiving format, as far as we know, would not be compatible between
different machines because of endiness issues, although GNUstep doesn't
have this problem.
Your best bet is to implement your own archiving format that would
work both with GNUstep and Cocoa. Fortuneatly, you don't have to start
from scratch, since this has been essentially done for you in the
nib2gmodel tool, which has an archiver that works both on GNUstep and
Cocoa. It might be nice to split this off into a separate project to
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.
Is there an Interface Builder for GNUstep?
------------------------------------------
There is an Interface Builder for GNUstep called Gorm, but it is in
alpha release, so it may not work perfectly. You can get it from the
GNUstep CVS repository (cvs -z3 checkout Gorm). The Project Manager
ProjectCenter is also new.
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.
Can I use my original NIB files?
--------------------------------
@ -286,8 +308,8 @@ Can I use my original NIB files?
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 that can be compiled under OPENSTEP to convert OPENSTEP nib files
to GNUstep gmodel files.
tool called nib2gmodel that can be compiled under OPENSTEP to convert
OPENSTEP nib files to GNUstep gmodel files.
Will code without NIB files work?
---------------------------------
@ -307,7 +329,7 @@ application that compiles cleanly under both GNUstep and Yellow Box.
Do we have to have the NeXTstep look and feel?
----------------------------------------------
Gnustep is aiming for something like the NeXTstep-3.3 look and feel
Gnustep is aiming for something like the NeXTstep-3.3 look and feel.
This is mostly determined by the gui backend library. In the case of
the two existing backends (xdps and xgps), both are designed to look
like NeXTstep/OPENSTEP. If someone wants to write a backend with a
@ -318,7 +340,7 @@ Can one use the hybrid "Objective-C++"
that one could on the NeXT?
No - at present the GNU compiler (gcc or egcs) does not support
No - at present the GNU compiler (gcc) does not support
"Objective-C++" There are no specific plans to make it do so, but any
volunteers to do it would be welcome.
@ -327,7 +349,7 @@ 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
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
@ -343,15 +365,21 @@ 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.
Also - there is no known recent port to OPENSTEP of the base library.
Also, the GNUstep base library is still being ported to Darwin.
Compiling and Developing
========================
How can I help with GNUstep?
----------------------------
1. Write/debug library code 2. Write documentation 3. Update the
TODO list and library headers 4. Write applications
1. Write/debug library code
Some general advice -
2. Write documentation
3. Update the TODO list and library headers
4. Write applications
Let people know what you are doing. Break your project up into the
smallest units you can. Feed back frequent updates to the maintainers.
@ -381,8 +409,8 @@ How do I start writing code?
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
www.gnustep.org website.
Specific tasks are noted in the developers section on the GNUstep
website.
Once you have coded something, you could always write a testcase and
documentation for it :-)
@ -390,10 +418,9 @@ documentation for it :-)
How do I start writing documentation?
-------------------------------------
Our documentation format is called gsdoc, which is an SGML format
for Objective-C documentation in the same vein as XML. We are also
trying to use Autodoc to self document source code. The gsdoc
translator is included with the base library.
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.
Newcomers could write documentation for individual classes by
comparing the OpenStep specification, the MacOS-X documentation, and
@ -423,11 +450,7 @@ OpenStep specification or the MacOS-X documentation not being present
in the GNustep libraries, it is also helpful to add the method
prototypes to the library header files.
At the moment, send changes to Adam Fedor <fedor@gnu.org> or Richard
Frith-Macdonald <richard@brainstorm.co.uk>
We are hoping to have a system where people can update the list
directly.
Send any changes or additions to <bug-gnustep@gnu.org>.
A beginner can look through the MacOS-X documentation, the OpenStep
specification and the GNUstep source and contribute TODO items.
@ -455,15 +478,12 @@ How do I start writing tests?
either fix the problem, or add it to the task list.
To write testcases, you need to use anonymous CVS to install the
latest gstep-core snapshot you can find. Then checkout the 'tests'
module from CVS. In the 'tests' directory, you will find a regression
testing framework for gstep-base. In order to use this you will also
need a recent (v 1.3.2 or later) copy of Guile (you can get this from a
GNU ftp site) and will need to hacke checked out, built, and installed
the 'guile' package from the GNUstep CVS repository.
At present, there is no such framework for the gui library - If you
are interested in working on one, contact <richard@brainstorm.co.uk>
latest GNUstep snapshots you can find. Then checkout the 'tests' module
from CVS. In the 'tests' directory, you will find a regression testing
framework. In order to use this you will also need a recent (v 1.3.2
or later) copy of Guile (you can get this from a GNU ftp site) and will
need to hacke checked out, built, and installed the 'guile' package
from the GNUstep CVS repository.
How do I start writing applications?
------------------------------------
@ -472,14 +492,6 @@ How do I start writing applications?
applications that have been started, and email their owners to
volunteer to help, or you can start your own project.
If you are starting your own project, you need to - 1. Get the
latest snapshot of GNUstep and build it to use the 'xgps' or 'xdps'
backend library. 2. Look at the example applications (particularly
Ink.app) in the gstep-examples package directory as a basis for your
work. 3. Be prepared to a) ask for help on the gnustep-discuss
mailing list b) fix bugs and implement missing functionality in the
gui and xgps libraries.
How can I help with the GNUstep website?
----------------------------------------
@ -494,11 +506,10 @@ the latest snapshot of the GNUstep core you can find, update it from
the CVS repository, and work with the contents of the appropriate
documentation directory.
If you want to work on other parts of the website - capture the
pages you want to edit in your web browser (at http://www.gnustep.org).
If you can't do that, you can grab a copy of the website via anonymous
CVS. See <http://savannah.gnu.org/cvs/?group_id=99> for instructions on
how to do that.
If you want to work on other parts of the website, you can grab a
copy of the website via anonymous CVS. See
<http://savannah.gnu.org/cvs/?group_id=99> for instructions on how to
do that.
The main task with the website is to figure out which bits are
out-of-date (or wrong) and update/mark-as-outdated as required.
@ -507,16 +518,15 @@ How do I compile GNUstep on my machine?
---------------------------------------
Read the file `GNUstep-HOWTO', which comes with the GNUstep
distribution, and also is available separately on the GNUstep ftp
sites. A PDF version also exists on the web site called
`GnustepInstall.pdf'.
distribution, and also is available separately on the GNUstep web site.
Are there any precompiled packages available?
---------------------------------------------
Check <http://www.gnustep.org/resources/sources.html> for links to
sites with RPMS, and perhaps in the future, Debian packages. In some
cases. You can check the debian site for preconfigured GNUstep packages.
cases. You can check the debian site for preconfigured GNUstep
packages. Also check the BSD sites for GNUstep ports.
What are these type and size warnings?
--------------------------------------
@ -525,7 +535,7 @@ What are these type and size warnings?
/usr/bin/ld: warning: type and size of dynamic symbol
`__objc_class_name_NSConstantString' are not defined
are a common occurence and are do to a mismatch between gcc and ld.
are a common occurence and are due to a mismatch between gcc and ld.
They don't do any harm so they can be safely ignored. Apparently no one
has bothered to fix them yet.
@ -574,10 +584,6 @@ initialization of static instances (such as @""-style string objects).
corresponding NeXT functions; the GNU names conform to the GNU
coding standards.
* GNU's runtime library has a new class heirarchy manipulating
method called `-transmuteClassTo:'. It can change the class of an
instance to a cousin class of the same instance-size.
* NeXT's compiler, `cc', is based on an old version of `gcc'. GNU's
compiler is, of course, the latest version of `gcc', and therefore
contains all the latest enhancements.
@ -587,12 +593,12 @@ Does it allow a mixture of Objective C and C++?
-----------------------------------------------
No. Unlike NeXT's `cc', GNU GCC does not support source files
containing both Objective C and C++. People at Cygnus have mentioned
that they would be willing to do the work--if they were paid for it, of
course. Several people are interested in seeing this happen. Send
email to `discuss-gnustep@gnu.org' if you are interesting in pushing
this issue, so that the efforts of all those people interested can be
coordinated.
containing both Objective C and C++. Apple seems to be willing to
merge their code back into the main GCC project, but this may take some
convincing of the GCC maintainers due to the large number of changes
necessary. Send email to `discuss-gnustep@gnu.org' if you are
interesting in pushing this issue, so that the efforts of all those
people interested can be coordinated.
Also, unlike NeXT's `cc', GNU GCC does not support the `extern
"Objective-C"' construct.
@ -622,12 +628,11 @@ portion of the OpenStep standard (the Foundation library).
What is its current state of development?
-----------------------------------------
It is about 98 percent of the way to having all the OpenStep classes
(and the later OPENSTEP/Rhaspody classes) fully implemented. Normal
work can already be done using the library since the missing 2 percent
are the least-often-used features or are simply not up to date with the
latest MacOS-X spec. Over 60,000 lines of code have already been
written.
GNUstep base is currently stable and implements probably 99% of the
functionality of the OpenStep classes and most all of the new Carbon
classes. Normal work can already be done using the library since the
missing 1 percent are the least-often-used features or are simply not
up to date with the latest Carbon spec.
What are the features of GNU Distributed Objects?
-------------------------------------------------
@ -722,9 +727,7 @@ 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, but should before the
end of 2000 (It's already been fixed in GNU Ghostscript 6.0, just not
released).
channel and compositing currently doesn't work.
What is the relationship between the Display Ghostscript Server and X Windows?
------------------------------------------------------------------------------

View file

@ -1,7 +1,7 @@
GNUstep HOWTO
*************
Last Update: 10 December 2001
Last Update: 1 January 2002
This document explains how to build the different components of the
GNUstep core libraries and GNUstep Launchpad.
@ -99,11 +99,11 @@ depending on the type of system you are using, include:
`openssl'
The openssl library is used to provide support for https
connections by the NSURL and HSURLHandle classes. To enable this
option you need to have the openssl libraries installed and add
the option `--enable-openssl' when running the `configure' script.
Note that the OpenSSL license is not compatible with GPL, so do
not use this option if you want your programs to be GPL compatible.
connections by the NSURL and HSURLHandle classes. This
functionality is compiled as a separate bundle since the OpenSSL
license is not compatible with GPL, and in the hopes that if
someone writes an openssl replacement, it can quickly be used by
creating another bundle.
`libiconv'
Unicode support functions (iconv) come with glibc version 2.1 or
@ -249,7 +249,8 @@ GNUstep Home
============
Set up your home GNUstep directory. This is where user defaults are
kept, and in the future, other files may be kept there.
kept as well as other user configuration files. User installed apps,
libraries, etc are also here (if the default user directory is used).
cd
mkdir GNUstep
@ -292,8 +293,8 @@ app:
* gdomap - Put this in a system startup file, like `/etc/rc.local'
or `/etc/rc.d/rc.local' (customize for your system)
GNUSTEP_SYSTEM_ROOT=/usr/GNUstep
if [ -f $GNUSTEP_SYSTEM_ROOT/Tools/powerpc/linux-gnu/gdomap ]; then
$GNUSTEP_SYSTEM_ROOT/Tools/powerpc/linux-gnu/gdomap
if [ -f $GNUSTEP_SYSTEM_ROOT/Tools/ix86/linux-gnu/gdomap ]; then
$GNUSTEP_SYSTEM_ROOT/Tools/ix86/linux-gnu/gdomap
fi
* gdnc - Put this after executing `GNUstep.sh' in your local .profile
@ -348,7 +349,7 @@ optimization can break some code. The easiest way to do this is when
configuring, `CFLAGS="" ./configure'. Or when building, `make
OPTFLAG=""'.
Darwin 1.0/PowerPC (_Unstable!_)
Darwin 1.x/PowerPC (_Unstable!_)
================================
`Recommended compiler'
@ -359,10 +360,11 @@ Darwin 1.0/PowerPC (_Unstable!_)
`Special Instructions'
GNUstep is being ported to Darwin. The current Darwin compiler
doesn't handle __builtin functions. Other than that it mostly compiles.
Expect some other irritations that haven't been found yet. You need to
use the ObjC runtime that comes with Darwin. To do this configure
(gnustep-make) like this:
doesn't handle __builtin functions, so these are diabled, which may
cause problems with invocations and DO. Other than that it mostly
compiles. Expect some other irritations that haven't been found yet.
You need to use the ObjC runtime that comes with Darwin. To do this
configure (gnustep-make) like this:
./configure --with-library-combo=nx-gnu-gnu

View file

@ -202,9 +202,10 @@ have some file that you read upon login, for example the BASH shell
reads the .bash_profile file in the user's home directory. So you can
add the following lines to that file:
# Setup for the GNUstep environment if [ -f
$GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh ]; then .
$GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh fi
# Setup for the GNUstep environment
if [ -f $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh ]; then
. $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh
fi
This will source in the GNUstep.sh file and set the environment
variables; thus making them available for the user.

20
NEWS
View file

@ -1,7 +1,25 @@
NEWS
****
The currently released version is `1.2.0'.
The currently released version is `1.2.1'.
Changes in version `1.2.1'
==========================
* the source distribution code has been rewritten to be more general
and extended. Packages built using gnustep-make now automatically
have handy targets building tarballs from sources or from CVS
imports.
* implemented support for auto-dependencies, which means that any
object file automatically depends on all the header files which
were used to build it. Only works with newer compilers.
* implemented INSTALL_AS_USER and INSTALL_AS_GROUP.
* implemented a strip=yes option.
* various bug fixes and minor improvements.
Changes in version `1.2.0'
==========================

View file

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