Closed KevinHopps closed 1 year ago
By auto-generating the config.hpp
file into the build directory, and having separate build directories for each unique configuration, and having two include dirs for stlab
builds, the problem is solved. Thank you, @sean-parent.
In our dev environment, we have multiple products and multiple platforms built on multiple libraries, many of which independently rely on
stlab
. We have been trying to move toward single copies of each of our library dependencies, includingstlab
. So solving this problem by requiring each to have its own copy ofstlab
is not a viable option for us.And, requiring a developer to re-generate
config.hpp
each time they want to switch to working on a different product is cumbersome as well as time-consuming, having to rebuild everything that depends onconfig.hpp
directly or indirectly.One example of this would be trying to simultaneously develop a product for MacOS as well as Web using emscripten.
Any chance we could switch back to a static
config.hpp
?