bartoszek/zephyr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
da299ecd47
zephyr/scripts/sanity_chk
History
Peter Mitsis 9d63adf3ea Renames supported platform configurations 
Renames supported platform configurations to conform to new platform
configuration naming scheme.

Example usage with PLATFORM_CONFIG:
    make PLATFORM_CONFIG=basic_cortex_m3
    make PLATFORM_CONFIG=basic_atom
    make PLATFORM_CONFIG=basic_minuteia
    make PLATFORM_CONFIG=galileo

  xxx_ti_lm3s6965_defconfig           -> xxx_basic_cortex_m3_defconfig
  xxx_generic_pc_atom_n28xx_defconfig -> xxx_basic_atom_defconfig
  xxx_generic_pc_minuteia_defconfig   -> xxx_basic_minuteia_defconfig
  xxx_quark_defconfig                 -> xxx_galileo_defconfig

Change-Id: I696eb8b9ad9a72d7a72efbe1341ce23500335764
Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>
2016-02-05 20:14:39 -05:00
..
bt_regression_chk Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00
bt_regression_chk.data Renames supported platform configurations 2016-02-05 20:14:39 -05:00
common.defs Renames supported platform configurations 2016-02-05 20:14:39 -05:00
footprint_chk Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00
footprint_chk.data Renames supported platform configurations 2016-02-05 20:14:39 -05:00
out-of-tree_chk Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00
out-of-tree_chk.data Renames supported platform configurations 2016-02-05 20:14:39 -05:00
README.txt sanity: Key off platform instead of BSP 2016-02-05 20:14:21 -05:00
regression_chk Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00
regression_chk.data Renames supported platform configurations 2016-02-05 20:14:39 -05:00
sanity_chk Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00

README.txt 

Sanity Check Data Files
=======================

The sanity check data files contain project metadata that is parsed by the
relevant sanity check script to both build and run the listed projects.

Project metadata consists of:
 - project directory (relative to PRJ_PATH - defined in the script)
 - build arguments (optional)
 - project flags, enclosed in angle brackets "<>"
   - 'u' => microkernel; 'n' => nanokernel (required; must be first flag)
   - 'q' => run as part of quick sanity check (optional)
 - list of platform names that can be used with the project

It is important that each set of project metadata be specified on a single line.

The sanity check scripts will select first listed platform name if the user
does not specify a platform name (i.e. is the "default" platform).

A given project can appear more than once, allowing the project to be
sanitized multiple times. This can be useful if the project has multiple
configurations, or if the project should be characterized on more than one
platform during a default platform sanity check.

Comment lines are permitted (denoted by '#').