-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom values of CMAKE_BUILD_TYPE #17106
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
Maybe we should mark this one as |
rules_foreign_cc sets this automatically to either Debug or Release based on bazel's compilation_mode. Overriding this can cause issues when deps' cmake configs expect to be in a specific subset of configs. Unlike LLVM most cmake configs seem to silently fail in that case by not setting an expected var correctly. I hit this issue when updating rules_foreign_cc (I'm not sure of why the update broke it) and wamr missing some settings for the custom Bazel config. Fixes: envoyproxy#17106 Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Testing if removing it works at this point #17679 |
Title: Allow custom values of CMAKE_BUILD_TYPE
Description:
Currently Envoy's build system sets
CMAKE_BUILD_TYPE
toBazel
unconditionally (since #8280). Yet some CMake-based dependencies modify e.g. defines or CFLAGS for different build types. The conventional values areDebug
,Release
,RelWithDebInfo
etc.It would be nice for debug purposes (or for enabling optimizations) to override
CMAKE_BUILD_TYPE
in theenvoy_cmake_external()
rule.The text was updated successfully, but these errors were encountered: