docs/7 - Contributing to crosstool-NG.txt
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu May 26 22:51:03 2011 +0200 (2011-05-26)
changeset 2481 30644208c955
parent 2076 b58109b7b321
child 2563 e17f35b05539
permissions -rw-r--r--
configure: add possibility to set arbitrary variable in check_for

If check_for is able to find the required prog/inc/lib, allow it to
set an arbitrary variable to 'y'. This variable is then pushed down
to the kconfig definition.

For example:
has_or_abort prog=foobar kconfig=has_foobar

If foobar is available, it yields a kconfig variable defaulting to y:
config CONFIGURE_has_foobar
bool
default y

If foobar is missing, it yields a kconfig variable defaulting to n:
config CONFIGURE_has_foobar
bool

Thus it is possible to depends on that variabel to show/hide options:
config SOME_FEATURE
bool
prompt "Some feature"
depends on CONFIGURE_has_foobar

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@2076
     1
File.........: 7 - Contributing to crosstool-NG.txt
yann@2076
     2
Copyrigth....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
yann@2076
     3
License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
yann@2076
     4
yann@2076
     5
yann@2076
     6
Contributing to crosstool-NG  /
yann@2076
     7
_____________________________/
yann@2076
     8
yann@2076
     9
yann@2076
    10
Sending a bug report |
yann@2076
    11
---------------------+
yann@2076
    12
yann@2076
    13
If you need to send a bug report, please send a mail with subject
yann@2076
    14
prefixed with "[CT_NG]" with to following destinations:
yann@2076
    15
    TO: yann.morin.1998 (at) anciens.enib.fr
yann@2076
    16
    CC: crossgcc (at) sourceware.org
yann@2076
    17
yann@2076
    18
yann@2076
    19
Sending patches |
yann@2076
    20
----------------+
yann@2076
    21
yann@2076
    22
If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
yann@2076
    23
yann@2076
    24
Patches should come with the appropriate SoB line. A SoB line is typically
yann@2076
    25
something like:
yann@2076
    26
   Signed-off-by: John DOE <john.doe@somewhere.net>
yann@2076
    27
yann@2076
    28
The SoB line is clearly described in Documentation/SubmittingPatches , section
yann@2076
    29
12, of your favourite Linux kernel source tree.
yann@2076
    30
yann@2076
    31
yann@2076
    32
For larger or more frequent contributions, mercurial should be used.
yann@2077
    33
There is a nice, complete and step-by-step tutorial in section 'C'.