ff10687a6c
Previously, ports that were needed for a scenario and that were not prepared or outdated, triggered one assertion each during the second build stage. The commit slots a mechanism in ahead that gathers all these ports during the first build stage and reports them in form of a list before the second build stage is entered. This list can be used directly as argument for tool/ports/prepare_port to prepare respectively update the ports. If, however, this mechanism is not available, for example because a target is build without the first build stage, the old assertion still prevents the target from running into troubles with a missing port. Fixes #1872 |
||
|---|---|---|
| .. | ||
| spec | ||
| README | ||
| base-libs.mk | ||
| dep_lib.mk | ||
| dep_prg.mk | ||
| generic.mk | ||
| global.mk | ||
| lib.mk | ||
| prg.mk | ||
| util.inc | ||
README
This directory contains the build system. In consists mainly of makefile templates for different directory roles. :'global.mk': This file contains global variables, for example the definitions of the tools to use. :'generic.mk': Generic rules for creating file types from others. :'prg.mk': This file represents the target binary role of a directory. It must be included by all makefiles that build programs. :'lib.mk': This file represents a library role. It is never used from within the 'src/' directory but only from the <libname>.mk files in 'lib/mk/'.