* Get setting default values from settings.yaml
* settings: Make the generator more robust and versatile
- Add support for resolving types and values in multiple compilers
- Add support for resolving types and values in clang 10
- Add support for using the host compiler for resolving the settings
This allows us to run the generator for the unit tests, since they now
need the settings_generated.h file to get the default setting values
from it.
* Fix regexps in settings.rb and add execution bit
* Fix git revision issue
* Fix issue with settings validation
* Fix issue with targets not defining USE_MAG
Co-authored-by: Alberto García Hierro <alberto@garciahierro.com>
- Don't include target.h explicitely, it's already included
by platform.h
- Fix an error in compiled file as a test for discovering
contstants. Since we rely on compiler errors to give us the
resolved value, that lets us get one extra value on each run
- Always compile the test files for setting discovery in c++11
even if no -std=XXX argument is passed from the caller.
A build is considered changed if either the TARGET, CFLAGS or
the #define'd constants by including target.h and platform.h change
The Makefile now runs a new tool in src/utils/build_stamp.rb which
updates the file in obj/build.stamp iff the build has changed. This
allows us to make the generated files to depend on this stamp file
rather than rebuilding them all the time. Automatic dependencies
generated by the compiler take care of recompiling just the files
which depend on the generated ones.
