Closed msandstedt closed 3 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.94. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
I seem to have a fix with simply the following:
commit e64fbc3226571b73b816241874357edc9d4634bb (HEAD -> fix_ble, mine/fix_ble)
Author: Michael Sandstedt <michael.sandstedt@smartthings.com>
Date: Tue Oct 13 09:18:19 2020 -0500
[build] fix linux builds with chip_enable_ble=false (#3179)
diff --git a/src/BUILD.gn b/src/BUILD.gn
index 863be6f6..d29ec3b5 100644
--- a/src/BUILD.gn
+++ b/src/BUILD.gn
@@ -27,8 +27,8 @@ config("includes") {
defines = [ "CHIP_SEPARATE_CONFIG_H=1" ]
- if (current_os == "linux") {
- defines += [ "CHIP_DEVICE_CONFIG_ENABLE_CHIPOBLE=1" ]
+ if (chip_device_platform == "linux") {
+ defines += [ "CHIP_DEVICE_CONFIG_ENABLE_CHIPOBLE=${chip_enable_ble}" ]
}
}
I will submit a PR shortly.
Problem
I cannot get connectedhomeip to build for Linux and Darwin targets at HEAD of master with chip_config_network_layer_ble=false. I am testing at this hash:
Reproducer is:
At this hash I am able to make this build work with the following changes:
That is the latest commit at which I'm able to build with this flag. Immediately after that, this commit seems to break the build for other reasons, that are now resolved in master, but make it impossible to bisect further to locate other regressions related to build with chip_config_network_layer_ble=false: