Ben Meadors
cad3a3a5c7
Range test is excluded on every target as of 2.8, so set MESHTASTIC_EXCLUDE_RANGETEST=1 globally in [env] build_flags and drop the now-redundant per-variant flags from esp32, rak11200 and stm32. Guard RangeTestModule.cpp with the same condition used in Modules.cpp so the translation unit compiles to nothing rather than relying on --gc-sections to strip it, and always report RANGETEST_CONFIG in the device metadata excluded_modules bitmask so clients hide the config.
23 lines
623 B
INI
23 lines
623 B
INI
[env:rak11200]
|
|
custom_meshtastic_hw_model = 13
|
|
custom_meshtastic_hw_model_slug = RAK11200
|
|
custom_meshtastic_architecture = esp32
|
|
custom_meshtastic_actively_supported = true
|
|
custom_meshtastic_support_level = 3
|
|
custom_meshtastic_display_name = RAK WisBlock 11200
|
|
custom_meshtastic_images = rak11200.svg
|
|
custom_meshtastic_tags = RAK
|
|
|
|
extends = esp32_base
|
|
board = wiscore_rak11200
|
|
board_level = pr
|
|
board_check = true
|
|
build_flags =
|
|
${esp32_base.build_flags}
|
|
-D RAK_11200
|
|
-I variants/esp32/rak11200
|
|
-DMESHTASTIC_EXCLUDE_WEBSERVER=1
|
|
-DMESHTASTIC_EXCLUDE_PAXCOUNTER=1
|
|
-DMESHTASTIC_EXCLUDE_MQTT=1
|
|
upload_speed = 115200
|