esp-idf/components/esp32/Makefile.projbuild

# Enable psram cache bug workaround in compiler if selected
ifdef CONFIG_SPIRAM_CACHE_WORKAROUND
CFLAGS+=-mfix-esp32-psram-cache-issue
CXXFLAGS+=-mfix-esp32-psram-cache-issue
endif

# Enable dynamic esp_timer overflow value if building unit tests
ifneq ("$(filter esp32,$(TEST_COMPONENTS_LIST))","")
CPPFLAGS += -DESP_TIMER_DYNAMIC_OVERFLOW_VAL
endif
ESP32_LINKER_SCRIPT_TEMPLATE := $(COMPONENT_PATH)/ld/esp32.project.ld.in
ESP32_LINKER_SCRIPT_OUTPUT_DIR := $(abspath $(BUILD_DIR_BASE)/esp32)

# Target to generate linker script generator from fragments presented by each of
# the components
$(eval $(call ldgen_process_template, $(ESP32_LINKER_SCRIPT_TEMPLATE), $(ESP32_LINKER_SCRIPT_OUTPUT_DIR)/esp32.project.ld))
Add initial SPI RAM support. This adds support for an ESP-PSRAM32 chip connected to the default flash pins and GPIO 16 and 17. The RAM is mapped to address 0x3F800000, but otherwise ignored by esp-idf as of yet. 2017-07-20 04:26:35 -04:00			`# Enable psram cache bug workaround in compiler if selected`
			`ifdef CONFIG_SPIRAM_CACHE_WORKAROUND`
			`CFLAGS+=-mfix-esp32-psram-cache-issue`
			`CXXFLAGS+=-mfix-esp32-psram-cache-issue`
			`endif`

run WiFi on ESP32SBETA 2019-06-16 23:50:37 -04:00			`# Enable dynamic esp_timer overflow value if building unit tests`
esp32, mbedtls: check component name when enabling test flags Otherwise flags get enabled even when building tests for other components. 2018-11-19 11:49:38 -05:00			`ifneq ("$(filter esp32,$(TEST_COMPONENTS_LIST))","")`
esp_timer: reduce overflow value in unit tests This allows testing for race conditions which occur near timer overflow point more effectively. 2018-05-23 10:39:49 -04:00			`CPPFLAGS += -DESP_TIMER_DYNAMIC_OVERFLOW_VAL`
			`endif`
esp32: Rename esp32.common.ld to esp32.project.ld to avoid build errors when downgrading Linker script generator produces build/esp32/esp32.common.ld from components/esp32/ld/esp32.common.ld.in This works fine until IDF is downgraded to V3.1 which uses components/esp32/ld/esp32.common.ld and doesn't track build/esp32/esp32.common.ld at all. At this point, the linker runs in the build/esp32 directory and "-T esp32.common.ld" picks up the linker script generated .ld file, which causes mis-builds. As reported on forums: https://esp32.com/viewtopic.php?f=13&t=9684&p=40105 2019-03-13 18:59:31 -04:00			`ESP32_LINKER_SCRIPT_TEMPLATE := $(COMPONENT_PATH)/ld/esp32.project.ld.in`
tools: implement linker script generation 2018-04-17 22:57:45 -04:00			`ESP32_LINKER_SCRIPT_OUTPUT_DIR := $(abspath $(BUILD_DIR_BASE)/esp32)`

			`# Target to generate linker script generator from fragments presented by each of`
			`# the components`
esp32: Rename esp32.common.ld to esp32.project.ld to avoid build errors when downgrading Linker script generator produces build/esp32/esp32.common.ld from components/esp32/ld/esp32.common.ld.in This works fine until IDF is downgraded to V3.1 which uses components/esp32/ld/esp32.common.ld and doesn't track build/esp32/esp32.common.ld at all. At this point, the linker runs in the build/esp32 directory and "-T esp32.common.ld" picks up the linker script generated .ld file, which causes mis-builds. As reported on forums: https://esp32.com/viewtopic.php?f=13&t=9684&p=40105 2019-03-13 18:59:31 -04:00			`$(eval $(call ldgen_process_template, $(ESP32_LINKER_SCRIPT_TEMPLATE), $(ESP32_LINKER_SCRIPT_OUTPUT_DIR)/esp32.project.ld))`