2020-09-23 06:55:55 +01:00
|
|
|
# Set location of base MicroPython directory.
|
2021-06-24 07:03:25 +01:00
|
|
|
if(NOT MICROPY_DIR)
|
esp32/CMake: Change PROJECT_DIR to CMAKE_CURRENT_LIST_DIR.
This migrates the CMake variable `MICROPY_PORT_DIR` from the ESP-IDF
defined project to the component. Previously used instances of the variable
within the project definition have been migrated to
`CMAKE_CURRENT_LIST_DIR`. Within the component (the `main` subdirectory in
the ESP32 port) we define `MICROPY_PORT_DIR` using `CMAKE_CURRENT_LIST_DIR`
and subsequently use the `MICROPY_PORT_DIR` value in all locations where
`PROJECT` had previously been used.
Context:
In commit 9b90882146, initial support was added for building with the newly
introduced CMake support provided by the ESP-IDF.
Specifically, the commit message states:
> This commit adds support for building the esp32 port with CMake, and in
particular, it builds MicroPython as a component within the ESP-IDF. Using
CMake and the ESP-IDF build infrastructure makes it much easier to maintain
the port, especially with the various new ESP32 MCUs and their required
toolchains.
`PROJECT_DIR` is a variable populated by the ESP-IDF specifically and is
not stable when used with "[Pure CMake components][1]" as documented in the
ESP-IDF. It is intended to be used in the scope of the parent of the
current file (the "project") as opposed to the current file ("the
component"). Crossing into the parent scope like this works solely when the
"project" is MicroPython, but not when used as a component by other ESP-IDF
projects.
Analyzing this file, the intention is to reference the "Project" which in
the example is the parent directory. Within the [CMake variables][2]
documentation, there is one specifically defined for referencing the
directory for the CMake listfile currently being processed:
[`CMAKE_CURRENT_LIST_DIR`][3].
After making the change from `PROJECT_DIR` to `CMAKE_CURRENT_LIST_DIR`, the
reach into the parent scope defined by the ESP-IDF and the resulting CMake
interface violation is removed.
Similar to the component definition, the project `CMakeLists.txt` uses the
variable `CMAKE_SOURCE_DIR` which CMake defines as "The path to the top
level of the source tree." This commit changes the variable to
`CMAKE_CURRENT_LIST_DIR` for the reasons cited above.
[1]: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/build-system.html#writing-pure-cmake-components
[2]: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
[3]: https://cmake.org/cmake/help/latest/variable/CMAKE_CURRENT_LIST_DIR.html
Signed-off-by: Brian 'redbeard' Harrington <redbeard@dead-city.org>
2023-06-12 21:02:10 +01:00
|
|
|
get_filename_component(MICROPY_DIR ${CMAKE_CURRENT_LIST_DIR}/../../.. ABSOLUTE)
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
if(NOT MICROPY_PORT_DIR)
|
|
|
|
|
get_filename_component(MICROPY_PORT_DIR ${MICROPY_DIR}/ports/esp32 ABSOLUTE)
|
2021-06-24 07:03:25 +01:00
|
|
|
endif()
|
2020-09-23 06:55:55 +01:00
|
|
|
|
|
|
|
|
# Include core source components.
|
|
|
|
|
include(${MICROPY_DIR}/py/py.cmake)
|
|
|
|
|
|
2021-03-27 21:10:39 +00:00
|
|
|
if(NOT CMAKE_BUILD_EARLY_EXPANSION)
|
2022-06-08 03:21:51 +01:00
|
|
|
# Enable extmod components that will be configured by extmod.cmake.
|
|
|
|
|
# A board may also have enabled additional components.
|
|
|
|
|
set(MICROPY_PY_BTREE ON)
|
|
|
|
|
|
2021-03-27 21:10:39 +00:00
|
|
|
include(${MICROPY_DIR}/py/usermod.cmake)
|
2021-04-08 14:45:28 +01:00
|
|
|
include(${MICROPY_DIR}/extmod/extmod.cmake)
|
2021-03-27 21:10:39 +00:00
|
|
|
endif()
|
|
|
|
|
|
2021-02-21 00:33:15 +00:00
|
|
|
set(MICROPY_QSTRDEFS_PORT
|
esp32/CMake: Change PROJECT_DIR to CMAKE_CURRENT_LIST_DIR.
This migrates the CMake variable `MICROPY_PORT_DIR` from the ESP-IDF
defined project to the component. Previously used instances of the variable
within the project definition have been migrated to
`CMAKE_CURRENT_LIST_DIR`. Within the component (the `main` subdirectory in
the ESP32 port) we define `MICROPY_PORT_DIR` using `CMAKE_CURRENT_LIST_DIR`
and subsequently use the `MICROPY_PORT_DIR` value in all locations where
`PROJECT` had previously been used.
Context:
In commit 9b90882146, initial support was added for building with the newly
introduced CMake support provided by the ESP-IDF.
Specifically, the commit message states:
> This commit adds support for building the esp32 port with CMake, and in
particular, it builds MicroPython as a component within the ESP-IDF. Using
CMake and the ESP-IDF build infrastructure makes it much easier to maintain
the port, especially with the various new ESP32 MCUs and their required
toolchains.
`PROJECT_DIR` is a variable populated by the ESP-IDF specifically and is
not stable when used with "[Pure CMake components][1]" as documented in the
ESP-IDF. It is intended to be used in the scope of the parent of the
current file (the "project") as opposed to the current file ("the
component"). Crossing into the parent scope like this works solely when the
"project" is MicroPython, but not when used as a component by other ESP-IDF
projects.
Analyzing this file, the intention is to reference the "Project" which in
the example is the parent directory. Within the [CMake variables][2]
documentation, there is one specifically defined for referencing the
directory for the CMake listfile currently being processed:
[`CMAKE_CURRENT_LIST_DIR`][3].
After making the change from `PROJECT_DIR` to `CMAKE_CURRENT_LIST_DIR`, the
reach into the parent scope defined by the ESP-IDF and the resulting CMake
interface violation is removed.
Similar to the component definition, the project `CMakeLists.txt` uses the
variable `CMAKE_SOURCE_DIR` which CMake defines as "The path to the top
level of the source tree." This commit changes the variable to
`CMAKE_CURRENT_LIST_DIR` for the reasons cited above.
[1]: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/build-system.html#writing-pure-cmake-components
[2]: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
[3]: https://cmake.org/cmake/help/latest/variable/CMAKE_CURRENT_LIST_DIR.html
Signed-off-by: Brian 'redbeard' Harrington <redbeard@dead-city.org>
2023-06-12 21:02:10 +01:00
|
|
|
${MICROPY_PORT_DIR}/qstrdefsport.h
|
2021-02-21 00:33:15 +00:00
|
|
|
)
|
|
|
|
|
|
2021-07-09 05:19:15 +01:00
|
|
|
set(MICROPY_SOURCE_SHARED
|
|
|
|
|
${MICROPY_DIR}/shared/readline/readline.c
|
|
|
|
|
${MICROPY_DIR}/shared/netutils/netutils.c
|
|
|
|
|
${MICROPY_DIR}/shared/timeutils/timeutils.c
|
|
|
|
|
${MICROPY_DIR}/shared/runtime/interrupt_char.c
|
|
|
|
|
${MICROPY_DIR}/shared/runtime/stdout_helpers.c
|
|
|
|
|
${MICROPY_DIR}/shared/runtime/sys_stdio_mphal.c
|
|
|
|
|
${MICROPY_DIR}/shared/runtime/pyexec.c
|
|
|
|
|
)
|
|
|
|
|
|
2020-09-23 06:55:55 +01:00
|
|
|
set(MICROPY_SOURCE_LIB
|
|
|
|
|
${MICROPY_DIR}/lib/littlefs/lfs1.c
|
|
|
|
|
${MICROPY_DIR}/lib/littlefs/lfs1_util.c
|
|
|
|
|
${MICROPY_DIR}/lib/littlefs/lfs2.c
|
|
|
|
|
${MICROPY_DIR}/lib/littlefs/lfs2_util.c
|
2023-04-30 22:24:26 +01:00
|
|
|
${MICROPY_DIR}/lib/mbedtls_errors/esp32_mbedtls_errors.c
|
2020-09-23 06:55:55 +01:00
|
|
|
${MICROPY_DIR}/lib/oofatfs/ff.c
|
|
|
|
|
${MICROPY_DIR}/lib/oofatfs/ffunicode.c
|
|
|
|
|
)
|
esp32: Add initial support for ESP32C3 SoCs.
Supported features for this SoC are:
- UART REPL, filesystem
- Pin, ADC, PWM, SoftI2C, SoftSPI, Timer, RTC
- OneWire, DHT, NeoPixel
- RMT
- WiFi, Bluetooth
Signed-off-by: Damien George <damien@micropython.org>
2021-07-18 03:11:21 +01:00
|
|
|
if(IDF_TARGET STREQUAL "esp32c3")
|
|
|
|
|
list(APPEND MICROPY_SOURCE_LIB ${MICROPY_DIR}/shared/runtime/gchelper_generic.c)
|
|
|
|
|
endif()
|
2020-09-23 06:55:55 +01:00
|
|
|
|
|
|
|
|
set(MICROPY_SOURCE_DRIVERS
|
|
|
|
|
${MICROPY_DIR}/drivers/bus/softspi.c
|
|
|
|
|
${MICROPY_DIR}/drivers/dht/dht.c
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
set(MICROPY_SOURCE_PORT
|
esp32/CMake: Change PROJECT_DIR to CMAKE_CURRENT_LIST_DIR.
This migrates the CMake variable `MICROPY_PORT_DIR` from the ESP-IDF
defined project to the component. Previously used instances of the variable
within the project definition have been migrated to
`CMAKE_CURRENT_LIST_DIR`. Within the component (the `main` subdirectory in
the ESP32 port) we define `MICROPY_PORT_DIR` using `CMAKE_CURRENT_LIST_DIR`
and subsequently use the `MICROPY_PORT_DIR` value in all locations where
`PROJECT` had previously been used.
Context:
In commit 9b90882146, initial support was added for building with the newly
introduced CMake support provided by the ESP-IDF.
Specifically, the commit message states:
> This commit adds support for building the esp32 port with CMake, and in
particular, it builds MicroPython as a component within the ESP-IDF. Using
CMake and the ESP-IDF build infrastructure makes it much easier to maintain
the port, especially with the various new ESP32 MCUs and their required
toolchains.
`PROJECT_DIR` is a variable populated by the ESP-IDF specifically and is
not stable when used with "[Pure CMake components][1]" as documented in the
ESP-IDF. It is intended to be used in the scope of the parent of the
current file (the "project") as opposed to the current file ("the
component"). Crossing into the parent scope like this works solely when the
"project" is MicroPython, but not when used as a component by other ESP-IDF
projects.
Analyzing this file, the intention is to reference the "Project" which in
the example is the parent directory. Within the [CMake variables][2]
documentation, there is one specifically defined for referencing the
directory for the CMake listfile currently being processed:
[`CMAKE_CURRENT_LIST_DIR`][3].
After making the change from `PROJECT_DIR` to `CMAKE_CURRENT_LIST_DIR`, the
reach into the parent scope defined by the ESP-IDF and the resulting CMake
interface violation is removed.
Similar to the component definition, the project `CMakeLists.txt` uses the
variable `CMAKE_SOURCE_DIR` which CMake defines as "The path to the top
level of the source tree." This commit changes the variable to
`CMAKE_CURRENT_LIST_DIR` for the reasons cited above.
[1]: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/build-system.html#writing-pure-cmake-components
[2]: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
[3]: https://cmake.org/cmake/help/latest/variable/CMAKE_CURRENT_LIST_DIR.html
Signed-off-by: Brian 'redbeard' Harrington <redbeard@dead-city.org>
2023-06-12 21:02:10 +01:00
|
|
|
main.c
|
|
|
|
|
uart.c
|
|
|
|
|
usb.c
|
|
|
|
|
usb_serial_jtag.c
|
|
|
|
|
gccollect.c
|
|
|
|
|
mphalport.c
|
|
|
|
|
fatfs_port.c
|
|
|
|
|
help.c
|
|
|
|
|
machine_bitstream.c
|
|
|
|
|
machine_timer.c
|
|
|
|
|
machine_pin.c
|
|
|
|
|
machine_touchpad.c
|
|
|
|
|
machine_adc.c
|
|
|
|
|
machine_adcblock.c
|
|
|
|
|
machine_dac.c
|
|
|
|
|
machine_i2c.c
|
|
|
|
|
machine_i2s.c
|
|
|
|
|
machine_uart.c
|
|
|
|
|
modmachine.c
|
|
|
|
|
network_common.c
|
|
|
|
|
network_lan.c
|
|
|
|
|
network_ppp.c
|
|
|
|
|
network_wlan.c
|
|
|
|
|
mpnimbleport.c
|
|
|
|
|
modsocket.c
|
|
|
|
|
modesp.c
|
|
|
|
|
esp32_nvs.c
|
|
|
|
|
esp32_partition.c
|
|
|
|
|
esp32_rmt.c
|
|
|
|
|
esp32_ulp.c
|
|
|
|
|
modesp32.c
|
|
|
|
|
machine_hw_spi.c
|
|
|
|
|
machine_wdt.c
|
|
|
|
|
mpthreadport.c
|
|
|
|
|
machine_rtc.c
|
|
|
|
|
machine_sdcard.c
|
|
|
|
|
modespnow.c
|
2020-09-23 06:55:55 +01:00
|
|
|
)
|
esp32/CMake: Change PROJECT_DIR to CMAKE_CURRENT_LIST_DIR.
This migrates the CMake variable `MICROPY_PORT_DIR` from the ESP-IDF
defined project to the component. Previously used instances of the variable
within the project definition have been migrated to
`CMAKE_CURRENT_LIST_DIR`. Within the component (the `main` subdirectory in
the ESP32 port) we define `MICROPY_PORT_DIR` using `CMAKE_CURRENT_LIST_DIR`
and subsequently use the `MICROPY_PORT_DIR` value in all locations where
`PROJECT` had previously been used.
Context:
In commit 9b90882146, initial support was added for building with the newly
introduced CMake support provided by the ESP-IDF.
Specifically, the commit message states:
> This commit adds support for building the esp32 port with CMake, and in
particular, it builds MicroPython as a component within the ESP-IDF. Using
CMake and the ESP-IDF build infrastructure makes it much easier to maintain
the port, especially with the various new ESP32 MCUs and their required
toolchains.
`PROJECT_DIR` is a variable populated by the ESP-IDF specifically and is
not stable when used with "[Pure CMake components][1]" as documented in the
ESP-IDF. It is intended to be used in the scope of the parent of the
current file (the "project") as opposed to the current file ("the
component"). Crossing into the parent scope like this works solely when the
"project" is MicroPython, but not when used as a component by other ESP-IDF
projects.
Analyzing this file, the intention is to reference the "Project" which in
the example is the parent directory. Within the [CMake variables][2]
documentation, there is one specifically defined for referencing the
directory for the CMake listfile currently being processed:
[`CMAKE_CURRENT_LIST_DIR`][3].
After making the change from `PROJECT_DIR` to `CMAKE_CURRENT_LIST_DIR`, the
reach into the parent scope defined by the ESP-IDF and the resulting CMake
interface violation is removed.
Similar to the component definition, the project `CMakeLists.txt` uses the
variable `CMAKE_SOURCE_DIR` which CMake defines as "The path to the top
level of the source tree." This commit changes the variable to
`CMAKE_CURRENT_LIST_DIR` for the reasons cited above.
[1]: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/build-system.html#writing-pure-cmake-components
[2]: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
[3]: https://cmake.org/cmake/help/latest/variable/CMAKE_CURRENT_LIST_DIR.html
Signed-off-by: Brian 'redbeard' Harrington <redbeard@dead-city.org>
2023-06-12 21:02:10 +01:00
|
|
|
list(TRANSFORM MICROPY_SOURCE_PORT PREPEND ${MICROPY_PORT_DIR}/)
|
2020-09-23 06:55:55 +01:00
|
|
|
|
|
|
|
|
set(MICROPY_SOURCE_QSTR
|
|
|
|
|
${MICROPY_SOURCE_PY}
|
|
|
|
|
${MICROPY_SOURCE_EXTMOD}
|
2021-03-27 21:10:39 +00:00
|
|
|
${MICROPY_SOURCE_USERMOD}
|
2021-07-09 05:19:15 +01:00
|
|
|
${MICROPY_SOURCE_SHARED}
|
2020-09-23 06:55:55 +01:00
|
|
|
${MICROPY_SOURCE_LIB}
|
|
|
|
|
${MICROPY_SOURCE_PORT}
|
2021-09-21 15:00:26 +01:00
|
|
|
${MICROPY_SOURCE_BOARD}
|
2020-09-23 06:55:55 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
set(IDF_COMPONENTS
|
|
|
|
|
app_update
|
|
|
|
|
bootloader_support
|
2021-02-13 14:36:30 +00:00
|
|
|
bt
|
2020-09-23 06:55:55 +01:00
|
|
|
driver
|
2021-12-21 15:15:24 +00:00
|
|
|
esp_adc_cal
|
2020-09-23 06:55:55 +01:00
|
|
|
esp_common
|
|
|
|
|
esp_eth
|
|
|
|
|
esp_event
|
|
|
|
|
esp_ringbuf
|
|
|
|
|
esp_rom
|
|
|
|
|
esp_wifi
|
|
|
|
|
freertos
|
|
|
|
|
heap
|
|
|
|
|
log
|
|
|
|
|
lwip
|
|
|
|
|
mbedtls
|
|
|
|
|
mdns
|
|
|
|
|
newlib
|
|
|
|
|
nvs_flash
|
|
|
|
|
sdmmc
|
|
|
|
|
soc
|
|
|
|
|
spi_flash
|
|
|
|
|
tcpip_adapter
|
|
|
|
|
ulp
|
|
|
|
|
vfs
|
|
|
|
|
xtensa
|
|
|
|
|
)
|
|
|
|
|
|
2021-11-04 13:50:39 +00:00
|
|
|
if(IDF_VERSION_MINOR GREATER_EQUAL 1 OR IDF_VERSION_MAJOR GREATER_EQUAL 5)
|
2021-02-15 10:00:01 +00:00
|
|
|
list(APPEND IDF_COMPONENTS esp_netif)
|
|
|
|
|
endif()
|
|
|
|
|
|
2021-11-04 13:50:39 +00:00
|
|
|
if(IDF_VERSION_MINOR GREATER_EQUAL 2 OR IDF_VERSION_MAJOR GREATER_EQUAL 5)
|
2021-02-15 10:00:09 +00:00
|
|
|
list(APPEND IDF_COMPONENTS esp_system)
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp_timer)
|
|
|
|
|
endif()
|
|
|
|
|
|
2021-11-04 13:50:39 +00:00
|
|
|
if(IDF_VERSION_MINOR GREATER_EQUAL 3 OR IDF_VERSION_MAJOR GREATER_EQUAL 5)
|
2021-02-18 23:38:01 +00:00
|
|
|
list(APPEND IDF_COMPONENTS esp_hw_support)
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp_pm)
|
|
|
|
|
list(APPEND IDF_COMPONENTS hal)
|
|
|
|
|
endif()
|
|
|
|
|
|
2021-02-18 10:24:34 +00:00
|
|
|
if(IDF_TARGET STREQUAL "esp32")
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp32)
|
esp32: Add initial support for ESP32C3 SoCs.
Supported features for this SoC are:
- UART REPL, filesystem
- Pin, ADC, PWM, SoftI2C, SoftSPI, Timer, RTC
- OneWire, DHT, NeoPixel
- RMT
- WiFi, Bluetooth
Signed-off-by: Damien George <damien@micropython.org>
2021-07-18 03:11:21 +01:00
|
|
|
elseif(IDF_TARGET STREQUAL "esp32c3")
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp32c3)
|
|
|
|
|
list(APPEND IDF_COMPONENTS riscv)
|
2021-02-18 10:24:34 +00:00
|
|
|
elseif(IDF_TARGET STREQUAL "esp32s2")
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp32s2)
|
2021-02-19 01:08:11 +00:00
|
|
|
list(APPEND IDF_COMPONENTS tinyusb)
|
2021-05-06 01:58:12 +01:00
|
|
|
elseif(IDF_TARGET STREQUAL "esp32s3")
|
|
|
|
|
list(APPEND IDF_COMPONENTS esp32s3)
|
|
|
|
|
list(APPEND IDF_COMPONENTS tinyusb)
|
2021-02-18 10:24:34 +00:00
|
|
|
endif()
|
|
|
|
|
|
2020-09-23 06:55:55 +01:00
|
|
|
# Register the main IDF component.
|
|
|
|
|
idf_component_register(
|
|
|
|
|
SRCS
|
|
|
|
|
${MICROPY_SOURCE_PY}
|
|
|
|
|
${MICROPY_SOURCE_EXTMOD}
|
2021-07-09 05:19:15 +01:00
|
|
|
${MICROPY_SOURCE_SHARED}
|
2020-09-23 06:55:55 +01:00
|
|
|
${MICROPY_SOURCE_LIB}
|
|
|
|
|
${MICROPY_SOURCE_DRIVERS}
|
|
|
|
|
${MICROPY_SOURCE_PORT}
|
2021-09-21 15:00:26 +01:00
|
|
|
${MICROPY_SOURCE_BOARD}
|
2020-09-23 06:55:55 +01:00
|
|
|
INCLUDE_DIRS
|
2021-04-08 15:59:16 +01:00
|
|
|
${MICROPY_INC_CORE}
|
2021-03-27 21:10:39 +00:00
|
|
|
${MICROPY_INC_USERMOD}
|
2020-09-23 06:55:55 +01:00
|
|
|
${MICROPY_PORT_DIR}
|
|
|
|
|
${MICROPY_BOARD_DIR}
|
|
|
|
|
${CMAKE_BINARY_DIR}
|
|
|
|
|
REQUIRES
|
|
|
|
|
${IDF_COMPONENTS}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# Set the MicroPython target as the current (main) IDF component target.
|
|
|
|
|
set(MICROPY_TARGET ${COMPONENT_TARGET})
|
|
|
|
|
|
|
|
|
|
# Define mpy-cross flags, for use with frozen code.
|
|
|
|
|
set(MICROPY_CROSS_FLAGS -march=xtensawin)
|
|
|
|
|
|
|
|
|
|
# Set compile options for this port.
|
|
|
|
|
target_compile_definitions(${MICROPY_TARGET} PUBLIC
|
2021-04-08 14:56:28 +01:00
|
|
|
${MICROPY_DEF_CORE}
|
2020-09-23 06:55:55 +01:00
|
|
|
MICROPY_ESP_IDF_4=1
|
|
|
|
|
MICROPY_VFS_FAT=1
|
|
|
|
|
MICROPY_VFS_LFS2=1
|
|
|
|
|
FFCONF_H=\"${MICROPY_OOFATFS_DIR}/ffconf.h\"
|
|
|
|
|
LFS1_NO_MALLOC LFS1_NO_DEBUG LFS1_NO_WARN LFS1_NO_ERROR LFS1_NO_ASSERT
|
|
|
|
|
LFS2_NO_MALLOC LFS2_NO_DEBUG LFS2_NO_WARN LFS2_NO_ERROR LFS2_NO_ASSERT
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# Disable some warnings to keep the build output clean.
|
|
|
|
|
target_compile_options(${MICROPY_TARGET} PUBLIC
|
|
|
|
|
-Wno-clobbered
|
|
|
|
|
-Wno-deprecated-declarations
|
|
|
|
|
-Wno-missing-field-initializers
|
|
|
|
|
)
|
|
|
|
|
|
2021-03-17 01:35:59 +00:00
|
|
|
# Additional include directories needed for private NimBLE headers.
|
|
|
|
|
target_include_directories(${MICROPY_TARGET} PUBLIC
|
|
|
|
|
${IDF_PATH}/components/bt/host/nimble/nimble
|
|
|
|
|
)
|
|
|
|
|
|
2021-04-08 14:56:28 +01:00
|
|
|
# Add additional extmod and usermod components.
|
|
|
|
|
target_link_libraries(${MICROPY_TARGET} micropy_extmod_btree)
|
2021-03-27 21:10:39 +00:00
|
|
|
target_link_libraries(${MICROPY_TARGET} usermod)
|
|
|
|
|
|
2020-09-23 06:55:55 +01:00
|
|
|
# Collect all of the include directories and compile definitions for the IDF components.
|
|
|
|
|
foreach(comp ${IDF_COMPONENTS})
|
2021-04-08 14:42:22 +01:00
|
|
|
micropy_gather_target_properties(__idf_${comp})
|
2020-09-23 06:55:55 +01:00
|
|
|
endforeach()
|
|
|
|
|
|
2021-11-04 13:50:39 +00:00
|
|
|
if(IDF_VERSION_MINOR GREATER_EQUAL 2 OR IDF_VERSION_MAJOR GREATER_EQUAL 5)
|
2021-02-15 10:00:09 +00:00
|
|
|
# These paths cannot currently be found by the IDF_COMPONENTS search loop above,
|
|
|
|
|
# so add them explicitly.
|
|
|
|
|
list(APPEND MICROPY_CPP_INC_EXTRA ${IDF_PATH}/components/soc/soc/${IDF_TARGET}/include)
|
|
|
|
|
list(APPEND MICROPY_CPP_INC_EXTRA ${IDF_PATH}/components/soc/soc/include)
|
2021-02-19 01:08:11 +00:00
|
|
|
if(IDF_VERSION_MINOR GREATER_EQUAL 3)
|
|
|
|
|
list(APPEND MICROPY_CPP_INC_EXTRA ${IDF_PATH}/components/tinyusb/additions/include)
|
|
|
|
|
list(APPEND MICROPY_CPP_INC_EXTRA ${IDF_PATH}/components/tinyusb/tinyusb/src)
|
|
|
|
|
endif()
|
2021-02-15 10:00:09 +00:00
|
|
|
endif()
|
|
|
|
|
|
2020-09-23 06:55:55 +01:00
|
|
|
# Include the main MicroPython cmake rules.
|
|
|
|
|
include(${MICROPY_DIR}/py/mkrules.cmake)
|
