Make the bootstrap library not confuse static code checkers

Static code checkers (Coverity, cppchecker, ...) get confused by the bootstrap library. In our current setup, same source file is compiled twice (with different defines / flags), leading to strange reports.

I was wondering if there was a practical way to re-engineer the build of the bootstrap library so that it's not the very same path that gets built twice. For instance, the buildsystem could symlink or copy the source files of the bootstrap lib into the build dir, and build those paths instead.

(OTOH: this makes it harder to configure the code checker to correctly check the bootstrap lib itself! Usually source files in the build dir are ignored, as they're considered autogenerated).