trick for compiler-config specific settings?
Posted: Tue Jun 17, 2014 10:27 pm
Hi guys,
do you have a suggestion for how to best handle multiple compiler-specific flavours?
I'm testing projects on various clang configs: libstdc++ or libc++ with either libcxxrt or libsupc++, plus various gcc versions/flavors. Each requires only slight changes to compiler/linker settings. It'd be unwieldy to have a different project configurations or even build-time wx-config type script which would have to be inserted in many fields and make build caching harder (more opaque).
I'm wondering if being able to chain env-var sets would be easiest, say an env var dependency directive like IMPORT_ENV_SET("base_set") so users can build hierarchical env var sets, possibly constructs like LINKER_FLAGS="${LINKER_FLAGS} -lc++ -lcxxrt", with CL throwing an error on a circular reference.
or is there a way to do this with existing features that I overlooked?
thx a lot & cheers!
-- p
do you have a suggestion for how to best handle multiple compiler-specific flavours?
I'm testing projects on various clang configs: libstdc++ or libc++ with either libcxxrt or libsupc++, plus various gcc versions/flavors. Each requires only slight changes to compiler/linker settings. It'd be unwieldy to have a different project configurations or even build-time wx-config type script which would have to be inserted in many fields and make build caching harder (more opaque).
I'm wondering if being able to chain env-var sets would be easiest, say an env var dependency directive like IMPORT_ENV_SET("base_set") so users can build hierarchical env var sets, possibly constructs like LINKER_FLAGS="${LINKER_FLAGS} -lc++ -lcxxrt", with CL throwing an error on a circular reference.
or is there a way to do this with existing features that I overlooked?
thx a lot & cheers!
-- p