diff options
author | Tido Klaassen <tido@4gh.eu> | 2015-10-06 09:04:14 +0300 |
---|---|---|
committer | Karl Palsson <karlp@tweak.net.au> | 2015-10-11 22:14:25 +0300 |
commit | aad8d06c3f0f3a248c983c6186db7f8d439059c1 (patch) | |
tree | f54329e54a3ec807819e7d5c3ea3fb5986065db1 /README.md | |
parent | 9217a5f888019236e8fc41f5803310f7ac661360 (diff) |
make: rename CFLAGS in target Makefiles to TGT_CFLAGS
Renamed every instance of variable CFLAGS in target specific Makefiles
to TGT_CFLAGS to free up CFLAGS for user defined compiler flags.
Added information in README.md about existence and usage of CFLAGS
environment variable in build process.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -90,6 +90,7 @@ them as environment variables, for example: $ VARIABLE=value make * `FP_FLAGS` - Control the floating-point ABI + If the Cortex-M core supports a hard float ABI, it will be compiled with floating-point support by default. In cases where this is not desired, the behavior can be specified by setting `FP_FLAGS` Currently, M4F cores default @@ -100,6 +101,17 @@ them as environment variables, for example: $ FP_FLAGS="-mfloat-abi=soft" make # No hardfloat $ FP_FLAGS="-mfloat-abi=hard -mfpu=magic" make # New FPU we don't know of +* `CFLAGS` - Add to or supersede compiler flags + + If the library needs to be compiled with additional flags, they can be + passed to the build system via the environment variable `CFLAGS`. The + contents of `CFLAGS` will be placed after all flags defined by the build + system, giving the user a way to override any default if necessary. + + Examples: + + $ CFLAGS="-fshort-wchar" make # compile lib with 2 byte wide wchar_t + Example projects ---------------- |