mirror of
https://github.com/gnustep/tools-make.git
synced 2025-04-23 22:33:28 +00:00
* Version 1.10.0
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@19989 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
parent
c6e205fe84
commit
006d2f22b5
11 changed files with 106 additions and 94 deletions
24
ANNOUNCE
24
ANNOUNCE
|
@ -1,7 +1,7 @@
|
|||
Announcement
|
||||
************
|
||||
|
||||
The GNUstep Makefile Package version 1.9.2 is now available.
|
||||
The GNUstep Makefile Package version 1.10.0 is now available.
|
||||
|
||||
What is the GNUstep makefile package?
|
||||
=====================================
|
||||
|
@ -12,17 +12,29 @@ 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.2'
|
||||
==========================
|
||||
Changes in version `1.10.0'
|
||||
===========================
|
||||
|
||||
* Application and Bundles use the latest convention on Apple.
|
||||
* a GNUsteprc file is now automatically created and installed in
|
||||
$GNUSTEP_SYSTEM_ROOT, which sets the system-wide default for the
|
||||
user root directory (default=~/GNUstep, which can be overriden
|
||||
with the `--with-user-root' argument to configure, or by modifying
|
||||
GNUsteprc after configuration.)
|
||||
|
||||
* Improve/Simplify dependency checking when making docs
|
||||
* make_services is not run by GNUstep.sh anymore. You must run this
|
||||
manually now (see the gnustep-gui documentation).
|
||||
|
||||
* Palettes use a plist instead of a strings format file now for the
|
||||
palette.table file.
|
||||
|
||||
* You can use the `--enable-native-objc-exceptions' argument to
|
||||
configure to enable use of built in objc exceptions with compilers
|
||||
that support it.
|
||||
|
||||
Obtaining gnustep-make
|
||||
======================
|
||||
|
||||
You can get the gstep-make-1.9.2.tar.gz distribution file at
|
||||
You can get the gstep-make-1.10.0.tar.gz distribution file at
|
||||
<ftp://ftp.gnustep.org/pub/gnustep/core>
|
||||
|
||||
Please log bug reports on the GNUstep project page
|
||||
|
|
|
@ -1,3 +1,7 @@
|
|||
2004-09-04 Adam Fedor <fedor@gnu.org>
|
||||
|
||||
* Version 1.10.0
|
||||
|
||||
2004-09-03 Adam Fedor <fedor@gnu.org>
|
||||
|
||||
* Add missing GNUsteprc.in
|
||||
|
|
|
@ -61,7 +61,7 @@ Cocoa:
|
|||
@item Do not use Objective-C++
|
||||
@item Do not use Quicktime or other proprietary extension
|
||||
@item You need to convert .nib files (see next question @pxref{Tools for porting})
|
||||
@item Some unfinished classes include NSToolBar and Drawers.
|
||||
@item Some unfinished classes include Drawers.
|
||||
@end itemize
|
||||
|
||||
@node Tools for porting, Can I transfer archived data from GNUstep to Cocoa?, How about porting between Cocoa and GNUstep?, Compatibility
|
||||
|
@ -128,10 +128,10 @@ why this won't work either.
|
|||
@node Is there an Interface Builder for GNUstep?, Can I use my original NIB files?, Does distributed objects work between GNUstep and Cocoa?, Compatibility
|
||||
@subsection 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 download it from
|
||||
the ftp site or via http.
|
||||
The Project Manager ProjectCenter is also available.
|
||||
There is an Interface Builder for GNUstep called Gorm. A lot of work
|
||||
has been put into it and it works very well. You can download it from
|
||||
the ftp site or via http. The Project Manager ProjectCenter is also
|
||||
available.
|
||||
|
||||
@node Can I use my original NIB files?, Can one use the hybrid "Objective-C++", Is there an Interface Builder for GNUstep?, Compatibility
|
||||
@subsection Can I use my original NIB files?
|
||||
|
@ -383,12 +383,8 @@ out-of-date (or wrong) and update/mark-as-outdated as required.
|
|||
@node Why doesn't GDB support Objective-C?, , How can I help with the GNUstep website?, Compiling and Developing
|
||||
@subsection Why doesn't GDB support Objective-C?
|
||||
|
||||
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 versions
|
||||
of gdb (see @url{ftp://ftp.gnustep.org/pub/gnustep/patches}).
|
||||
|
||||
Um, it does. As of GDB 6.0, gdb supports debugging of Objective-C
|
||||
code.
|
||||
|
||||
@c -------------------------------------------------------------------
|
||||
|
||||
|
@ -484,7 +480,7 @@ objects implementations, but, since it is free software, it can be
|
|||
ported to platforms for which other distributed objects implementations
|
||||
are not available.
|
||||
|
||||
[NOTE: The GNU distributed object facilities have the same ease-of-use
|
||||
[ NOTE: The GNU distributed object facilities have the same ease-of-use
|
||||
as NeXT's; be warned, however, that they are not compatible with each
|
||||
other. They have different class hierarchies, different instance
|
||||
variables, different method names, different implementation strategies
|
||||
|
@ -497,7 +493,7 @@ target for the method encoding types and caches the results; GNU
|
|||
NSDistantObject gets the types directly from the local GNU "typed selector"
|
||||
mechanism if the information is known locally and only queries the remote
|
||||
target or caching encoding types when using a method that is not known to
|
||||
the local process. The NSProxy for the remote root object always has name 0
|
||||
the local process. The NSProxy for the remote root object always has name
|
||||
and, once set, you cannot change the root object of a NSConnection; the GNU
|
||||
Proxy for the remote root object has a target address value just like
|
||||
all other Proxy's, and you can change the root object as many times as
|
||||
|
@ -568,7 +564,7 @@ This is a very good backend that draws using the libart package and
|
|||
freetype with near PostScript quality and functionality. At some point
|
||||
it will become the standard.
|
||||
@item w32
|
||||
This backend works on Windows and is currently very alpha quality.
|
||||
This backend works on Windows and is currently beta quality.
|
||||
@end table
|
||||
|
||||
@c ------------------------- GNUstep GUI Library -----------------------
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
@ifclear HOWTO
|
||||
@c Machine Specific, Darwin/ix86, , (DIR)
|
||||
@node Machine Specific
|
||||
@node Machine Specific, Darwin/ix86, , (DIR)
|
||||
@chapter Machines
|
||||
@end ifclear
|
||||
|
||||
|
|
|
@ -9,6 +9,25 @@
|
|||
The currently released version is @samp{@value{GNUSTEP-MAKE-VERSION}}.
|
||||
@end ifclear
|
||||
|
||||
@section Changes in version @samp{1.10.0}
|
||||
|
||||
@itemize @bullet
|
||||
@item a GNUsteprc file is now automatically created and installed in
|
||||
$GNUSTEP_SYSTEM_ROOT, which sets the system-wide default for the user
|
||||
root directory (default=~/GNUstep, which can be overriden with the
|
||||
@code{--with-user-root} argument to configure, or by modifying GNUsteprc
|
||||
after configuration.)
|
||||
@item make_services is not run by GNUstep.sh anymore. You must run this
|
||||
manually now (see the gnustep-gui documentation).
|
||||
@item Palettes use a plist instead of a strings format file now for the
|
||||
palette.table file.
|
||||
@item You can use the @code{--enable-native-objc-exceptions} argument to
|
||||
configure to enable use of built in objc exceptions with compilers that
|
||||
support it.
|
||||
@end itemize
|
||||
|
||||
@ifclear ANNOUNCE-ONLY
|
||||
|
||||
@section Changes in version @samp{1.9.2}
|
||||
|
||||
@itemize @bullet
|
||||
|
@ -16,8 +35,6 @@ The currently released version is @samp{@value{GNUSTEP-MAKE-VERSION}}.
|
|||
@item Improve/Simplify dependency checking when making docs
|
||||
@end itemize
|
||||
|
||||
@ifclear ANNOUNCE-ONLY
|
||||
|
||||
@section Changes in version @samp{1.9.1}
|
||||
|
||||
@itemize @bullet
|
||||
|
|
|
@ -24,7 +24,6 @@ at the (developer) FAQ for more developer oriented questions.
|
|||
* What platforms does GNUstep run on?::
|
||||
* Does GNUstep run on Windows?::
|
||||
* What is GNUstep's position towards KDE and the GNOME project?::
|
||||
* Which Foundation Library can I use?::
|
||||
* How can I get GNUstep?::
|
||||
* How do you run GNUstep?::
|
||||
* Is there a web site?::
|
||||
|
@ -62,7 +61,7 @@ See the list of supported platforms at
|
|||
@url{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.
|
||||
current gcc compilers and gdb debugger work.
|
||||
|
||||
@node Does GNUstep run on Windows?, What is GNUstep's position towards KDE and the GNOME project?, What platforms does GNUstep run on?, GNUstep General Information
|
||||
@subsection Does GNUstep run on Windows?
|
||||
|
@ -70,23 +69,23 @@ current gcc/egcs compilers and gdb debugger work.
|
|||
The primary targets for GNUstep are free 'Unix' platforms such
|
||||
as GNU/Linux.
|
||||
|
||||
That being said, the base library should run on Windows-NT,98 with the
|
||||
That being said, the base library should run on Windows-NT,98,2000 with the
|
||||
Cygwin unix emulation library from Cygnus
|
||||
(http://sourceware.cygnus.com/cygwin/) or the MinGW libraries. At
|
||||
present there are a few problems with networking (Distributed Objects)
|
||||
support, but the library is believed to work.
|
||||
|
||||
The gui library needs a win32 backend library to work under
|
||||
Windows-NT. The backend library is a thin layer that converts the
|
||||
The gui library uses the win32 backend library to work under
|
||||
Windows. The backend library is a thin layer that converts the
|
||||
GNUstep methods to handle drawing of GUI elements to calls to the
|
||||
win32 API. This is a project is in an alpha state.
|
||||
win32 API. This project is in beta.
|
||||
|
||||
The application-wrapper used for GNUstep already allows for multiple
|
||||
binaries to be stored for different systems, so you should be able
|
||||
to write once, deploy anywhere.
|
||||
|
||||
|
||||
@node What is GNUstep's position towards KDE and the GNOME project?, Which Foundation Library can I use?, Does GNUstep run on Windows?, GNUstep General Information
|
||||
@node What is GNUstep's position towards KDE and the GNOME project?, How can I get GNUstep?, Does GNUstep run on Windows?, GNUstep General Information
|
||||
@subsection What is GNUstep's position towards KDE and the GNOME project?
|
||||
|
||||
You can use GNUstep with GNOME and/or KDE. GNUstep displays
|
||||
|
@ -100,20 +99,7 @@ work of developing an OS independent framework from scratch. It
|
|||
gives you lots of basic functionality, from Font Panels to Unicode
|
||||
strings to Distributed Objects.
|
||||
|
||||
@node Which Foundation Library can I use?, How can I get GNUstep?, What is GNUstep's position towards KDE and the GNOME project?, GNUstep General Information
|
||||
@subsection Which Foundation Library can I use?
|
||||
|
||||
That depends ...
|
||||
|
||||
If you only want to use the database package - gnustep-db, you can
|
||||
use either the gnustep base library or libFoundation.
|
||||
|
||||
If you want to develop/use GNUstep gui applications, you must use
|
||||
the gnustep-base library since libFoundation is (13-Feb-2000)
|
||||
missing much essential functionality.
|
||||
|
||||
|
||||
@node How can I get GNUstep?, How do you run GNUstep?, Which Foundation Library can I use?, GNUstep General Information
|
||||
@node How can I get GNUstep?, How do you run GNUstep?, What is GNUstep's position towards KDE and the GNOME project?, GNUstep General Information
|
||||
@subsection How can I get GNUstep?
|
||||
|
||||
Get the HOWTO from
|
||||
|
@ -171,15 +157,15 @@ snapshots.
|
|||
|
||||
@itemize @bullet
|
||||
@item gnustep-make does pretty much what the makefiles in NeXTstep do.
|
||||
@item gnustep-base (Foundation) stuff should work fine for almost all projects.
|
||||
@item gnustep-db is only EOF-1.0 compatible but should work OK.
|
||||
@item gnustep-base (Foundation) works well and is used in production evironments.
|
||||
@item gnustep-gdl2 works well and is used in production evironments.
|
||||
@item gnustep-gui (AppKit) has a lot working but there is still stuff missing.
|
||||
@item DGS (Display Ghostscript) is usable but slow.
|
||||
@end itemize
|
||||
|
||||
What does this mean for users? Many applications will run quite well.
|
||||
Applications that require very complex drawing and some unusual features may
|
||||
not.
|
||||
Applications that require very complex text handling and some unusual
|
||||
features and/or some of the latest additions to Cocoa may not work as
|
||||
well.
|
||||
|
||||
@c ****************************************************************
|
||||
@node Compiling and Installing, Compatibility and Layout, GNUstep General Information, Top
|
||||
|
@ -203,9 +189,8 @@ GNUstep web site.
|
|||
@subsection Are there any precompiled packages available?
|
||||
|
||||
Check @url{http://www.gnustep.org/resources/sources.html} for links to
|
||||
RPMS. Debian packages are also available. You can check the debian
|
||||
site(s) for preconfigured GNUstep packages. Also check the BSD sites for
|
||||
GNUstep ports.
|
||||
RPMS, Debain packages, and BSD ports. Also Windows installers, MacOSX biniaries
|
||||
and others.
|
||||
|
||||
@node What are these type and size warnings?, What are these import warnings?, Are there any precompiled packages available?, Compiling and Installing
|
||||
@subsection What are these type and size warnings?
|
||||
|
@ -281,14 +266,8 @@ this. Actually we're hoping someone will volunteer to do it.
|
|||
|
||||
First of all, GNUstep uses a slightly different directory structure than
|
||||
NeXT or MacOSX. Part of this is historical, part is because we can't do
|
||||
things the same way (see @pxref{Why not use Frameworks?}).
|
||||
|
||||
GNUstep also stores libraries and binaries in subdirectories based on
|
||||
the operating system and cpu. This is so you can compile and store
|
||||
binaries for different systems in the same directory structure. MacOSX
|
||||
uses Fat binaries to accomplish this (another reason we do it
|
||||
differently). If you want, you can get rid of this using the
|
||||
@samp{--enable-flattened} option to the gnustep-make package.
|
||||
things the same way (see @pxref{Why not use Frameworks?}). Although currently
|
||||
the structure is very similar to the it is done in MacOSX.
|
||||
|
||||
@node Why not use Frameworks?, , What's up with the directory structure?, Compatibility and Layout
|
||||
@subsection Why not use Frameworks?
|
||||
|
|
20
FAQ
20
FAQ
|
@ -1,7 +1,7 @@
|
|||
GNUstep Frequently Asked Questions with Answers
|
||||
***********************************************
|
||||
|
||||
Last updated 9 June 2004. Please send corrections to
|
||||
Last updated 3 September 2004. Please send corrections to
|
||||
<gnustep-maintainer@gnu.org>. Also look at the user FAQ for more user
|
||||
oriented questions.
|
||||
|
||||
|
@ -37,7 +37,7 @@ GNUstep yet. Plus there are some other issues. If you start with Cocoa:
|
|||
* You need to convert .nib files (see next question *note Tools for
|
||||
porting::)
|
||||
|
||||
* Some unfinished classes include NSToolBar and Drawers.
|
||||
* Some unfinished classes include Drawers.
|
||||
|
||||
Tools for porting
|
||||
-----------------
|
||||
|
@ -102,8 +102,8 @@ 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 download it from
|
||||
There is an Interface Builder for GNUstep called Gorm. A lot of work
|
||||
has been put into it and it works very well. You can download it from
|
||||
the ftp site or via http. The Project Manager ProjectCenter is also
|
||||
available.
|
||||
|
||||
|
@ -340,11 +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
|
||||
supports debugging of Objective-C code.
|
||||
|
||||
There are patches available on the gnustep web site for earlier
|
||||
versions of gdb (see <ftp://ftp.gnustep.org/pub/gnustep/patches>).
|
||||
Um, it does. As of GDB 6.0, gdb supports debugging of Objective-C code.
|
||||
|
||||
GNU Objective C Compiler and Runtime
|
||||
====================================
|
||||
|
@ -422,7 +418,7 @@ objects implementations, but, since it is free software, it can be
|
|||
ported to platforms for which other distributed objects implementations
|
||||
are not available.
|
||||
|
||||
[NOTE: The GNU distributed object facilities have the same
|
||||
[ NOTE: The GNU distributed object facilities have the same
|
||||
ease-of-use as NeXT's; be warned, however, that they are not compatible
|
||||
with each other. They have different class hierarchies, different
|
||||
instance variables, different method names, different implementation
|
||||
|
@ -435,7 +431,7 @@ the method encoding types and caches the results; GNU NSDistantObject
|
|||
gets the types directly from the local GNU "typed selector" mechanism
|
||||
if the information is known locally and only queries the remote target
|
||||
or caching encoding types when using a method that is not known to the
|
||||
local process. The NSProxy for the remote root object always has name 0
|
||||
local process. The NSProxy for the remote root object always has name
|
||||
and, once set, you cannot change the root object of a NSConnection; the
|
||||
GNU Proxy for the remote root object has a target address value just
|
||||
like all other Proxy's, and you can change the root object as many
|
||||
|
@ -497,7 +493,7 @@ There are several backends currently available:
|
|||
point it will become the standard.
|
||||
|
||||
`w32'
|
||||
This backend works on Windows and is currently very alpha quality.
|
||||
This backend works on Windows and is currently beta quality.
|
||||
|
||||
GNUstep DisplayGhostScript Server
|
||||
=================================
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
GNUstep HOWTO
|
||||
*************
|
||||
|
||||
Last Update: 9 June 2004
|
||||
Last Update: 3 September 2004
|
||||
|
||||
This document explains how to build the different components of the
|
||||
GNUstep core libraries and GNUstep Launchpad.
|
||||
|
@ -507,11 +507,6 @@ FreeBSD 4.x
|
|||
Unknown
|
||||
|
||||
`Special Instructions'
|
||||
If you're using zsh, some shell variables may not be set correctly
|
||||
when executing GNUstep.sh. Try turing on SH_WORD_SPLIT (e.g. 'zsh
|
||||
-sh-word-split', 'zsh -o shwordsplit', 'zsh -y' or by setting
|
||||
'setopt SH_WORD_SPLIT' in one of zsh's startup files.)
|
||||
|
||||
For gcc 3.0.4, make WANT_THREADS_SUPPORT=YES
|
||||
|
||||
For libxml2 2.4.24, make WITHOUT_PYTHON=YES
|
||||
|
@ -743,21 +738,20 @@ This configuration is no longer being tested, but it may still work.
|
|||
`Special Instructions'
|
||||
See the Solaris 2.6 section for more instructions.
|
||||
|
||||
Solaris 2.[67]/Sparc
|
||||
====================
|
||||
Solaris 2.[678]/Sparc
|
||||
=====================
|
||||
|
||||
Tested on Solaris version 6, 7, and 8
|
||||
|
||||
`Recommended compiler'
|
||||
gcc 3.2.1 gcc 2.95.3. Version 2.95.2 has several bugs that GNUstep
|
||||
tickles. gcc 3.04. Not 3.1 - does not compile parts of GNUstep.
|
||||
gcc 3.2.1 or greater gcc 2.95.3. Version 2.95.2 has several bugs
|
||||
that GNUstep tickles. gcc 3.04. Not 3.1 - does not compile parts
|
||||
of GNUstep.
|
||||
|
||||
`Extra libs needed'
|
||||
tiff, Don't use the one in /usr/openwin
|
||||
|
||||
`Special Instructions'
|
||||
No libffi-support unless you use the patch
|
||||
<http://gcc.gnu.org/ml/java-patches/2002-q3/msg00036.html> (not
|
||||
particularly recommended).
|
||||
|
||||
Using a POSIX shell (zsh or bash, which should come with Solaris)
|
||||
is highly recommended. In fact, some functions, such as compiling
|
||||
frameworks, will not work without it.
|
||||
|
|
5
INSTALL
5
INSTALL
|
@ -249,8 +249,3 @@ directory. It may be overridden on a system-wide basis by supplying a
|
|||
# Set up to store GNUstep files directly in my home directory
|
||||
GNUSTEP_USER_ROOT=~
|
||||
|
||||
The system-wide .GNUsteprc file can also contain aa line saying
|
||||
FORCE_USER_ROOT
|
||||
Which will force the value supplied in the system wide file to be
|
||||
used irrespective of any user specific .GNUsteprc file settings.
|
||||
|
||||
|
|
21
NEWS
21
NEWS
|
@ -1,7 +1,26 @@
|
|||
NEWS
|
||||
****
|
||||
|
||||
The currently released version is `1.9.2'.
|
||||
The currently released version is `1.10.0'.
|
||||
|
||||
Changes in version `1.10.0'
|
||||
===========================
|
||||
|
||||
* a GNUsteprc file is now automatically created and installed in
|
||||
$GNUSTEP_SYSTEM_ROOT, which sets the system-wide default for the
|
||||
user root directory (default=~/GNUstep, which can be overriden
|
||||
with the `--with-user-root' argument to configure, or by modifying
|
||||
GNUsteprc after configuration.)
|
||||
|
||||
* make_services is not run by GNUstep.sh anymore. You must run this
|
||||
manually now (see the gnustep-gui documentation).
|
||||
|
||||
* Palettes use a plist instead of a strings format file now for the
|
||||
palette.table file.
|
||||
|
||||
* You can use the `--enable-native-objc-exceptions' argument to
|
||||
configure to enable use of built in objc exceptions with compilers
|
||||
that support it.
|
||||
|
||||
Changes in version `1.9.2'
|
||||
==========================
|
||||
|
|
4
Version
4
Version
|
@ -3,8 +3,8 @@
|
|||
|
||||
# The version number of this release.
|
||||
GNUSTEP_MAKE_MAJOR_VERSION=1
|
||||
GNUSTEP_MAKE_MINOR_VERSION=9
|
||||
GNUSTEP_MAKE_SUBMINOR_VERSION=2
|
||||
GNUSTEP_MAKE_MINOR_VERSION=10
|
||||
GNUSTEP_MAKE_SUBMINOR_VERSION=0
|
||||
GNUSTEP_MAKE_VERSION=${GNUSTEP_MAKE_MAJOR_VERSION}.${GNUSTEP_MAKE_MINOR_VERSION}.${GNUSTEP_MAKE_SUBMINOR_VERSION}
|
||||
|
||||
|
||||
|
|
Loading…
Reference in a new issue