Skip to content

Commit eac084f

Browse files
Use BoringSSL for python controller build (#33964)
Problem: - OpenSSL can vary per build machine, causing non-hermetic builds This PR: - Selects boringssl (built from tree) as default CHIP crypto backend for Python controller Testing done: - All Python unit tests and integration tests still pass
1 parent 917cf26 commit eac084f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

scripts/build_python.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,7 @@ export SYSTEM_VERSION_COMPAT=0
184184
# Make all possible human redable tracing available.
185185
tracing_options="matter_log_json_payload_hex=true matter_log_json_payload_decode_full=true matter_enable_tracing_support=true"
186186

187-
gn --root="$CHIP_ROOT" gen "$OUTPUT_ROOT" --args="$tracing_options chip_detail_logging=$chip_detail_logging enable_pylib=$enable_pybindings enable_rtti=$enable_pybindings chip_project_config_include_dirs=[\"//config/python\"] $chip_mdns_arg $chip_case_retry_arg $pregen_dir_arg chip_config_network_layer_ble=$enable_ble chip_enable_ble=$enable_ble"
187+
gn --root="$CHIP_ROOT" gen "$OUTPUT_ROOT" --args="$tracing_options chip_detail_logging=$chip_detail_logging enable_pylib=$enable_pybindings enable_rtti=$enable_pybindings chip_project_config_include_dirs=[\"//config/python\"] $chip_mdns_arg $chip_case_retry_arg $pregen_dir_arg chip_config_network_layer_ble=$enable_ble chip_enable_ble=$enable_ble chip_crypto=\"boringssl\""
188188

189189
function ninja_target() {
190190
# Print the ninja target required to build a gn label.

0 commit comments

Comments
 (0)