source: clfs-embedded/BOOK/cross-tools/common/introduction.xml@ 0a9c489

Last change on this file since 0a9c489 was 1e8cfef, checked in by Joe Ciccone <jciccone@…>, 14 years ago

Embedded book doesn't install same packages twice

The embedded book never installs the same package twice so some
of the wording in section 6.1 Introduction is not needed and
could be confusing.

  • Property mode set to 100644
File size: 2.1 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-cross-tools-introduction">
9 <?dbhtml filename="introduction.html"?>
10
11 <title>Introduction</title>
12
13 <para>This chapter shows you how to create cross platform tools.</para>
14
15 <para>If for some reason you have to stop and come back later, remember
16 to use the <command>su - clfs</command> command, and it will setup the
17 build environment that you left.</para>
18
19 <sect2>
20 <title>Common Notes</title>
21
22 <important>
23 <para>Before issuing the build instructions for a package, the package
24 should be unpacked as user <systemitem class="username">clfs</systemitem>,
25 and a <command>cd</command> into the created directory should be
26 performed. The build instructions assume that the <command>bash</command>
27 shell is in use.</para>
28 </important>
29
30 <para>Several of the packages are patched before compilation, but only
31 when the patch is needed to circumvent a problem or supply a default
32 configuration. Warning messages about <emphasis>offset</emphasis> or
33 <emphasis>fuzz</emphasis> may also be encountered when applying a patch.
34 Do not worry about these warnings, as the patch was still successfully
35 applied.</para>
36
37 <para>During the compilation of most packages, there will be several
38 warnings that scroll by on the screen. These are normal and can safely
39 be ignored. These warnings are as they appear&mdash;warnings about
40 deprecated, but not invalid, use of the C or C++ syntax. C standards
41 change fairly often, and some packages still use the older standard.
42 This is not a problem, but does prompt the warning.</para>
43
44 <important>
45 <para>After installing each package, both in this and the next chapters,
46 delete its source and build directories, unless specifically instructed
47 otherwise.</para>
48 </important>
49
50 </sect2>
51
52</sect1>
Note: See TracBrowser for help on using the repository browser.