mirror of
https://github.com/esphome/esphome.git
synced 2026-09-16 09:38:42 +00:00
J. Nick Koston
998337e3b1
\`bme680_bsec\` pulls in the BSEC v1 library (single-instance API: \`bsec_init\`, \`bsec_set_configuration\`, …) and \`bme68x_bsec2\` pulls in the BSEC v2 library (multi-instance API: \`bsec_init_m\`, \`bsec_set_configuration_m\`, …). The two libraries export different symbol sets and can't coexist in one firmware image — linking them together currently fails with undefined references to the \`*_m\` symbols. This manifests in CI when the test-component grouping logic merges \`bme680_bsec\` and \`bme68x_bsec2_i2c\` into a single build. Declare \`CONFLICTS_WITH\` on both components so the config validator rejects the combination at config time with a clear message instead of leaving users to decode a linker failure.
