arch/powerpc/config.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Wed Oct 01 18:10:40 2008 +0000 (2008-10-01)
changeset 894 c444ce4b51b9
parent 815 6236ce3be104
permissions -rw-r--r--
Save the toolchain configuration to its own file, as an auto-extracting shell script:
- get rid of the 'extractconfig' action, it was cumbersome to use, and badly documented,
- introduce a skeleton for the config script,
- update auto-completion,
- document the config script.

/trunk/kconfig/kconfig.mk | 9 2 7 0 ++-------
/trunk/scripts/crosstool.sh | 6 5 1 0 +++++-
/trunk/docs/overview.txt | 21 9 12 0 +++++++++------------
/trunk/tools/toolchain-config.in | 8 8 0 0 ++++++++
/trunk/ct-ng.comp | 2 1 1 0 +-
5 files changed, 25 insertions(+), 21 deletions(-)
     1 # powerpc specific configuration file
     2 
     3 config ARCH_powerpc
     4     select ARCH_SUPPORT_ABI
     5     select ARCH_SUPPORT_CPU
     6     select ARCH_SUPPORT_TUNE
     7     help
     8       The PowerPC architecture, as defined by:
     9         http://www.ibm.com/developerworks/eserver/articles/archguide.html
    10 
    11 config ARCH_POWERPC_SPE
    12     bool
    13     prompt "Enable SPE support"
    14     default n
    15     help
    16       Add support for the Signal Processing Engine.  This will set up
    17       the toolchain so that it supports the SPE ABI extensions. This
    18       mainly targets Freescale e500 processors.
    19 
    20       Setting this option will append "spe" to the end of your target
    21       tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
    22       configure/build system will know to include SPE ABI support.
    23       It will also automatically add "-mabi=spe -mspe" to your
    24       TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
    25       so you do not need to explicitly add them.