mirror of
https://github.com/gnustep/tools-make.git
synced 2025-04-23 22:33:28 +00:00
Version 1.11.2
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@22196 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Adam Fedor
parent
488a9e55f4
commit
6cc69963c5
10 changed files with 187 additions and 129 deletions
37
ANNOUNCE
37
ANNOUNCE
|
|
@ -1,7 +1,7 @@
|
|||
Announcement
|
||||
************
|
||||
|
||||
The GNUstep Makefile Package version 1.11.1 is now available.
|
||||
The GNUstep Makefile Package version 1.11.2 is now available.
|
||||
|
||||
What is the GNUstep makefile package?
|
||||
=====================================
|
||||
|
|
@ -12,21 +12,40 @@ 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.11.1'
|
||||
Changes in version `1.11.2'
|
||||
===========================
|
||||
|
||||
Part of the previous change was reversed. Now libobjc is still linked
|
||||
with individual applications (as well as the base library), since some
|
||||
operating systems require this to resolve external symbols. However,
|
||||
there is no need to recompile all applications again.
|
||||
The `GNUstep.conf' file is now viewed as the essential determination of
|
||||
the install location for GNUstep libraries, tools and other files.
|
||||
During configuration, this file is read, if it exists, to determine
|
||||
this information. This can still be overriden with environment and
|
||||
command line options, however. See the filesystem documentation in the
|
||||
GNUstep Make Documentation directory for more information.
|
||||
|
||||
Compilation of GNUstep on cygwin was revampled and fixed due to a
|
||||
lot of work by Tom MacSween.
|
||||
You no longer need to source GNUstep.sh in order to compile GNUstep
|
||||
programs. All that is needed is the definition of GNUSTEP_MAKEFILES.
|
||||
You should also have the GNUstep system tools directory in your path.
|
||||
|
||||
All netbsd systems are assumed to use ELF libraries. Support for the
|
||||
old static libs version of netbsd was removed.
|
||||
|
||||
Serveral new options were added to configure to change the location
|
||||
of basic dir locations and basic configuration files. Also, the help was
|
||||
greatly improved. Note that -prefix=/usr/GNUstep/System no longer
|
||||
works. Please use -prefix=/usr/GNUstep or
|
||||
-with-system-root=/usr/GNUstep/System.
|
||||
|
||||
A few more fixes for cygwin are included as well as Windows resource
|
||||
rules.
|
||||
|
||||
Support for ObjC++ has been added. You should list the ObjC++ .mm
|
||||
files in the xxx_OBJCC_FILES variable, and put extra ObjC++ flags in
|
||||
xxx_OBJCCFLAGS or ADDITIONAL_OBJCCFLAGS.
|
||||
|
||||
Obtaining gnustep-make
|
||||
======================
|
||||
|
||||
You can get the gstep-make-1.11.1.tar.gz distribution file at
|
||||
You can get the gstep-make-1.11.2.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 @@
|
|||
2005-12-21 Adam Fedor <fedor@gnu.org>
|
||||
|
||||
* Version 1.11.2
|
||||
|
||||
2005-12-20 Adam Fedor <fedor@gnu.org>
|
||||
|
||||
* configure.ac: Check for objc-gnu in the GNUstep libraries dir.
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Cocoa:
|
|||
@itemize @bullet
|
||||
@item Use #ifndef GNUSTEP for Apple only code.
|
||||
@item Do not use CoreFoundation
|
||||
@item Do not use Objective-C++
|
||||
@item Do not use Objective-C++ (except with gcc 4.1 or later)
|
||||
@item Do not use Quicktime or other proprietary extension
|
||||
@item You need to convert .nib files (see next question @pxref{Tools for porting})
|
||||
@end itemize
|
||||
|
|
@ -119,12 +119,9 @@ 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. Fortunately, 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.
|
||||
The new keyed archiving using XML file formats is much more portable,
|
||||
and GNUstep is trying to maintain compatibility with Apple with this
|
||||
type of archiving.
|
||||
|
||||
@node Does distributed objects work between GNUstep and Cocoa?, Is there an Interface Builder for GNUstep?, Can I transfer archived data from GNUstep to Cocoa?, Compatibility
|
||||
@subsection Does distributed objects work between GNUstep and Cocoa?
|
||||
|
|
@ -150,12 +147,16 @@ archive format (which can be edited by Gorm). There IS a conversion
|
|||
tool called nib2gmodel that can be compiled under OPENSTEP to convert
|
||||
nib files to GNUstep gmodel files.
|
||||
|
||||
Newer nib files use XML format keyed archiving and may possibly be
|
||||
transportable, although differences in class and ivar layout may still
|
||||
make this difficult.
|
||||
|
||||
@node Can one use the hybrid "Objective-C++", Is there a plan to support Java/YellowBox Bindings?, Can I use my original NIB files?, Compatibility
|
||||
@subsection 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.
|
||||
"Objective-C++". Soon to br released gcc 4.1 will have this support, but
|
||||
it is still unclear how robust it will be.
|
||||
|
||||
@node Is there a plan to support Java/YellowBox Bindings?, What if I compile GNUstep under OPENSTEP/MacOS X?, Can one use the hybrid "Objective-C++", Compatibility
|
||||
@subsection Is there a plan to support the Java/YellowBox Bindings?
|
||||
|
|
@ -179,7 +180,7 @@ 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
|
||||
You can, however, use a GNUstep program with an X11 server
|
||||
running on MacOSX.
|
||||
|
||||
@node Is the Objective C API for GTK related?, How about implementing parts of the Application Kit with GTK?, What if I compile GNUstep under OPENSTEP/MacOS X?, Compatibility
|
||||
|
|
@ -362,13 +363,9 @@ good idea to get in touch with Adam or Richard to coordinate efforts.
|
|||
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
|
||||
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 check-out,
|
||||
built, and installed the 'guile' package from the GNUstep CVS repository.
|
||||
To write testcases, you need to use anonymous CVS to install the latest
|
||||
GNUstep snapshots you can find. Then checkout the
|
||||
'gnustep/dev-apps/test/Testsuite' module from CVS.
|
||||
|
||||
@node How do I start writing applications?, How can I help with the GNUstep website?, How do I start writing tests?, Compiling and Developing
|
||||
@subsection How do I start writing applications?
|
||||
|
|
@ -412,11 +409,9 @@ code.
|
|||
|
||||
@menu
|
||||
* What is the Objective C Runtime?::
|
||||
* Does it allow a mixture of Objective C and C++::
|
||||
* Where can I find more information?::
|
||||
@end menu
|
||||
|
||||
@node What is the Objective C Runtime?, Does it allow a mixture of Objective C and C++, GNU Objective C Compiler and Runtime, GNU Objective C Compiler and Runtime
|
||||
@node What is the Objective C Runtime?, , GNU Objective C Compiler and Runtime, GNU Objective C Compiler and Runtime
|
||||
@subsection What is the Objective C Runtime?
|
||||
|
||||
The Objective C Runtime Library provides C functions and data structures
|
||||
|
|
@ -444,20 +439,12 @@ works with both runtimes. You should use functions there or use OpenStep
|
|||
Foundation methods/functions instead of the basic
|
||||
runtime functions so that you code can run with either system.
|
||||
|
||||
Apple has recently added new functionality to their runtime, including
|
||||
built-in exception handling, etc. Hopefully these will be ported to the
|
||||
GNU runtime in the future.
|
||||
|
||||
@end itemize
|
||||
|
||||
@node Does it allow a mixture of Objective C and C++, Where can I find more information?, What is the Objective C Runtime?, GNU Objective C Compiler and Runtime
|
||||
@subsection Does it allow a mixture of Objective C and C++?
|
||||
|
||||
No.
|
||||
See @pxref{Can one use the hybrid "Objective-C++"}
|
||||
|
||||
@node Where can I find more information?, , Does it allow a mixture of Objective C and C++, GNU Objective C Compiler and Runtime
|
||||
@subsection Where can I find more information?
|
||||
|
||||
The FAQ associated with the newsgroup @samp{comp.lang.objective-c}
|
||||
contains more information about GNU Objective C.
|
||||
|
||||
@c ------------- GNU Compiler and Objective C Runtime Library -------
|
||||
|
||||
@node GNUstep Base Library, GNUstep GUI Library, GNU Objective C Compiler and Runtime, Top
|
||||
|
|
@ -500,14 +487,14 @@ ported to platforms for which other distributed objects implementations
|
|||
are not available.
|
||||
|
||||
[ 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
|
||||
as Apple'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
|
||||
and different network message formats. You cannot communicate with a
|
||||
NeXT NSConnection using a GNU NSConnection.
|
||||
Apple NSConnection using a GNU NSConnection.
|
||||
|
||||
Here are some differences between GNU distributed objects and NeXT's
|
||||
distributed objects: NeXT NSDistantObject asks it's remote
|
||||
Here are some differences between GNU distributed objects and Apple's
|
||||
distributed objects: Apple NSDistantObject asks it's remote
|
||||
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
|
||||
|
|
@ -575,15 +562,18 @@ There are several backends currently available:
|
|||
|
||||
@table @samp
|
||||
@item xlib
|
||||
This is the standard backend that runs on X11 and uses standard xlib
|
||||
This backend runs on X11 and uses standard xlib
|
||||
calls for implementing drawing. It works well, but is limited in many
|
||||
areas due to the limitations of xlib drawing.
|
||||
@item art
|
||||
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.
|
||||
freetype with near PostScript quality and functionality. It is currently
|
||||
the standard backend (as long as the required libraries are installed).
|
||||
@item w32
|
||||
This backend works on Windows and is currently beta quality.
|
||||
This backend works on Windows and uses basic Windows drawing
|
||||
@item cairo
|
||||
An up-and-coming backend. It still relies on unpublished functions in
|
||||
the cairo library so using it is not for the beginner.
|
||||
@end table
|
||||
|
||||
@c ------------------------- GNUstep GUI Library -----------------------
|
||||
|
|
@ -617,7 +607,7 @@ 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.
|
||||
doesn't work.
|
||||
|
||||
@node What is the relationship between the Display Ghostscript Server and X Windows?, , What is DGSs current state of development?, GNUstep DisplayGhostScript Server
|
||||
@subsection What is the relationship between the Display Ghostscript Server and X Windows?
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ any later version published by the Free Software Foundation.
|
|||
Copyright (C) 1996 - 2002 Free Software Foundation, Inc.
|
||||
|
||||
Permission is granted to copy, distribute and/or modify this document
|
||||
under the terms of the GNU Free Documentation License, Version 1.1 or
|
||||
under the terms of the GNU Public License, Version 1.0 or
|
||||
any later version published by the Free Software Foundation.
|
||||
@end format
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,38 @@
|
|||
The currently released version is @samp{@value{GNUSTEP-MAKE-VERSION}}.
|
||||
@end ifclear
|
||||
|
||||
@section Changes in version @samp{1.11.2}
|
||||
|
||||
The @file{GNUstep.conf} file is now viewed as the essential
|
||||
determination of the install location for GNUstep libraries, tools and
|
||||
other files. During configuration, this file is read, if it exists, to
|
||||
determine this information. This can still be overriden with
|
||||
environment and command line options, however. See the filesystem
|
||||
documentation in the GNUstep Make Documentation directory for more
|
||||
information.
|
||||
|
||||
You no longer need to source GNUstep.sh in order to compile GNUstep
|
||||
programs. All that is needed is the definition of
|
||||
GNUSTEP_MAKEFILES. You should also have the GNUstep system tools
|
||||
directory in your path.
|
||||
|
||||
All netbsd systems are assumed to use ELF libraries. Support for the old
|
||||
static libs version of netbsd was removed.
|
||||
|
||||
Serveral new options were added to configure to change the location of
|
||||
basic dir locations and basic configuration files. Also, the help was
|
||||
greatly improved. Note that --prefix=/usr/GNUstep/System no longer
|
||||
works. Please use --prefix=/usr/GNUstep or
|
||||
--with-system-root=/usr/GNUstep/System.
|
||||
|
||||
A few more fixes for cygwin are included as well as Windows resource rules.
|
||||
|
||||
Support for ObjC++ has been added. You should list the ObjC++ .mm
|
||||
files in the xxx_OBJCC_FILES variable, and put extra ObjC++ flags in
|
||||
xxx_OBJCCFLAGS or ADDITIONAL_OBJCCFLAGS.
|
||||
|
||||
@ifclear ANNOUNCE-ONLY
|
||||
|
||||
@section Changes in version @samp{1.11.1}
|
||||
|
||||
Part of the previous change was reversed. Now libobjc is still linked
|
||||
|
|
@ -19,8 +51,6 @@ there is no need to recompile all applications again.
|
|||
Compilation of GNUstep on cygwin was revampled and fixed due to a lot of
|
||||
work by Tom MacSween.
|
||||
|
||||
@ifclear ANNOUNCE-ONLY
|
||||
|
||||
@section Changes in version @samp{1.11.0}
|
||||
|
||||
NOTE: The libobjc library is now linked in with the base library and NOT with
|
||||
|
|
|
|||
|
|
@ -35,8 +35,9 @@ at the (developer) FAQ for more developer oriented questions.
|
|||
@subsection What is GNUstep?
|
||||
|
||||
GNUstep is the Free Software Foundation's effort to implement NeXT
|
||||
Software, Inc.'s (now Apple Computer, Inc.) OpenStep Standard. The project is
|
||||
not finished, so some parts are not as polished as they could be.
|
||||
Software, Inc.'s (now Apple Computer, Inc.) OpenStep Standard. Also we
|
||||
are building developer and user applications based on this standard which
|
||||
may someday be used to form a complete desktop experience.
|
||||
|
||||
@node What is the OpenStep standard?, What platforms does GNUstep run on?, What is GNUstep?, GNUstep General Information
|
||||
@subsection What is the OpenStep standard?
|
||||
|
|
@ -45,11 +46,12 @@ OpenStep is an Application Programming Interface (API) for creating
|
|||
applications using the Objective-C language. It was published by NeXT
|
||||
Computer, Inc. in 1994.
|
||||
|
||||
OpenStep consists of three parts: the @samp{Foundation Kit}, a library of
|
||||
non-graphical objects; the @samp{Application Kit}, a library of objects useful
|
||||
in creating graphical applications; and the @samp{Display PostScript System}, an
|
||||
interface for drawing to the screen using the PostScript graphics
|
||||
language.
|
||||
OpenStep consists of three parts: the @samp{Foundation Kit}, a library
|
||||
of non-graphical objects; the @samp{Application Kit}, a library of
|
||||
objects useful in creating graphical applications; and the @samp{Display
|
||||
PostScript System} (DPS), an interface for drawing to the screen using
|
||||
the PostScript graphics language. DPS support is not being persued at
|
||||
this time however.
|
||||
|
||||
You can obtain a copy of the OpenStep standard from the GNUstep web site
|
||||
@url{http://www.gnustep.org} or it's mirror sites.
|
||||
|
|
@ -58,7 +60,7 @@ You can obtain a copy of the OpenStep standard from the GNUstep web site
|
|||
@subsection What platforms does GNUstep run on?
|
||||
|
||||
See the list of supported platforms at
|
||||
@url{http://www.gnustep.org/information/machines_toc.html} for
|
||||
@url{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 compilers and gdb debugger work.
|
||||
|
|
@ -72,19 +74,13 @@ as GNU/Linux and FreeBSD.
|
|||
That being said, the base library should run on Windows NT, 98, 2000, and XP
|
||||
with the Cygwin UNIX system-emulation environment from Cygnus
|
||||
(@url{http://www.cygwin.com/}), or the MinGW environment
|
||||
(@url{http://www.mingw.org}). At present there are a few problems with
|
||||
networking (distributed objects) support, but the library is believed to work.
|
||||
(@url{http://www.mingw.org}).
|
||||
|
||||
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
|
||||
Windows API. This project is currently 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?, 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?
|
||||
|
||||
|
|
@ -102,14 +98,10 @@ strings to distributed objects.
|
|||
@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
|
||||
@url{http://www.gnustep.org/resources/documentation/GNUstep-HOWTO}
|
||||
Get the latest release from @url{ftp://ftp.gnustep.org}. If you're
|
||||
really adventurous, get the latest snapshot by anonymous ftp from
|
||||
@url{ftp://ftp.gnustep.org/pub/daily-snapshots}
|
||||
|
||||
Use anonymous CVS to keep up to date - instructions are in the
|
||||
HOWTO.
|
||||
Many distributions include packaged versions of GNUstep (Debian,
|
||||
etc). To compile from sratch, download the GNUstep Startup package or
|
||||
get the HOWTO from @url{gnustep-howto_toc.html}. Get the latest releases
|
||||
from @url{ftp://ftp.gnustep.org/pub/gnustep/core}.
|
||||
|
||||
@node How do you run GNUstep?, Is there a web site?, How can I get GNUstep?, GNUstep General Information
|
||||
@subsection How do you run GNUstep?
|
||||
|
|
@ -155,12 +147,10 @@ snapshots.
|
|||
@node What is usable?, , When is GNUstep intended to be available?, GNUstep General Information
|
||||
@subsection What is usable?
|
||||
|
||||
@itemize @bullet
|
||||
@item gnustep-make does pretty much what the makefiles in NEXTSTEP do.
|
||||
@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 (Application Kit) has a lot working but there is still stuff missing.
|
||||
@end itemize
|
||||
Most of GNUstep is quite usable and there are many complex applications
|
||||
that work well. However, GNUstep does not completely track the latest
|
||||
changes that Apple makes to their interface and there are still some
|
||||
parts that need some work).
|
||||
|
||||
What does this mean for users? Many applications will run quite well.
|
||||
Applications that require very complex text handling and some unusual
|
||||
|
|
@ -259,7 +249,7 @@ Although we don't want to force anyone into this, a lot of the power and
|
|||
ease of use comes from this feel. The look of GNUstep is something
|
||||
different --- buttons and other widgets can look different but still act
|
||||
the same way. We hope to implement themes which will allow
|
||||
this. Actually we're hoping someone will volunteer to do it.
|
||||
this.
|
||||
|
||||
@node What's up with the directory structure?, Why not use framework bundles?, Do we have to have the NEXTSTEP look and feel?, Compatibility and Layout
|
||||
@subsection What's up with the directory structure?
|
||||
|
|
|
|||
79
FAQ
79
FAQ
|
|
@ -1,7 +1,7 @@
|
|||
GNUstep Frequently Asked Questions with Answers
|
||||
***********************************************
|
||||
|
||||
Last updated 18 September 2005. Please send corrections to
|
||||
Last updated 20 December 2005. Please send corrections to
|
||||
<gnustep-maintainer@gnu.org>. Also look at the user FAQ for more user
|
||||
oriented questions.
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ GNUstep yet. Plus there are some other issues. If you start with Cocoa:
|
|||
|
||||
* Do not use CoreFoundation
|
||||
|
||||
* Do not use Objective-C++
|
||||
* Do not use Objective-C++ (except with gcc 4.1 or later)
|
||||
|
||||
* Do not use Quicktime or other proprietary extension
|
||||
|
||||
|
|
@ -92,12 +92,9 @@ 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. Fortunately, 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.
|
||||
The new keyed archiving using XML file formats is much more portable,
|
||||
and GNUstep is trying to maintain compatibility with Apple with this
|
||||
type of archiving.
|
||||
|
||||
Does distributed objects work between GNUstep and Cocoa?
|
||||
--------------------------------------------------------
|
||||
|
|
@ -123,12 +120,16 @@ archive format (which can be edited by Gorm). There IS a conversion
|
|||
tool called nib2gmodel that can be compiled under OPENSTEP to convert
|
||||
nib files to GNUstep gmodel files.
|
||||
|
||||
Newer nib files use XML format keyed archiving and may possibly be
|
||||
transportable, although differences in class and ivar layout may still
|
||||
make this difficult.
|
||||
|
||||
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.
|
||||
Soon to br released gcc 4.1 will have this support, but it is still
|
||||
unclear how robust it will be.
|
||||
|
||||
Is there a plan to support the Java/YellowBox Bindings?
|
||||
-------------------------------------------------------
|
||||
|
|
@ -151,8 +152,8 @@ 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.
|
||||
You can, however, use a GNUstep program with an X11 server running
|
||||
on MacOSX.
|
||||
|
||||
Is the Objective C API for GTK related?
|
||||
---------------------------------------
|
||||
|
|
@ -317,12 +318,8 @@ 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
|
||||
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 check-out, built, and installed the 'guile' package from the
|
||||
GNUstep CVS repository.
|
||||
latest GNUstep snapshots you can find. Then checkout the
|
||||
'gnustep/dev-apps/test/Testsuite' module from CVS.
|
||||
|
||||
How do I start writing applications?
|
||||
------------------------------------
|
||||
|
|
@ -389,17 +386,10 @@ initialization of static instances (such as @""-style string objects).
|
|||
instead of the basic runtime functions so that you code can run
|
||||
with either system.
|
||||
|
||||
Apple has recently added new functionality to their runtime,
|
||||
including built-in exception handling, etc. Hopefully these will
|
||||
be ported to the GNU runtime in the future.
|
||||
|
||||
Does it allow a mixture of Objective C and 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.
|
||||
|
||||
GNUstep Base Library
|
||||
====================
|
||||
|
|
@ -435,14 +425,14 @@ ported to platforms for which other distributed objects implementations
|
|||
are not available.
|
||||
|
||||
[ 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 and different network message formats. You cannot
|
||||
communicate with a NeXT NSConnection using a GNU NSConnection.
|
||||
ease-of-use as Apple'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 and different network message formats. You
|
||||
cannot communicate with a Apple NSConnection using a GNU NSConnection.
|
||||
|
||||
Here are some differences between GNU distributed objects and NeXT's
|
||||
distributed objects: NeXT NSDistantObject asks it's remote target for
|
||||
Here are some differences between GNU distributed objects and Apple's
|
||||
distributed objects: Apple NSDistantObject asks it's remote 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
|
||||
|
|
@ -499,17 +489,22 @@ What is the current state of development of the back-ends?
|
|||
There are several backends currently available:
|
||||
|
||||
`xlib'
|
||||
This is the standard backend that runs on X11 and uses standard
|
||||
xlib calls for implementing drawing. It works well, but is limited
|
||||
in many areas due to the limitations of xlib drawing.
|
||||
This backend runs on X11 and uses standard xlib calls for
|
||||
implementing drawing. It works well, but is limited in many areas
|
||||
due to the limitations of xlib drawing.
|
||||
|
||||
`art'
|
||||
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.
|
||||
freetype with near PostScript quality and functionality. It is
|
||||
currently the standard backend (as long as the required libraries
|
||||
are installed).
|
||||
|
||||
`w32'
|
||||
This backend works on Windows and is currently beta quality.
|
||||
This backend works on Windows and uses basic Windows drawing
|
||||
|
||||
`cairo'
|
||||
An up-and-coming backend. It still relies on unpublished functions
|
||||
in the cairo library so using it is not for the beginner.
|
||||
|
||||
GNUstep DisplayGhostScript Server
|
||||
=================================
|
||||
|
|
@ -536,7 +531,7 @@ 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.
|
||||
doesn't work.
|
||||
|
||||
What is the relationship between the Display Ghostscript Server and X Windows?
|
||||
------------------------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
GNUstep HOWTO
|
||||
*************
|
||||
|
||||
Last Update: 18 September 2005
|
||||
Last Update: 20 December 2005
|
||||
|
||||
This document explains how to build the different components of the
|
||||
GNUstep core libraries and GNUstep Launchpad.
|
||||
|
|
@ -9,7 +9,7 @@
|
|||
Copyright (C) 1996 - 2002 Free Software Foundation, Inc.
|
||||
|
||||
Permission is granted to copy, distribute and/or modify this document
|
||||
under the terms of the GNU Free Documentation License, Version 1.1 or
|
||||
under the terms of the GNU Public License, Version 1.0 or
|
||||
any later version published by the Free Software Foundation.
|
||||
|
||||
Introduction
|
||||
|
|
|
|||
32
NEWS
32
NEWS
|
|
@ -1,7 +1,37 @@
|
|||
NEWS
|
||||
****
|
||||
|
||||
The currently released version is `1.11.1'.
|
||||
The currently released version is `1.11.2'.
|
||||
|
||||
Changes in version `1.11.2'
|
||||
===========================
|
||||
|
||||
The `GNUstep.conf' file is now viewed as the essential determination of
|
||||
the install location for GNUstep libraries, tools and other files.
|
||||
During configuration, this file is read, if it exists, to determine
|
||||
this information. This can still be overriden with environment and
|
||||
command line options, however. See the filesystem documentation in the
|
||||
GNUstep Make Documentation directory for more information.
|
||||
|
||||
You no longer need to source GNUstep.sh in order to compile GNUstep
|
||||
programs. All that is needed is the definition of GNUSTEP_MAKEFILES.
|
||||
You should also have the GNUstep system tools directory in your path.
|
||||
|
||||
All netbsd systems are assumed to use ELF libraries. Support for the
|
||||
old static libs version of netbsd was removed.
|
||||
|
||||
Serveral new options were added to configure to change the location
|
||||
of basic dir locations and basic configuration files. Also, the help was
|
||||
greatly improved. Note that -prefix=/usr/GNUstep/System no longer
|
||||
works. Please use -prefix=/usr/GNUstep or
|
||||
-with-system-root=/usr/GNUstep/System.
|
||||
|
||||
A few more fixes for cygwin are included as well as Windows resource
|
||||
rules.
|
||||
|
||||
Support for ObjC++ has been added. You should list the ObjC++ .mm
|
||||
files in the xxx_OBJCC_FILES variable, and put extra ObjC++ flags in
|
||||
xxx_OBJCCFLAGS or ADDITIONAL_OBJCCFLAGS.
|
||||
|
||||
Changes in version `1.11.1'
|
||||
===========================
|
||||
|
|
|
|||
2
Version
2
Version
|
|
@ -4,7 +4,7 @@
|
|||
# The version number of this release.
|
||||
GNUSTEP_MAKE_MAJOR_VERSION=1
|
||||
GNUSTEP_MAKE_MINOR_VERSION=11
|
||||
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}
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue