scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).
Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.
So, for each tool, we need to explicitly know what file to munge.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
1 File.........: 2 - Installing crosstool-NG.txt
2 Copyright....: (C) 2010 Yann E. MORIN <yann.morin.1998@free.fr>
3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
6 Installing crosstool-NG /
7 ________________________/
10 There are two ways you can use crosstool-NG:
11 - build and install it, then get rid of the sources like you'd do for most
13 - or only build it and run from the source directory.
15 The former should be used if you got crosstool-NG from a packaged tarball, see
16 "Install method", below, while the latter is most useful for developers that
17 use a clone of the repository, and want to submit patches, see "The Hacker's
24 If you go for the install, then you just follow the classical, but yet easy
26 ./configure --prefix=/some/place
29 export PATH="${PATH}:/some/place/bin"
31 You can then get rid of crosstool-NG source. Next create a directory to serve
32 as a working place, cd in there and run:
37 See below for complete usage.
43 If you go the hacker's way, then the usage is a bit different, although very
44 simple. First, you need to generate the ./configure script from its autoconf
48 Then, you run ./configure for local execution of crosstool-NG:
49 ./configure --enable-local
52 Now, *do not* remove crosstool-NG sources. They are needed to run crosstool-NG!
53 Stay in the directory holding the sources, and run:
56 See below for complete usage.
58 Now, provided you used a clone of the repository, you can send me your changes.
59 See the section titled CONTRIBUTING, below, for how to submit changes.
62 Preparing for packaging |
63 ------------------------+
65 If you plan on packaging crosstool-NG, you surely don't want to install it
66 in your root file system. The install procedure of crosstool-NG honors the
69 ./configure --prefix=/usr
71 make DESTDIR=/packaging/place install
77 crosstool-NG comes with a shell script fragment that defines bash-compatible
78 completion. That shell fragment is currently not installed automatically, but
81 To install the shell script fragment, you have two options:
82 - install system-wide, most probably by copying ct-ng.comp into
83 /etc/bash_completion.d/
84 - install for a single user, by copying ct-ng.comp into ${HOME}/ and
85 sourcing this file from your ${HOME}/.bashrc
91 Some people contributed code that couldn't get merged for various reasons. This
92 code is available as lzma-compressed patches, in the contrib/ sub-directory.
93 These patches are to be applied to the source of crosstool-NG, prior to
94 installing, using something like the following:
95 lzcat contrib/foobar.patch.lzma |patch -p1
97 There is no guarantee that a particular contribution applies to the current
98 version of crosstool-ng, or that it will work at all. Use contributions at