mirror of
https://github.com/gnustep/tools-make.git
synced 2025-04-23 22:33:28 +00:00
New manpages from Dennis, and changes to makefile to install/uninstall them, plus a few enhancements in uninstall
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@25788 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Nicola Pero
parent
7783e60fdb
commit
26ce343a5f
8 changed files with 647 additions and 174 deletions
17
ChangeLog
17
ChangeLog
|
|
@ -1,3 +1,20 @@
|
|||
2007-12-26 Nicola Pero <nicola.pero@meta-innovation.com>
|
||||
|
||||
* GNUmakefile.in (install): Install the new debugapp.1,
|
||||
gnustep-config.1, opentool.1 and library-combo.7 manpages.
|
||||
(uninstall): Uninstall them.
|
||||
(uninstall): Remove mandir, mandir/man1, mandir/man7, tooldir and
|
||||
GNUSTEP_CONFIG_FILE_DIR if empty.
|
||||
|
||||
2007-12-26 Dennis Leeuw <dleeuw@made-it.com>
|
||||
|
||||
* Documentation/debugapp.1: New file.
|
||||
* Documentation/gnustep-config.1: New file.
|
||||
* Documentation/opentool.1: New file.
|
||||
* Documentation/library-combo.7: New file.
|
||||
* Documentation/openapp.1: Rewritten.
|
||||
* Documentation/GNUstep.7: Rewritten.
|
||||
|
||||
2007-12-20 Adam Fedor <fedor@gnu.org>
|
||||
|
||||
* Master/nsis.make: Generalize to install in other than Applications.
|
||||
|
|
|
|||
|
|
@ -1,66 +1,74 @@
|
|||
.\"GNUstep(7) man page
|
||||
.\"put together by Martin Brecher <martin@gnustep.de>
|
||||
.\"
|
||||
.\"Process this file with
|
||||
.\"groff -man -Tascii GNUstep.7
|
||||
.\"
|
||||
.TH GNUSTEP 7 "August 2003" GNUstep "GNUstep System Manual"
|
||||
.\" Process this file with
|
||||
.\" groff -man -Tascii GNUstep.7
|
||||
.\"
|
||||
.TH GNUstep 7 "15/12/2007" gnustep-core "GNUstep System Manual"
|
||||
.SH NAME
|
||||
GNUstep \- A free implementation of the OpenStep standard
|
||||
|
||||
.SH DESCRIPTION
|
||||
GNUstep provides an Object-Oriented application development framework
|
||||
and toolset for use on a wide variety of computer platforms.
|
||||
GNUstep is based on the original OpenStep specification provided by
|
||||
NeXT, Inc. (now Apple).
|
||||
.B GNUstep
|
||||
provides an Object-Oriented application development framework and toolset for use on a wide variety of computer platforms.
|
||||
.B GNUstep
|
||||
is based on the original OpenStep specification provided by NeXT, Inc. (now Apple).
|
||||
.P
|
||||
GNUstep is written in Objective-C, an object-oriented superset of the C
|
||||
programming language, similar to SmallTalk. However there exist a number
|
||||
of brigdes and interfaces to develop GNUstep programs using other languages
|
||||
like JAVA or Ruby.
|
||||
.B GNUstep
|
||||
is written in Objective-C, an object-oriented superset of the C programming language, similar to SmallTalk. However there exist a number of brigdes and interfaces to develop
|
||||
.B GNUstep
|
||||
programs using other languages like JAVA or Ruby.
|
||||
|
||||
.P
|
||||
.B The GNUstep Core System
|
||||
.P
|
||||
The GNUstep core system consists of the following parts:
|
||||
.IP gnustep-make
|
||||
A set of scripts and makefiles that heavily ease the
|
||||
creation and maintenance of software projects.
|
||||
.IP gnustep-base
|
||||
The FoundationKit libraries for non-GUI tools providing
|
||||
everything from string
|
||||
and array classes, filemanager classes to distributed objects.
|
||||
.IP gnustep-gui
|
||||
The ApplicationKit containing widgets, workspace classes and
|
||||
means for
|
||||
applications to interact with the user. This is the frontend of
|
||||
GNUstep's GUI part.
|
||||
.IP gnustep-back
|
||||
This is the backend of GNUstep's GUI part which does the actual
|
||||
rendering and event handling. It acts as a layer between
|
||||
gnustep-gui and the operating/drawing system. Backends exist
|
||||
for X11 (one using libart, one using xlib drawing) and win32.
|
||||
|
||||
Apart from the above, there exist a number of addon libraries, like Renaissance
|
||||
which allows developers to specify an application's user interface in xml.
|
||||
For database access, there is gdl2 - the GNUstep Database Library.
|
||||
Please refer to the GNUstep website for more information.
|
||||
|
||||
|
||||
GNUstep is self-containing. That means that all GNUstep applications, tools,
|
||||
libraries and add-ons are installed into the GNUstep directory hierarchy.
|
||||
The
|
||||
.B GNUstep
|
||||
core system consists of the following parts, which are jointly refered to as
|
||||
.I gnustep-core
|
||||
:
|
||||
.TP
|
||||
.I gnustep-make
|
||||
A set of scripts and makefiles that heavily ease the creation and maintenance of software projects.
|
||||
.TP
|
||||
.I gnustep-base
|
||||
The FoundationKit libraries for non-GUI tools providing everything from string and array classes, filemanager classes to distributed objects.
|
||||
.TP
|
||||
.I gnustep-gui
|
||||
The ApplicationKit containing widgets, workspace classes and means for applications to interact with the user. This is the frontend of \fBGNUstep\fR's GUI part.
|
||||
.TP
|
||||
.I gnustep-back
|
||||
This is the backend of
|
||||
.BR GNUstep 's
|
||||
GUI part which does the actual rendering and event handling. It acts as a layer between gnustep-gui and the operating/drawing system. Backends exist for X11 (one using cairo, one using libart, one using xlib drawing) and win32.
|
||||
.PP
|
||||
Apart from the above, there exist a number of addon libraries, like
|
||||
.B Renaissance
|
||||
which allows developers to specify an application's user interface in xml. For database access, there is
|
||||
.B GDL2
|
||||
\- the GNUstep Database Library. Please refer to the
|
||||
.B GNUstep
|
||||
website for more information.
|
||||
.PP
|
||||
.B GNUstep
|
||||
per default is self-contained. That means that all
|
||||
.B GNUstep
|
||||
applications, tools, libraries and add-ons are installed into the
|
||||
.B GNUstep
|
||||
directory hierarchy. However as of
|
||||
.I gnustep-make-2.0.0
|
||||
it is also possible to install everything in compliance with other filesystem hierarchies. See the
|
||||
.I FilesystemLayouts
|
||||
directory in the source package of
|
||||
.I gnustep-make
|
||||
for more information.
|
||||
.PP
|
||||
There are four domains which are searched for files: the System domain, which
|
||||
should only contain the core system files, the Local domain which stores all
|
||||
that has later been installed on the system, the Network domain which should
|
||||
be used for importing data from a remote system, and the User domain which resides in the user's home directory (mostly ~/GNUstep).
|
||||
See the filesystem.texi document for more information.
|
||||
be used for importing data from a remote system, and the User domain which resides in the user's home directory (mostly
|
||||
.IR ~/GNUstep ).
|
||||
.PP
|
||||
A complete description of the default
|
||||
.B GNUstep
|
||||
layout can be found in the
|
||||
.IR filesystem.pdf .
|
||||
|
||||
.P
|
||||
.B Some Basic Terms:
|
||||
|
||||
.P
|
||||
.B Tools and Applications
|
||||
.P
|
||||
.SS TOOLS AND APPLICATIONS
|
||||
In the world of GNUstep the term
|
||||
.I tool
|
||||
refers to command line programs whereas
|
||||
|
|
@ -73,26 +81,37 @@ reside in the domains' Tools folder,
|
|||
can be
|
||||
found in the domains' Applications folder.
|
||||
|
||||
Applications are either launched using the openapp command or from the
|
||||
Workspace.
|
||||
Applications are either launched using the
|
||||
.B openapp
|
||||
command or from the Workspace.
|
||||
|
||||
|
||||
.P
|
||||
.B Services
|
||||
.P
|
||||
In GNUstep applications globally offer functionality to other applications
|
||||
through
|
||||
.I services
|
||||
. They can be reached through the Services menu entry in an
|
||||
application's main menu.
|
||||
Apart from
|
||||
.SS SERVICES
|
||||
.RB "In " GNUstep
|
||||
applications globally offer functionality to other applications through
|
||||
.IR services .
|
||||
They can be reached through the Services menu entry in an
|
||||
application's main menu. Apart from
|
||||
.I services
|
||||
offered by applications, there may
|
||||
be programs whose sole purpose is the offering of services. They can be found
|
||||
in the domains' Libary/Services folders.
|
||||
.PP
|
||||
The
|
||||
.B make_services
|
||||
tool makes sure the services are known to other applications when a application is newly installed.
|
||||
|
||||
.SS BUNDLES
|
||||
A bundle is a collection of resources making up a discrete package for use. There are currently three types of bundles: applications, frameworks and loadable bundles.
|
||||
.P
|
||||
.B The Workspace
|
||||
A loadable bundle is a kind of plug-in. There are two types of loadable bundles, namely plug-ins and palettes. The plug-in is noramlly refered to as a bundle, which can make it a bit confusing. A plug-in is a bundle that can be loaded by an application to provide additional functionality, while a palette is a plug-in for
|
||||
.BR GORM ,
|
||||
the interface builder. A palette is used to extend
|
||||
.B GORM
|
||||
with custom UI objects. Palettes have a
|
||||
.I .palette
|
||||
extension.
|
||||
|
||||
.SS THE WORKSPACE
|
||||
.P
|
||||
The central place of the user interface is the
|
||||
.I Workspace
|
||||
|
|
@ -102,46 +121,66 @@ which acts as an interface between the user and parts of the system like
|
|||
files, processes, etc. The GWorkspace application provides this functionality
|
||||
in GNUstep. See the GWorkspace website for more details.
|
||||
|
||||
.SS DEVELOPER APPLICATIONS
|
||||
.P
|
||||
.P
|
||||
.B Getting More Help
|
||||
.P
|
||||
Most discussion and support is taking place on the GNUstep mailinglists
|
||||
<http://www.gnustep.org/information/gethelp.html>. Additionally, most larger
|
||||
projects have their own mailing lists. Consult the appropriate websites for
|
||||
details.
|
||||
.P
|
||||
Alternatively you are invited to join the #GNUstep IRC channel on
|
||||
FreeNode (irc.freenode.net).
|
||||
.P
|
||||
What would a development environment be without the applications to create applications? The applications provided by GNUstep for Rapid Application Developement are:
|
||||
.TP
|
||||
GORM
|
||||
.B GORM
|
||||
is the interface modeler. With
|
||||
.B GORM
|
||||
you can quickly create the graphical interface of your application.
|
||||
.TP
|
||||
Project Center
|
||||
.B Project Center
|
||||
is the program where you can develop your program. It offers you automatic generation of
|
||||
.I GNUmakefiles
|
||||
, project maintenance and of course a code editor.
|
||||
|
||||
.SH SEE ALSO
|
||||
gcc(1), gdnc(1), gdomap(8), gopen(1), gpbs(1), make(1), openapp(1)
|
||||
.PP
|
||||
.B GNUstep Websites:
|
||||
.PP
|
||||
Official GNUstep website <http://www.gnustep.org/> -
|
||||
GNUstep Wiki (lots of useful information) <http://wiki.gnustep.org/> -
|
||||
GNUstep Project Page <http://savannah.gnu.org/projects/gnustep/> -
|
||||
GNUstep Community Page <http://www.gnustep.net/> -
|
||||
GNUstep Documentation Library <http://gnustep.made-it.com/> -
|
||||
GNUstep Build Guide <http://gnustep.made-it.com/BuildGuide/>
|
||||
.PP
|
||||
Collaboration World <http://www.collaboration-world.com/> -
|
||||
GNUstep.de <http://www.gnustep.de/> -
|
||||
GNUstep.it <http://www.gnustep.it/> -
|
||||
GNUstep.us <http://www.gnustep.us/> -
|
||||
GWorkspace Website <http://www.gnustep.it/enrico/gworkspace/>
|
||||
.PP
|
||||
.B Mailinglists:
|
||||
.PP
|
||||
<http://www.gnu.org/software/gnustep/information/gethelp.html> -
|
||||
Archives can be found at <http://mail.gnu.org/archive/html/>
|
||||
.TP
|
||||
http://www.gnustep.org/
|
||||
Official GNUstep website
|
||||
.TP
|
||||
http://wiki.gnustep.org/
|
||||
GNUstep Wiki (lots of useful information)
|
||||
.TP
|
||||
http://savannah.gnu.org/projects/gnustep/
|
||||
GNUstep Project Page
|
||||
.TP
|
||||
http://gnustep.made-it.com/
|
||||
GNUstep Documentation Library
|
||||
.TP
|
||||
http://www.collaboration-world.com
|
||||
Collaboration World, the home of GNUmail
|
||||
.TP
|
||||
http://www.gnustep.it/
|
||||
The home of GWorkspace, JIGS, Renaissance and programming tutorials.
|
||||
.P
|
||||
.SH AUTHORS
|
||||
.B Mailinglists
|
||||
.TP
|
||||
http://www.gnustep.org/information/gethelp.html
|
||||
Mailing lists and mailing list archives.
|
||||
.P
|
||||
.B IRC
|
||||
.TP
|
||||
#GNUstep on FreeNode
|
||||
You are invited to join the #GNUstep IRC channel on FreeNode (irc.freenode.net).
|
||||
.SH HISTORY
|
||||
.B GNUstep
|
||||
was at first a collaboration of two projects that wanted to create a single
|
||||
.B GNUstep
|
||||
project that complied to the OpenStep specification provided by NeXT Computer, Inc. and SunSoft, Inc. Development of this joint effort started around 1993-1994. For a more detailed history description see the GNUstep Documentation Library referenced in the
|
||||
.B SEE ALSO
|
||||
section.
|
||||
.PP
|
||||
GNUstep is developed and maintained by a large number of people. Please
|
||||
see <http://www.gnustep.org/developers/whoiswho.html> for a list.
|
||||
|
||||
.SH AUTHORS
|
||||
This man-page was first written by Martin Brecher <martin@mb-itconsulting.com> in august of 2003.
|
||||
.PP
|
||||
GWorkspace is developed by Enrico Sersale. Please see the GWorkspace Website
|
||||
for details.
|
||||
.PP
|
||||
This man page was written by Martin Brecher <martin@mb-itconsulting.com>.
|
||||
In December 2007 it was expanded by Dennis Leeuw <dleeuw@made-it.com> and made to comply with the gnustep-make-2.0.x releases.
|
||||
|
|
|
|||
40
Documentation/debugapp.1
Normal file
40
Documentation/debugapp.1
Normal file
|
|
@ -0,0 +1,40 @@
|
|||
.\" Process this file with
|
||||
.\" groff -man -Tascii debugapp.1
|
||||
.\"
|
||||
.TH debugapp 1 "16/12/2007" GNUstep "GNUstep System Manual"
|
||||
.SH NAME
|
||||
debugapp \- A wrapper for openapp.
|
||||
.SH SYNOPSIS
|
||||
.BR debugapp " [" \-\-find ]
|
||||
.RB [ \-\-gdb=... ]
|
||||
.IR application " [" arguments... ]
|
||||
.P
|
||||
.SH DESCRIPTION
|
||||
.B debugapp
|
||||
is a tool that helps you start or find applications by name in debugging mode. It acts as a wrapper around
|
||||
.B openapp
|
||||
, and calls openapp with the
|
||||
.B \-\-debug
|
||||
option. By default gdb is used as the debugger, but this can be changed with the
|
||||
.B \-\-gdb=
|
||||
option or through the
|
||||
.B GDB
|
||||
enviroment variable.
|
||||
.P
|
||||
The
|
||||
.I arguments
|
||||
are the arguments passed to the application.
|
||||
.P
|
||||
See the
|
||||
.B openapp
|
||||
(1) man-page for a complete description.
|
||||
.SH SEE ALSO
|
||||
openapp(1)
|
||||
.P
|
||||
.SH HISTORY
|
||||
Work on
|
||||
.B debugapp
|
||||
started in October 2006 by Nicola Pero <n.pero@mi.flashnet.it>.
|
||||
|
||||
.SH AUTHORS
|
||||
This man page was written by Dennis Leeuw <dleeuw@made-it.com>.
|
||||
88
Documentation/gnustep-config.1
Normal file
88
Documentation/gnustep-config.1
Normal file
|
|
@ -0,0 +1,88 @@
|
|||
.\" Process this file with
|
||||
.\" groff -man -Tascii gnustep-config.1
|
||||
.\"
|
||||
.TH gnustep-config 1 "24/12/2007" GNUstep "GNUstep System Manual"
|
||||
.SH NAME
|
||||
gnustep-config \- prints information about the current gnustep installation.
|
||||
.SH SYNOPSIS
|
||||
.BR gnustep-config " ["
|
||||
.BI \-\-variable= variable
|
||||
.RB | \-\-objc-flags | \-\-objc-libs | \-\-base-libs | \-\-gui-libs " ]"
|
||||
.SH DESCRIPTION
|
||||
.B gnustep-config
|
||||
can print information about the currently installed GNUstep system. It can output dependend on the options used the different flags used for compilation, but also the different internal variables used by the make system.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.BI \-\-variable= variable
|
||||
prints the value of the specified variable. Possible variables are:
|
||||
.RS
|
||||
.RS
|
||||
.PD 0
|
||||
.HP
|
||||
GNUSTEP_MAKEFILES
|
||||
.HP
|
||||
GNUSTEP_USER_DIR
|
||||
.HP
|
||||
GNUSTEP_USER_DEFAULTS_DIR
|
||||
.HP
|
||||
GNUSTEP_HOST
|
||||
.HP
|
||||
GNUSTEP_HOST_CPU
|
||||
.HP
|
||||
GNUSTEP_HOST_VENDOR
|
||||
.HP
|
||||
GNUSTEP_HOST_OS
|
||||
.HP
|
||||
GNUSTEP_IS_FLATTENED
|
||||
.HP
|
||||
GNUSTEP_xxx_APPS
|
||||
.HP
|
||||
GNUSTEP_xxx_TOOLS
|
||||
.HP
|
||||
GNUSTEP_xxx_LIBRARY
|
||||
.HP
|
||||
GNUSTEP_xxx_HEADERS
|
||||
.HP
|
||||
GNUSTEP_xxx_LIBRARIES
|
||||
.HP
|
||||
GNUSTEP_xxx_DOC
|
||||
.HP
|
||||
GNUSTEP_xxx_DOC_MAN
|
||||
.HP
|
||||
GNUSTEP_xxx_DOC_INFO
|
||||
.RE
|
||||
where 'xxx' could be any of 'SYSTEM', 'NETWORK', 'LOCAL' and 'USER'.
|
||||
.RE
|
||||
.PD 1
|
||||
|
||||
.TP
|
||||
.B \-\-objc-flags
|
||||
prints all the flags required to compile an ObjC file
|
||||
|
||||
.TP
|
||||
.B \-\-objc-libs
|
||||
prints all the flags required to link a pure ObjC program (no foundation/gui)
|
||||
|
||||
.TP
|
||||
.B \-\-base-libs
|
||||
prints all the flags required to link a command-line ObjC program (no gui)
|
||||
|
||||
.TP
|
||||
.B \-\-gui-libs
|
||||
prints all the flags required to link a GUI ObjC program
|
||||
.SH BUGS
|
||||
None known
|
||||
.SH SEE ALSO
|
||||
GNUstep(7)
|
||||
.SH HISTORY
|
||||
Work on
|
||||
.B gnustep-config
|
||||
started in 2007 by Nicola Pero <n.pero@mi.flashnet.it>.
|
||||
.SH AUTHORS
|
||||
This man page was written by Dennis Leeuw <dleeuw@made-it.com>.
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2007 Free Software Foundation, Inc.
|
||||
.PP
|
||||
Copying and distribution of this file, with or without modification,
|
||||
are permitted in any medium without royalty provided the copyright
|
||||
notice and this notice are preserved.
|
||||
229
Documentation/library-combo.7
Normal file
229
Documentation/library-combo.7
Normal file
|
|
@ -0,0 +1,229 @@
|
|||
.\" Process this file with
|
||||
.\" groff -man -Tascii library-combo.7
|
||||
.\"
|
||||
.TH library-combo 7 "20/12/2007" gnustep-make "GNUstep System Manual"
|
||||
.SH DESCRIPTION
|
||||
This manual page is about cross-compilation and fat binaries. Fat binaries are packeges that you can supply which contains more the one binary of your e.g. application. So you can support multiple platforms with a single package.
|
||||
.PP
|
||||
To support this your system has to be built in a non-flattened way. Meaning that during the installation of
|
||||
.I gnustep-make
|
||||
you should have selected
|
||||
.B \-\-disable-flattened
|
||||
and the types of library combinations you want to support, through the
|
||||
.B \-\-with-library-combo
|
||||
option. With library combinations we mean the Objective-C runtime, the Foundation library and the Application library. For more details about this see the LIBRARY-COMBO section.
|
||||
.PP
|
||||
If you installed your
|
||||
.B GNUstep
|
||||
system in a non-flattened way all system dependend binaries are installed in subdirectories with
|
||||
.I cpu/os/library-combo
|
||||
information. That means for instance that the
|
||||
.I gnustep-base
|
||||
library will be installed in
|
||||
.I Library/Libraries/ix86/linux/gnu\-gnu\-gnu/
|
||||
when you are on an Intel x86 system, running linux with the
|
||||
.SM GNU
|
||||
runtime for Objective-C and you installed
|
||||
.BR GNUstep .
|
||||
.PP
|
||||
For each and every library-combo that you want to support you should create the environment through
|
||||
.IR gnustep-make ,
|
||||
because it installs a different
|
||||
.I config.make
|
||||
to support its own
|
||||
.BR CC ", " OPTFLAGS ,
|
||||
etc. flags.
|
||||
.SS LIBRARY-COMBO
|
||||
An important issue is to let to a package the ability to deal with various libraries and configurations available now:
|
||||
.TP
|
||||
.B Objective-C runtimes
|
||||
In the Objective-C world there are three major runtimes: the NeXT runtime, the Apple runtime and the
|
||||
.SM GNU
|
||||
runtime (both with and without garbage collection enabled). They are different in several respects and a program or library that works at the runtime level should be aware of them.
|
||||
.TP
|
||||
.B Foundation libraries
|
||||
There are several Foundation libraries an application or tool can be written on top of: NeXT Foundation library which runs on NeXTStep/OPENSTEP systems, gnustep-base, libFoundation and Apple Cocoa system.
|
||||
.TP
|
||||
.B Graphical interfaces
|
||||
Until now three libraries provide or try to provide OpenStep compliant systems: the AppKit from NeXT, gnustep-gui and Cocoa from Apple.
|
||||
.PP
|
||||
If a program wants to work with all the possible combinations it will have to provide different binaries for each combination because it's not possible to have a tool compiled for NeXT Foundation that runs with gnustep-base or vice-versa. To summarize, a program can be compiled for these combinations:
|
||||
.TP
|
||||
.B Objective-C runtime
|
||||
nx (for NeXT), gnu (for
|
||||
.SM GNU
|
||||
without garbage collection), gnugc (for
|
||||
.SM GNU
|
||||
with garbage collection), apple (for Apple)
|
||||
.TP
|
||||
.B Foundation library
|
||||
nx (for NeXT), gnu (for gnustep-base), fd (for libFoundation), apple (for Apple Cocoa)
|
||||
.TP
|
||||
.B GUI library
|
||||
nx (for NeXT), gnu (for gnustep-gui), apple (for Apple Cocoa)
|
||||
.PP
|
||||
We'll denote the fact that an application was compiled for a certain combination of the above values by using the abbreviations of the different subsystems and placing dashes between them. For example an application compiled for NeXT Foundation using NeXT AppKit will have the compile attribute nx\-nx\-nx. An application compiled for Apple Cocoa with the
|
||||
.SM GNU
|
||||
compiler for Objective-C gnu\-apple\-apple and another one compiled for
|
||||
.I gnustep-base
|
||||
using
|
||||
.I gnustep-gui
|
||||
under Unix will be denoted by gnu\-gnu\-gnu. Here is a list of some of the possible combinations:
|
||||
.PP
|
||||
.RS 0
|
||||
Runtime Foundation GUI
|
||||
.RS 0
|
||||
nx nx nx
|
||||
.RS 0
|
||||
nx fd gnu
|
||||
.RS 0
|
||||
gnu gnu gnu
|
||||
.RS 0
|
||||
gnu fd gnu
|
||||
.RS 0
|
||||
gnu apple apple
|
||||
.RS 0
|
||||
gnugc gnu gnu
|
||||
.RS 0
|
||||
gnugc fd gnu
|
||||
.RS 0
|
||||
gnugc apple apple
|
||||
.RS 0
|
||||
apple apple apple
|
||||
.RS 0
|
||||
apple gnu gnu
|
||||
.RE 0
|
||||
.PP
|
||||
Note that one can choose his/her own packages to build; it is not required to have all the packages installed on the system. Not having all of them installed limits only the ability to build and distribute binaries for those missing combinations.
|
||||
|
||||
.SS DIRECTORY STRUCTURE
|
||||
For cross-compilation in a non-flattened directory structure is recommended, so that you can store on the same directory structure binaries for different machines. The standard
|
||||
.B GNUstep
|
||||
filesystem layout is normally used when a non-flattened directory structure is being used; this is obtained with the
|
||||
.BI \-\-with-layout= gnustep
|
||||
option when configuring
|
||||
.IR gnustep-make .
|
||||
The entire
|
||||
.B GNUstep
|
||||
installation is then created inside
|
||||
.I /usr/GNUstep
|
||||
(or another directory if you use the
|
||||
.B \-\-prefix=...
|
||||
option when configuring
|
||||
.IR gnustep-make ).
|
||||
Directories that contain binaries (such as the
|
||||
.I Libraries
|
||||
directory) inside
|
||||
.I /usr/GNUstep
|
||||
are then set up to support fat binaries as follows:
|
||||
.PP
|
||||
.RS 0
|
||||
Libraries/
|
||||
.RS 0
|
||||
ix86/
|
||||
.RS 0
|
||||
linux\-gnu/
|
||||
.RS 0
|
||||
gnu\-gnu\-gnu/
|
||||
.RS 0
|
||||
libgnustep\-base.so
|
||||
.RS 0
|
||||
libgnustep\-gui.so
|
||||
.RS 0
|
||||
gnu\-fd\-gnu/
|
||||
.RS 0
|
||||
libFoundation.so
|
||||
.RS 0
|
||||
libgnustep\-gui.so
|
||||
.PP
|
||||
To allow the right libraries to be found, you need to source
|
||||
.I GNUstep.sh
|
||||
before using
|
||||
.BR GNUstep ,
|
||||
and you need to start up your application by using
|
||||
.BR openapp ,
|
||||
which will locate the right binary for your library combo.
|
||||
.SS BUILDING FOR A LIBRARY-COMBO
|
||||
The makefile package will allow the user to choose between different library combinations. To specify a combination you want to compile for just type:
|
||||
.PP
|
||||
.RS 0
|
||||
$ make library_combo=library-combo
|
||||
.PP
|
||||
For instance if you want to choose to compile using the GNUstep's Foundation implementation and use the GNUstep GUI library on a GNU/Linux machine you can do like this:
|
||||
.PP
|
||||
.RS 0
|
||||
$ make library_combo=gnu\-gnu\-gnu
|
||||
.PP
|
||||
If your project requires running configure before compiling there are two issues you have to keep in mind. 'configure' is used to determine the existence of particular header files and/or of some specific functionality in the system header files. This thing is usually done by creating a config.h file which contains a couple of defines like HAVE_... which say if the checked functionality is present or not.
|
||||
.PP
|
||||
Another usage of configure is to determine some specific libraries to link against to and/or some specific tools. A typical
|
||||
.B GNUstep
|
||||
program is not required to check for additional libraries because this step is done by the time the makefile package is installed. If the project still needs to check for additional libraries and/or tools, the recommended way is to output a
|
||||
.I config.mak
|
||||
file which is included by the main
|
||||
.IR GNUmakefile ,
|
||||
instead of using
|
||||
.I Makefile.in
|
||||
files which are modified by
|
||||
.IR configure .
|
||||
The reason for not doing this is to avoid having the makefiles contain target dependencies like above, this way keeping only one makefile instead of several for each target machine.
|
||||
.PP
|
||||
The makefile package is written for
|
||||
.SM GNU
|
||||
make because it provides some very powerful features that save time both in writing the package but also at runtime, when you compile a project.
|
||||
|
||||
.SS BUILDING FOR AN ARCHITECTURE
|
||||
In order to build a project for multiple architectures you'll need the development environment for the target machine installed on your machine. This includes a cross-compiler together with all the additional tools like the assembler and linker, the target header files and all the libraries you need.
|
||||
.PP
|
||||
The
|
||||
.B GNUstep
|
||||
makefile package should be able to compile and link an application for another machine just by typing
|
||||
.PP
|
||||
.RS 0
|
||||
$ make target=target-triplet
|
||||
.PP
|
||||
where target-triplet is the canonical system name as reported by
|
||||
.IR config.guess .
|
||||
|
||||
.SS USING A LIBRARY-COMBO
|
||||
When you use library-combos, you must always source
|
||||
.IR GNUstep.sh .
|
||||
That allows you to switch library paths on the fly. If you want to switch to a different library-combo in your shell, and if you are using
|
||||
.BR bash ,
|
||||
it's common to first source
|
||||
.I GNUstep-reset.sh
|
||||
to reset all shell variables, then to source
|
||||
.B GNUstep.sh
|
||||
again. Let's assume we use gnu-gnu-gnu as our current
|
||||
.B LIBRARY_COMBO
|
||||
and we want to switch to gnugc\-gnu\-gnu, then we would use:
|
||||
.PP
|
||||
.RS 0
|
||||
. /usr/GNUstep/System/Library/Makefiles/GNUstep-reset.sh
|
||||
.RS 0
|
||||
export LIBRARY_COMBO=gnugc\-gnu\-gnu
|
||||
.RS 0
|
||||
. /usr/GNUstep/System/Library/Makefiles/GNUstep.sh
|
||||
|
||||
.SH SEE ALSO
|
||||
debugapp(1), GNUstep(7), gnustep-config(1), openapp(1)
|
||||
|
||||
.SH HISTORY
|
||||
Work on gnustep-make started in 1997 by Scott Christley <scottc@net-community.com>.
|
||||
.PP
|
||||
Version 2.0.0 of gnustep-make introduced many changes with previous releases, which was mainly the work of Nicola Pero <nicola.pero@meta-innovation.com>
|
||||
|
||||
.SH AUTHORS
|
||||
This man-page was written by Dennis Leeuw <dleeuw@made-it.com> based on the DESIGN document from the gnustep-make source tree.
|
||||
|
||||
.SH CREDITS
|
||||
The DESIGN document was written by Ovidiu Predescu.
|
||||
.PP
|
||||
This work could only be as is due to the notes and corrects from Nicola Pero <nicola.pero@meta-innovation.com>.
|
||||
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2007 Free Software Foundation, Inc.
|
||||
.PP
|
||||
Copying and distribution of this file, with or without modification,
|
||||
are permitted in any medium without royalty provided the copyright
|
||||
notice and this notice are preserved.
|
||||
|
|
@ -1,106 +1,113 @@
|
|||
.\"openapp(1) man page
|
||||
.\"put together by Martin Brecher <martin@gnustep.de>
|
||||
.\" Process this file with
|
||||
.\" groff -man -Tascii openpp.1
|
||||
.\"
|
||||
.\"Process this file with
|
||||
.\"groff -man -Tascii openpp.1
|
||||
.\"
|
||||
.TH OPENAPP 1 "August 2003" GNUstep "GNUstep System Manual"
|
||||
.TH openapp 1 "12/12/2007" gnustep-make "GNUstep System Manual"
|
||||
.SH NAME
|
||||
openapp \- launch applications from the command line
|
||||
|
||||
.SH SYNOPSIS
|
||||
.B openapp
|
||||
.RB [ --find ]
|
||||
.IR application
|
||||
.RB [ "\fIarguments..." ]
|
||||
.P
|
||||
.RB [ \-\-find ]
|
||||
.RB [ \-\-debug " [" \-\-gdb=
|
||||
.IR debuger "]] ["
|
||||
.BI \-\-library-combo= library-combo
|
||||
]
|
||||
.I application
|
||||
.RI [ arguments... ]
|
||||
|
||||
.SH DESCRIPTION
|
||||
The
|
||||
.B openapp
|
||||
command allows you launch graphical GNUstep applications from the command
|
||||
line.a
|
||||
command allows you to launch graphical GNUstep applications from the command line.
|
||||
.PP
|
||||
.I application
|
||||
is the complete or relative name of the application program with or
|
||||
without the .app extension, like Ink.app.
|
||||
is the complete or relative name of the application program with or without the .app extension, like
|
||||
.B Ink.app.
|
||||
.PP
|
||||
.I arguments
|
||||
are the arguments passed to the application.
|
||||
.PP
|
||||
.B openapp
|
||||
first checks whether the application is in the current working directory.
|
||||
If not then searches the GNUstep domains' Applications folders in the
|
||||
following order:
|
||||
User (i.e. ~/GNUstep/Applications), Local, Network, System. First match wins.
|
||||
.PP
|
||||
If
|
||||
.I application
|
||||
is given without extension (i.e. Ink instead of Ink.app),
|
||||
.B openapp
|
||||
searches for
|
||||
.I application.app
|
||||
,
|
||||
.I application.debug
|
||||
,
|
||||
.I application.profile
|
||||
(in that order).
|
||||
.PP
|
||||
If
|
||||
.I --find
|
||||
is used as first argument,
|
||||
.B openapp
|
||||
prints out
|
||||
the full path of the application executable which would be
|
||||
executed, without actually executing it as it would normally do.
|
||||
.PP
|
||||
first checks whether the application is in the current working directory. If not then searches the GNUstep domains' Applications folders in the following order:
|
||||
User
|
||||
.RI "(i.e. " ~/GNUstep/Applications ),
|
||||
Local, Network, System. First match wins.
|
||||
|
||||
.SH OPTIONS
|
||||
.IP "\fB--find"
|
||||
print complete path of the executable which would be launched.
|
||||
.IP "\fB--help"
|
||||
.TP
|
||||
.BI \-\-find " application"
|
||||
will print out the full path of the application executable which would be executed, without actually executing it. It will also list all paths that are attempted.
|
||||
.TP
|
||||
.BI \-\-debug " application"
|
||||
starts the application in the debugger. By default
|
||||
.BR gdb ,
|
||||
but this can be changed with the
|
||||
.B \-\-gdb=
|
||||
argument or through the
|
||||
.B GDB
|
||||
shell variable.
|
||||
.TP
|
||||
.BI \-\-library-combo= library-combo
|
||||
Starts the application with the specified library combo. This is a rarely used option in a non-flattened setup. See the
|
||||
.BR library-combo (7)
|
||||
man-page for more information about the different library combinations.
|
||||
.TP
|
||||
.B \-\-help
|
||||
print above usage description.
|
||||
.PP
|
||||
|
||||
.SH EXAMPLES
|
||||
Start Ink.app without additional parameters:
|
||||
Start
|
||||
.B Ink.app
|
||||
without additional parameters:
|
||||
.PP
|
||||
.I openapp Ink.app
|
||||
.B openapp Ink.app
|
||||
.PP
|
||||
Launch Ink.app and pass it the --GNU-Debug argument:
|
||||
Launch
|
||||
.B Ink.app
|
||||
and pass it the
|
||||
.B \-\-debug
|
||||
argument:
|
||||
.PP
|
||||
.I openapp Ink.app --GNU-Debug=NSTextView
|
||||
.B openapp \-\-debug Ink.app
|
||||
.PP
|
||||
To determine which executable is launched by openapp, type:
|
||||
.PP
|
||||
.I openapp --find Ink.app
|
||||
.B openapp \-\-find Ink.app
|
||||
.PP
|
||||
The output of the abovecommand might be something like:
|
||||
The output of the above command might be something like:
|
||||
.I /usr/GNUstep/Local/Applications/Ink.app/Ink
|
||||
.PP
|
||||
.SH BUGS
|
||||
.B openapp
|
||||
does currently not handle library combos.
|
||||
.PP
|
||||
|
||||
.SH ENVIRONMENT
|
||||
.IP "\fBGNUSTEP_PATHLIST"
|
||||
This variable contains the paths of the domains in which
|
||||
.B gopen
|
||||
tries to find applications to open the files with. Entries are
|
||||
separated by a colon.
|
||||
.IP
|
||||
.IP Example:
|
||||
.I /home/foo/GNUstep:/usr/GNUstep/Local:/usr/GNUstep/Network:/usr/GNUstep/System
|
||||
.PP
|
||||
.TP
|
||||
.B GNUSTEP_CONFIG_FILE
|
||||
is used to determine where the
|
||||
.B GNUstep.sh
|
||||
configuration file is located. If the variable is not set
|
||||
.B openapp
|
||||
tries to locate it in the folder where
|
||||
.B openapp
|
||||
was started, then in the user domain, and as a last resort in the system domain (or actually the place you configured
|
||||
.RI ( \-\-with-config-file= )
|
||||
during building).
|
||||
.TP
|
||||
.B GDB
|
||||
Sets the debugger to use when
|
||||
.B \-\-debug
|
||||
is used.
|
||||
|
||||
.SH SEE ALSO
|
||||
GNUstep(7), gopen(1)
|
||||
.P
|
||||
debugapp(1), GNUstep(7), gopen(1), library-combo(7), opentool(1)
|
||||
|
||||
.SH HISTORY
|
||||
Work on
|
||||
.B openapp
|
||||
started October 1997.
|
||||
.P
|
||||
This manual page was first written July 2003.
|
||||
.P
|
||||
.SH AUTHORS
|
||||
openapp was originally written by Ovidiu Predescu <ovidiu@net-community.com>
|
||||
.PP
|
||||
.B openapp
|
||||
was originally written by Ovidiu Predescu <ovidiu@net-community.com>
|
||||
and is now maintained by Nicola Pero <n.pero@mi.flashnet.it>.
|
||||
.P
|
||||
This man page was written by Martin Brecher <martin@mb-itconsulting.com>.
|
||||
|
||||
.SH AUTHORS
|
||||
This manual page was first written July 2003 by Martin Brecher <martin@mb-itconsulting.com>.
|
||||
.PP
|
||||
Updated with notes from Hubert Chathi <uhoreg@debian.org> and Dennis Leeuw <dleeuw@made-it.com>, December 2007 by Dennis Leeuw.
|
||||
|
|
|
|||
36
Documentation/opentool.1
Normal file
36
Documentation/opentool.1
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
.\" Process this file with
|
||||
.\" groff -man -Tascii opentool.1
|
||||
.\"
|
||||
.TH opentool 1 12/12/2007 gnustep-make "GNUstep System Manual"
|
||||
.SH NAME
|
||||
opentool \- Command line tool for starting tools
|
||||
|
||||
.SH SYNOPSIS
|
||||
.BR opentool " [" \-\-library-combo=... ]
|
||||
.B tool
|
||||
.RI " [" arguments... ]
|
||||
|
||||
.SH DESCRIPTION
|
||||
.B opentool
|
||||
is absolete. Make sure the
|
||||
.I Tools
|
||||
directories are in your
|
||||
.BR PATH ,
|
||||
then
|
||||
.B opentool
|
||||
is not needed anymore.
|
||||
.SH SEE ALSO
|
||||
openapp(1), debugapp(1), GNUstep(7)
|
||||
.SH HISTORY
|
||||
Work on
|
||||
.B opentool
|
||||
started in 1997 and was written by Scott Predescu <ovidiu@net-community.com>, Ovidiu Predescu <ovidiu@net-community.com> and Nicola Pero <n.pero@mi.flashnet.it>
|
||||
.
|
||||
.SH AUTHORS
|
||||
This man page was written by Dennis Leeuw <dleeuw@made-it.com> December 2007.
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2007 Free Software Foundation, Inc.
|
||||
.PP
|
||||
Copying and distribution of this file, with or without modification,
|
||||
are permitted in any medium without royalty provided the copyright
|
||||
notice and this notice are preserved.
|
||||
|
|
@ -184,10 +184,18 @@ install: generated-files
|
|||
$(EC)(echo "Installing manpages"; \
|
||||
"$(srcdir)/mkinstalldirs" "$(mandir)/man1" \
|
||||
"$(mandir)/man7"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/debugapp.1" "$(mandir)/man1"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man1/debugapp.1.gz" && gzip -9 "$(mandir)/man1/debugapp.1"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/gnustep-config.1" "$(mandir)/man1"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man1/gnustep-config.1.gz" && gzip -9 "$(mandir)/man1/gnustep-config.1"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/openapp.1" "$(mandir)/man1"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man1/openapp.1.gz" && gzip -9 "$(mandir)/man1/openapp.1"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/opentool.1" "$(mandir)/man1"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man1/opentool.1.gz" && gzip -9 "$(mandir)/man1/opentool.1"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/GNUstep.7" "$(mandir)/man7"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man7/GNUstep.7.gz" && gzip -9 "$(mandir)/man7/GNUstep.7")
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man7/GNUstep.7.gz" && gzip -9 "$(mandir)/man7/GNUstep.7"; \
|
||||
$(INSTALL_DATA) "$(srcdir)/Documentation/library-combo.7" "$(mandir)/man7"; \
|
||||
which gzip > /dev/null 2>&1 && rm -f "$(mandir)/man7/library-combo.7.gz" && gzip -9 "$(mandir)/man7/library-combo.7")
|
||||
$(EC)(if [ "@GNUSTEP_STRIP_MAKEFILES@" = "strip" ]; then \
|
||||
echo "Stripping makefiles and shell scripts..."; \
|
||||
cd "$(makedir)"; ./strip_makefiles.sh; \
|
||||
|
|
@ -198,8 +206,15 @@ install: generated-files
|
|||
# $(INSTALL_DATA) $(srcdir)/config.site $(GNUSTEP_SYSTEM_ROOT)/share)
|
||||
|
||||
uninstall:
|
||||
rm -f "$(mandir)/man1/debugapp.1" "$(mandir)/man1/debugapp.1.gz"; \
|
||||
rm -f "$(mandir)/man1/gnustep-config.1" "$(mandir)/man1/gnustep-config.1.gz"; \
|
||||
rm -f "$(mandir)/man1/openapp.1" "$(mandir)/man1/openapp.1.gz"; \
|
||||
rm -f "$(mandir)/man1/opentool.1" "$(mandir)/man1/opentool.1.gz"; \
|
||||
rm -f "$(mandir)/man7/GNUstep.7" "$(mandir)/man7/GNUstep.7.gz"; \
|
||||
rm -f "$(mandir)/man7/library-combo.7" "$(mandir)/man7/library-combo.7.gz"
|
||||
-rmdir "$(mandir)/man1"
|
||||
-rmdir "$(mandir)/man7"
|
||||
-rmdir "$(mandir)"
|
||||
for f in config.guess config.sub install-sh mkinstalldirs \
|
||||
clean_cpu.sh clean_os.sh \
|
||||
clean_vendor.sh cpu.sh ld_lib_path.sh os.sh \
|
||||
|
|
@ -238,6 +253,7 @@ uninstall:
|
|||
rm -f "$(makedir)/filesystem.make"
|
||||
rm -f "$(makedir)/$(GNUSTEP_TARGET_LDIR)/config.make"
|
||||
rm -f "$(GNUSTEP_CONFIG_FILE)"
|
||||
-rmdir "$(GNUSTEP_CONFIG_FILE_DIR)"
|
||||
-for f in "$(makedir)/Instance/Documentation" \
|
||||
"$(makedir)/Instance/Shared" \
|
||||
"$(makedir)/Instance" \
|
||||
|
|
@ -247,7 +263,8 @@ uninstall:
|
|||
"$(makedir)/$(GNUSTEP_TARGET_LDIR)" \
|
||||
"$(makedir)/$(GNUSTEP_TARGET_DIR)" \
|
||||
"$(makedir)/$(GNUSTEP_TARGET_CPU)" \
|
||||
"$(makedir)"; do \
|
||||
"$(makedir)" \
|
||||
"$(tooldir)"; do \
|
||||
test -d "$$f" && rmdir "$$f"; \
|
||||
done
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue