steps.mk
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sun May 11 13:38:12 2014 +0200 (2014-05-11)
changeset 3313 ad14212ebf54
parent 3123 6a5946fbc728
permissions -rw-r--r--
config: switch cc with libc in the config order

Some of the compiler options depend on the C library choice, (e.g.
whether core passes are needed).

Since the compiler menu comes before the C library menu, those options
may or may not be visible until the C library is chosen, leading to
either options being visible by the user (thus be puzzling as they would
not apply to his case), or invisible to him (yet again puzzling him).

Invert the order of the compiler and the C library in the menuconfig. It
anyway looks more rational, in the end.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
     1 # Makefile for each steps
     2 # Copyright 2006 Yann E. MORIN <yann.morin.1998@free.fr>
     3 
     4 # ----------------------------------------------------------
     5 # This is the steps help entry
     6 
     7 help-build::
     8 	@echo  '  list-steps         - List all build steps'
     9 
    10 help-env::
    11 	@echo  '  STOP=step          - Stop the build just after this step (list with list-steps)'
    12 	@echo  '  RESTART=step       - Restart the build just before this step (list with list-steps)'
    13 
    14 # ----------------------------------------------------------
    15 # The steps list
    16 
    17 # The _for_build steps are noop for native and cross,
    18 # but are actual steps for canadian and cross-native.
    19 # Please keep the last line with a '\' and keep the following empy line:
    20 # it helps when diffing and merging.
    21 CT_STEPS := libc_check_config        \
    22             companion_libs_for_build \
    23             binutils_for_build       \
    24             companion_libs_for_host  \
    25             binutils_for_host        \
    26             cc_core_pass_1           \
    27             kernel_headers           \
    28             libc_start_files         \
    29             cc_core_pass_2           \
    30             libc                     \
    31             cc_for_build             \
    32             cc_for_host              \
    33             libelf_for_target        \
    34             binutils_for_target      \
    35             debug                    \
    36             test_suite               \
    37             finish                   \
    38 
    39 # Keep an empty line above this comment, so the last
    40 # back-slash terminated line works as expected.
    41 
    42 # Make the list available to sub-processes (scripts/crosstool-NG.sh needs it)
    43 export CT_STEPS
    44 
    45 # Print the steps list
    46 PHONY += list-steps
    47 list-steps:
    48 	@echo  'Available build steps, in order:'
    49 	@for step in $(CT_STEPS); do    \
    50 	     echo "  - $${step}";       \
    51 	 done
    52 	@echo  'Use "<step>" as action to execute only that step.'
    53 	@echo  'Use "+<step>" as action to execute up to that step.'
    54 	@echo  'Use "<step>+" as action to execute from that step onward.'
    55 
    56 # ----------------------------------------------------------
    57 # This part deals with executing steps
    58 
    59 $(CT_STEPS):
    60 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$@ STOP=$@ build
    61 
    62 $(patsubst %,+%,$(CT_STEPS)):
    63 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) STOP=$(patsubst +%,%,$@) build
    64 
    65 $(patsubst %,%+,$(CT_STEPS)):
    66 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$(patsubst %+,%,$@) build