mirror
/
esp-idf
kopia lustrzana https://github.com/espressif/esp-idf
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
esp-idf/tools/test_apps/system/no_embedded_paths
Historia
Marius Vikhammer 2aead8ba57 Support ESP32S3 Beta 3 target 
Update ROM API. Port changes from bringup branch.
 		2021-03-18 10:24:22 +08:00
..
main config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
CMakeLists.txt config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
README.md Support ESP32S3 Beta 3 target 2021-03-18 10:24:22 +08:00
check_for_file_paths.py ci: Add a test app for not placing embedded file paths into binaries 2021-03-03 10:31:05 +11:00
sdkconfig.ci.noasserts config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
sdkconfig.ci.noasserts.nimble config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
sdkconfig.ci.replacepaths config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
sdkconfig.ci.silentasserts config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00
sdkconfig.ci.silentasserts.nimble config: Add new option to replace IDF_PATH and project path with placeholders in macros 2021-03-03 10:31:05 +11:00

README.md

Supported Targets ESP32 ESP32-S2 ESP32-C3

No Embedded Paths

This test app exists to verify that paths (like FILE) are not compiled into any object files in configurations where this should be avoided.

Configurations where this is relevant include:

  • Assertions disabled (doubles up as a build-time check that disabling assertions doesn't lead to any warnings)
  • Silent assertions
  • CONFIG_COMPILER_HIDE_PATHS_MACROS is set to replace IDF_PATH and project dir with placeholders when expanding __FILE__

Not embedding paths reduces the binary size, avoids leaking information about the compilation environment, and is a necessary step to support reproducible builds across projects built in different directories.