rules.h: add fall through where no ENV_<STAGE> is set

There are cases where rules.h can be pulled in, but the
usage is not associated with a particular stage. For
example, the cpu/ti/am335x build creates an opmap header.
That is a case where there is no stage associated with
the process. Therefore, provide a case of no ENV_>STAGE>
being set.

BUG=chrome-os-partner:44827
BRANCH=None
TEST=Built a myriad of boards. Analyzed readelf output.

Change-Id: Ia9688886d445c961f4a448fc7bfcb28f691609db
Signed-off-by: Aaron Durbin <adubin@chromium.org>
Reviewed-on: http://review.coreboot.org/11513
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
Aaron Durbin 2015-09-04 16:28:15 -05:00
parent 6aa8c5bc58
commit cd96c5cf95
1 changed files with 15 additions and 1 deletions

View File

@ -63,13 +63,27 @@
#define ENV_SECMON 0
#define ENV_VERSTAGE 1
#else
#elif defined(__RAMSTAGE__)
#define ENV_BOOTBLOCK 0
#define ENV_ROMSTAGE 0
#define ENV_RAMSTAGE 1
#define ENV_SMM 0
#define ENV_SECMON 0
#define ENV_VERSTAGE 0
#else
/*
* Default case of nothing set for random blob generation using
* create_class_compiler that isn't bound to a stage. Also AGESA
* apparently builds things compeletely separate from coreboot's
* build infrastructure -- hardcoding its own rules.
*/
#define ENV_BOOTBLOCK 0
#define ENV_ROMSTAGE 0
#define ENV_RAMSTAGE 0
#define ENV_SMM 0
#define ENV_SECMON 0
#define ENV_VERSTAGE 0
#endif
/* For romstage and ramstage always build with simple device model, ie.