> I have serious doubts concerning concentration on 3 compilers when in
> embedded environment the compiler is likely to be produced by a company, one
> may never have heard of before
Most embedded compilers follow GCC though when it comes to command line
options, many are forks of GCC in fact. But you can also use `--compileOnly`
and compile the `.c` files in `nimcache` on your own.
> The problem could have been easily avoided by providing an option to generate
> C files only without attempt to control the compiler based on obscure (read:
> mostly undocumented) information
How so? And what exactly needs to be documented? I'm too dumb to see what needs
to be documented here:
cc = gcc
# additional options always passed to the compiler:
--parallel_build: "0" # 0 to auto-detect number of processors
hint[LineTooLong]=off
#hint[XDeclaredButNotUsed]=off
# example of how to setup a cross-compiler:
arm.linux.gcc.exe = "arm-linux-gcc"
arm.linux.gcc.linkerexe = "arm-linux-gcc"
mips.linux.gcc.exe = "mips-openwrt-linux-gcc"
mips.linux.gcc.linkerexe = "mips-openwrt-linux-gcc"
...
# Configuration for the LLVM CLang compiler:
clang.options.debug = "-g"
clang.options.always = "-w"
clang.options.speed = "-O3"
clang.options.size = "-Os"
