This manual describes how to install GNUPro and introduces you to GNUPro and the GNUPro documentation set. After you read this Getting Started Guide, refer to the following documentation for details about the GNUPro Toolkit:
The documentation is in HTML and PDF formats on your CD as well as being available at the Red Hat site:
http://www.redhat.com/docs/manuals/gnupro/
For more information on the tools and their history, see the following web sites:
http://www.opensource.org/docs/products.php
http://www.openbsd.org/docum.html
This list of URLs is only an introduction; other sites are available.
The GNUPro manuals use the following conventions.
The heading IMPORTANT! gives essential information, while WARNING! helps you avoid problems such as damaged files or system or programming errors. For example:
% indicates a system's shell prompt in this documentation. A prompt may differ in some examples, depending on the system and tools in use; with the debugger and its console's command line window, (gdb) is the prompt.
The GNUPro manuals also use the following conventions for commands, filenames, and other program-specific subjects.
|
%
gcc -print-search-dirs |
Use the configure command for setting up the environment in which your applications will compile, and for locating the tools to use with your applications.
When configuring, use the canonical architecture-vendor-operating-system naming convention; Table 1 shows the usage of canonical names (referring to a host platform that Red Hat supports).
|
Microsoft Windows NT 4.0-sp3 |
|
In Table 1, for a Sun SPARCstation running the Solaris 2.6 operating system, the full name is sparc-sun-solaris2.6 ( sparc being the architecture, sun being the vendor, and solaris2.6 being the operating system version). There are exceptions to this pattern, such as i686-cygwin for Microsoft Windows operating systems and i686-pc-linux-gnulibc2.1 or i686-pc-linux-gnulibc2.2 for Red Hat Linux operating systems.
A very common requirement for build systems is simultaneously allowing compilation of the same code in multiple environments. Given one set of source code, developers want the ability to create more than one set of targets from it; for instance, building it on two or more different operating systems. There are basically three approaches: Source Copy method, the Explicit Path method, and the VPATH method. See "Developing with GNUPro Toolkit" on page 33; see also Using GNU CC in the GNUPro Compiler Tools and Using make in GNUPro Development Tools for more information on how to build, to compile, and to develop on multiple systems.
The following tasks are fundamentals of a process for ensuring that your configuration works:
Use the config.guess shell script to determine the host type that you have running. Invoke the script by typing configure config.guess at a shell prompt.
If your shell cannot find the config.guess script, use configure along with system commands such as uname.
The following object file formats are configurable for output when compiling: a.out (UNIX object file format), COFF (Common Object File Format), EABI (Embedded Application Binary Interface format), and ELF (Embedded Linker Format).
For configurations with embedded development when using the whole environment's names, see "Embedded Cross-configurations" on page 5.
For more information on configuring your system and your environment before developing, see "Developing with GNUPro Toolkit" on page 33; see also Using GNU CC in the GNUPro Compiler Tools manual.
GNUPro Toolkit software is configurable for the following native host operating systems:
When developing with an embedded cross-configuration, GNUPro Toolkit software works with target processors. You work with the tools, which are on the host, using a toolchain, calling a specific tool with the specific embedded target's name.
To use a specific tool, add the tool's name to its canonical name . For host names, see Table 1, and, for the name of the specific tool, see "Compiler and Development Tools" on page 18, "Libraries" on page 18, and "Auxiliary Development Tools" on page 19. For example, if you are working with a SPARCstation, and calling the compiler for a Power PC-based board, you would type the following canonical name to invoke the GNU compiler:
sparc-sun-solaris2.6-x-powerpc-eabi-gcc
For more information, see "Developing with GNUPro Toolkit" on page 33, "What Embedded Development Means" on page 34 and "Tools, Toolchains and Usage" on page 35 for the complete naming conventions for hosts, targets and tools, and how to begin with embedded development.