config/global/paths.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 17 23:06:02 2010 +0100 (2010-01-17)
changeset 1740 c57458bb354d
parent 1509 f79fcf38ec21
child 1865 6a0b74b87dbd
permissions -rw-r--r--
configure: do not require hg when configuring in an hg clone

When configuring in an hg clone, we need hg to compute the version string.
It can happen that users do not have Mercurial (eg. if they got a snapshot
rather that they did a full clone). In this case, we can still run, of
course, so simply fill the version string with a sufficiently explicit
value, that does not require hg. The date is a good candidate.
yann@445
     1
# Options related to paths and install
yann@1
     2
yann@1
     3
comment "Paths"
yann@1
     4
yann@85
     5
config LOCAL_TARBALLS_DIR
yann@1
     6
    string
yann@85
     7
    prompt "Local tarballs directory"
yann@85
     8
    default ""
yann@1
     9
    help
yann@85
    10
      If you have previously downloaded the tarballs, enter the PATH where
yann@85
    11
      you stored them here.
yann@31
    12
yann@265
    13
config SAVE_TARBALLS
yann@265
    14
    bool
yann@265
    15
    prompt "Save new tarballs"
yann@265
    16
    default n
yann@265
    17
    depends on LOCAL_TARBALLS_DIR != ""
yann@265
    18
    help
yann@425
    19
      If you say 'y' here, new downloaded tarballs will be saved in the
yann@265
    20
      directory you entered above.
yann@265
    21
yann@610
    22
config WORK_DIR
yann@610
    23
    string
yann@610
    24
    prompt "Working directory"
yann@610
    25
    default "${CT_TOP_DIR}/targets"
yann@610
    26
    help
yann@610
    27
      Set this to the directory where all build actions will be done.
yann@610
    28
      
yann@610
    29
      The default is "${CT_TOP_DIR}/targets", and leaving this option
yann@610
    30
      empty will also use the default.
yann@610
    31
      
yann@610
    32
      You should not need to change that, except in one very peculiar
yann@610
    33
      setup:
yann@610
    34
       - your crosstool-NG source directory is on the network
yann@610
    35
       - you configured crosstool-NG with --local
yann@610
    36
      This kind of setup is a pain, as any action involving source file
yann@610
    37
      access would have to go through the wire. In this case, you should
yann@610
    38
      set CT_WORK_DIR to point to a path local to your machine, to avoid
yann@610
    39
      any network overhead.
yann@610
    40
      
yann@610
    41
      Do *NOT* change it if you don't know better.
yann@610
    42
yann@1
    43
config PREFIX_DIR
yann@1
    44
    string
yann@1
    45
    prompt "Prefix directory"
yann@613
    46
    default "${HOME}/x-tools/${CT_TARGET}"
yann@1
    47
    help
yann@1
    48
      This is the path the toolchain will run from.
yann@1
    49
yann@1
    50
config INSTALL_DIR
yann@1
    51
    string
yann@1
    52
#    prompt "Install directory"
yann@1
    53
    default "${CT_PREFIX_DIR}"
yann@1
    54
#    help
yann@610
    55
#      This is the path the toolchain will be installed into.
yann@1
    56
#      
yann@1
    57
#      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
yann@1
    58
#      you can't write there, you can install somewhere else and have a third
yann@1
    59
#      person do the install for you.
yann@1
    60
#      The reason you might also want to install elsewhere is if you are going
yann@1
    61
#      to package your shinny new toolchain for distribution.
yann@1
    62
yann@14
    63
config REMOVE_DOCS
yann@14
    64
    bool
yann@14
    65
    prompt "Remove documentation"
yann@753
    66
    default y
yann@14
    67
    help
yann@14
    68
      Remove the installed documentation (man and info pages).
yann@14
    69
      Gains around 8MiB for a uClibc-based, C and C++ compiler.
yann@14
    70
yann@174
    71
config INSTALL_DIR_RO
yann@174
    72
    bool
yann@174
    73
    prompt "Render the toolchain read-only"
yann@753
    74
    default y
yann@174
    75
    help
yann@174
    76
      Render the directory of the toolchain (and its sub-directories)
yann@174
    77
      read-only.
yann@174
    78
      
yann@174
    79
      Usefull for toolchains destined for production.