Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
docs/0 - Table of content.txt
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 2077 b11117cdfdf7
child 2385 d1b8e9836cbf
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 File.........: 0 - Table of content.txt

     2 Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>

     3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5

     4 

     5 

     6 Table Of Content  /

     7 _________________/

     8 

     9 

    10 1- Introduction

    11     - History

    12     - Referring to crosstool-NG

    13 

    14 2- Installing crosstool-NG

    15     - Install method

    16     - The hacker's way

    17     - Preparing for packaging

    18     - Shell completion

    19     - Contributed code

    20 

    21 3- Configuring a toolchain

    22     - Interesting config options

    23     - Re-building an existing toolchain

    24     - Using as a backend for a build-system

    25 

    26 4- Building the toolchain

    27     - Stopping and restarting a build

    28     - Testing all toolchains at once

    29     - Overriding the number of // jobs

    30     - Note on // jobs

    31     - Tools wrapper

    32 

    33 5- Using the toolchain

    34     - The 'populate' script

    35 

    36 6- Toolchain types

    37     - Seemingly-native toolchains

    38 

    39 7- Contributing

    40     - Sending a bug report

    41     - Sending patches

    42 

    43 8- Internals

    44     - Makefile front-end

    45     - Kconfig parser

    46     - Architecture-specific

    47     - Adding a new version of a component

    48     - Build scripts

    49 

    50 9 - How is a toolchain constructed?

    51     - I want a cross-compiler! What is this toolchain you're speaking about?

    52     - So, what are those components in a toolchain?

    53     - And now, how do all these components chained together?

    54     - So the list is complete. But why does crosstool-NG have more steps?

    55 

    56 A- Credits

    57 

    58 B- Known issues

    59 

    60 C- Misc. tutorials

    61     - Using crosstool-NG on FreeBSD (and other *BSD)

    62     - Using crosstool-NG on MacOS-X

    63     - Using Mercurial to hack crosstool-NG
crosstool-ng