2020-09-23 01:55:55 -04:00
|
|
|
# Set location of base MicroPython directory.
|
2021-06-24 02:03:25 -04:00
|
|
|
if(NOT MICROPY_DIR)
|
2023-05-08 19:52:54 -04:00
|
|
|
get_filename_component(MICROPY_DIR ${CMAKE_CURRENT_LIST_DIR}/../.. ABSOLUTE)
|
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 16:02:10 -04:00
|
|
|
endif()
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
# Set location of the ESP32 port directory.
|
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 16:02:10 -04:00
|
|
|
if(NOT MICROPY_PORT_DIR)
|
|
|
|
|
get_filename_component(MICROPY_PORT_DIR ${MICROPY_DIR}/ports/esp32 ABSOLUTE)
|
2021-06-24 02:03:25 -04:00
|
|
|
endif()
|
2020-09-23 01:55:55 -04:00
|
|
|
|
|
|
|
|
# Include core source components.
|
|
|
|
|
include(${MICROPY_DIR}/py/py.cmake)
|
|
|
|
|
|
2023-07-31 03:24:38 -04:00
|
|
|
# CMAKE_BUILD_EARLY_EXPANSION is set during the component-discovery phase of
|
|
|
|
|
# `idf.py build`, so none of the extmod/usermod (and in reality, most of the
|
|
|
|
|
# micropython) rules need to happen. Specifically, you cannot invoke add_library.
|
2021-03-27 17:10:39 -04:00
|
|
|
if(NOT CMAKE_BUILD_EARLY_EXPANSION)
|
2022-06-07 22:21:51 -04: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 17:10:39 -04:00
|
|
|
include(${MICROPY_DIR}/py/usermod.cmake)
|
2021-04-08 09:45:28 -04:00
|
|
|
include(${MICROPY_DIR}/extmod/extmod.cmake)
|
2021-03-27 17:10:39 -04:00
|
|
|
endif()
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND 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 16:02:10 -04:00
|
|
|
${MICROPY_PORT_DIR}/qstrdefsport.h
|
2021-02-20 19:33:15 -05:00
|
|
|
)
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND MICROPY_SOURCE_SHARED
|
2021-07-09 00:19:15 -04:00
|
|
|
${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
|
|
|
|
|
)
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND MICROPY_SOURCE_LIB
|
2020-09-23 01:55:55 -04:00
|
|
|
${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-05-08 19:52:54 -04:00
|
|
|
#${MICROPY_DIR}/lib/mbedtls_errors/esp32_mbedtls_errors.c
|
2020-09-23 01:55:55 -04:00
|
|
|
${MICROPY_DIR}/lib/oofatfs/ff.c
|
|
|
|
|
${MICROPY_DIR}/lib/oofatfs/ffunicode.c
|
|
|
|
|
)
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND MICROPY_SOURCE_DRIVERS
|
2020-09-23 01:55:55 -04:00
|
|
|
${MICROPY_DIR}/drivers/bus/softspi.c
|
|
|
|
|
${MICROPY_DIR}/drivers/dht/dht.c
|
|
|
|
|
)
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND 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 16:02:10 -04:00
|
|
|
main.c
|
2023-06-21 01:09:26 -04:00
|
|
|
ppp_set_auth.c
|
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 16:02:10 -04:00
|
|
|
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 01:55:55 -04: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 16:02:10 -04:00
|
|
|
list(TRANSFORM MICROPY_SOURCE_PORT PREPEND ${MICROPY_PORT_DIR}/)
|
2023-07-14 10:03:59 -04:00
|
|
|
list(APPEND MICROPY_SOURCE_PORT ${CMAKE_BINARY_DIR}/pins.c)
|
2020-09-23 01:55:55 -04:00
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND MICROPY_SOURCE_QSTR
|
2020-09-23 01:55:55 -04:00
|
|
|
${MICROPY_SOURCE_PY}
|
|
|
|
|
${MICROPY_SOURCE_EXTMOD}
|
2021-03-27 17:10:39 -04:00
|
|
|
${MICROPY_SOURCE_USERMOD}
|
2021-07-09 00:19:15 -04:00
|
|
|
${MICROPY_SOURCE_SHARED}
|
2020-09-23 01:55:55 -04:00
|
|
|
${MICROPY_SOURCE_LIB}
|
|
|
|
|
${MICROPY_SOURCE_PORT}
|
2021-09-21 10:00:26 -04:00
|
|
|
${MICROPY_SOURCE_BOARD}
|
2020-09-23 01:55:55 -04:00
|
|
|
)
|
|
|
|
|
|
2023-05-08 19:52:54 -04:00
|
|
|
list(APPEND IDF_COMPONENTS
|
2020-09-23 01:55:55 -04:00
|
|
|
app_update
|
|
|
|
|
bootloader_support
|
2021-02-13 09:36:30 -05:00
|
|
|
bt
|
2020-09-23 01:55:55 -04:00
|
|
|
driver
|
2023-05-08 19:52:54 -04:00
|
|
|
esp_adc
|
|
|
|
|
esp_app_format
|
2020-09-23 01:55:55 -04:00
|
|
|
esp_common
|
|
|
|
|
esp_eth
|
|
|
|
|
esp_event
|
2023-05-08 19:52:54 -04:00
|
|
|
esp_hw_support
|
|
|
|
|
esp_netif
|
|
|
|
|
esp_partition
|
|
|
|
|
esp_pm
|
|
|
|
|
esp_psram
|
2020-09-23 01:55:55 -04:00
|
|
|
esp_ringbuf
|
|
|
|
|
esp_rom
|
2023-05-08 19:52:54 -04:00
|
|
|
esp_system
|
|
|
|
|
esp_timer
|
2020-09-23 01:55:55 -04:00
|
|
|
esp_wifi
|
|
|
|
|
freertos
|
2023-05-08 19:52:54 -04:00
|
|
|
hal
|
2020-09-23 01:55:55 -04:00
|
|
|
heap
|
|
|
|
|
log
|
|
|
|
|
lwip
|
|
|
|
|
mbedtls
|
|
|
|
|
newlib
|
|
|
|
|
nvs_flash
|
|
|
|
|
sdmmc
|
|
|
|
|
soc
|
|
|
|
|
spi_flash
|
|
|
|
|
ulp
|
|
|
|
|
vfs
|
|
|
|
|
xtensa
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# Register the main IDF component.
|
|
|
|
|
idf_component_register(
|
|
|
|
|
SRCS
|
|
|
|
|
${MICROPY_SOURCE_PY}
|
|
|
|
|
${MICROPY_SOURCE_EXTMOD}
|
2021-07-09 00:19:15 -04:00
|
|
|
${MICROPY_SOURCE_SHARED}
|
2020-09-23 01:55:55 -04:00
|
|
|
${MICROPY_SOURCE_LIB}
|
|
|
|
|
${MICROPY_SOURCE_DRIVERS}
|
|
|
|
|
${MICROPY_SOURCE_PORT}
|
2021-09-21 10:00:26 -04:00
|
|
|
${MICROPY_SOURCE_BOARD}
|
2020-09-23 01:55:55 -04:00
|
|
|
INCLUDE_DIRS
|
2021-04-08 10:59:16 -04:00
|
|
|
${MICROPY_INC_CORE}
|
2021-03-27 17:10:39 -04:00
|
|
|
${MICROPY_INC_USERMOD}
|
2020-09-23 01:55:55 -04: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 09:56:28 -04:00
|
|
|
${MICROPY_DEF_CORE}
|
2023-07-25 01:03:30 -04:00
|
|
|
${MICROPY_DEF_BOARD}
|
2020-09-23 01:55:55 -04: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-16 21:35:59 -04: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 09:56:28 -04:00
|
|
|
# Add additional extmod and usermod components.
|
|
|
|
|
target_link_libraries(${MICROPY_TARGET} micropy_extmod_btree)
|
2021-03-27 17:10:39 -04:00
|
|
|
target_link_libraries(${MICROPY_TARGET} usermod)
|
|
|
|
|
|
2023-07-05 12:03:11 -04:00
|
|
|
# Collect all of the include directories and compile definitions for the IDF components,
|
|
|
|
|
# including those added by the IDF Component Manager via idf_components.yaml.
|
|
|
|
|
foreach(comp ${__COMPONENT_NAMES_RESOLVED})
|
2021-04-08 09:42:22 -04:00
|
|
|
micropy_gather_target_properties(__idf_${comp})
|
2023-05-08 19:52:54 -04:00
|
|
|
micropy_gather_target_properties(${comp})
|
2020-09-23 01:55:55 -04:00
|
|
|
endforeach()
|
|
|
|
|
|
|
|
|
|
# Include the main MicroPython cmake rules.
|
|
|
|
|
include(${MICROPY_DIR}/py/mkrules.cmake)
|
2023-07-14 10:03:59 -04:00
|
|
|
|
|
|
|
|
# Generate source files for named pins (requires mkrules.cmake for MICROPY_GENHDR_DIR).
|
|
|
|
|
|
|
|
|
|
set(GEN_PINS_PREFIX "${MICROPY_PORT_DIR}/boards/pins_prefix.c")
|
|
|
|
|
set(GEN_PINS_MKPINS "${MICROPY_PORT_DIR}/boards/make-pins.py")
|
|
|
|
|
set(GEN_PINS_SRC "${CMAKE_BINARY_DIR}/pins.c")
|
|
|
|
|
set(GEN_PINS_HDR "${MICROPY_GENHDR_DIR}/pins.h")
|
|
|
|
|
|
|
|
|
|
if(EXISTS "${MICROPY_BOARD_DIR}/pins.csv")
|
|
|
|
|
set(GEN_PINS_BOARD_CSV "${MICROPY_BOARD_DIR}/pins.csv")
|
|
|
|
|
set(GEN_PINS_BOARD_CSV_ARG --board-csv "${GEN_PINS_BOARD_CSV}")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
target_sources(${MICROPY_TARGET} PRIVATE ${GEN_PINS_HDR})
|
|
|
|
|
|
|
|
|
|
add_custom_command(
|
|
|
|
|
OUTPUT ${GEN_PINS_SRC} ${GEN_PINS_HDR}
|
|
|
|
|
COMMAND ${Python3_EXECUTABLE} ${GEN_PINS_MKPINS} ${GEN_PINS_BOARD_CSV_ARG}
|
|
|
|
|
--prefix ${GEN_PINS_PREFIX} --output-source ${GEN_PINS_SRC} --output-header ${GEN_PINS_HDR}
|
|
|
|
|
DEPENDS
|
|
|
|
|
${MICROPY_MPVERSION}
|
|
|
|
|
${GEN_PINS_MKPINS}
|
|
|
|
|
${GEN_PINS_BOARD_CSV}
|
|
|
|
|
${GEN_PINS_PREFIX}
|
|
|
|
|
VERBATIM
|
|
|
|
|
COMMAND_EXPAND_LISTS
|
|
|
|
|
)
|
