bazel: reorganize dbg configs #2457
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Rafal Augustyniak <[email protected]>
Signed-off-by: Rafal Augustyniak <[email protected]>
Signed-off-by: Rafal Augustyniak <[email protected]>
|
/retest |
keith
approved these changes
Aug 5, 2022
|
/retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: After finding an interface binding related crash in #2456 I noticed that our
dbgbazel config does not specify--define=include_ifaddrs=truewhich is supposed to ensure that we compile code that's required for proper functioning of Envoy Mobile on Android. Introducedbg-androidanddbg-ioswhich are intended to be platform specificdbgconfigurations.Risk Level: None, does not impact release configurations.
Testing: Ran Kotlin example app manually.
Docs Changes: N/A
Release Notes: N/A
Signed-off-by: Rafal Augustyniak [email protected]