Roberthh wrote: ↑Wed Apr 21, 2021 3:17 pm
I can build that without any changes to scripts.
But are you adding any
#include "tusb.h" ? My builds are fine if I don't, it's only when I do I have problems.
Perhaps you could add
#include "tusb.h" to 'moduos.c' and see if it still builds or fails as it does for me.
I am pretty certain it's not a cleaning or caching issue as I am using the nuclear option every time -
Code: Select all
rm -r build
mkdir build
cd build
cmake ..
make
It seems that {MICROPY_SOURCE_QSTR} is created on a per port basis, from 'CMakeLists.txt' ...
Code: Select all
set(MICROPY_SOURCE_QSTR
${MICROPY_SOURCE_PY}
${MICROPY_SOURCE_EXTMOD}
${MICROPY_SOURCE_USERMOD}
${MICROPY_DIR}/lib/utils/mpirq.c
${MICROPY_DIR}/lib/utils/sys_stdio_mphal.c
${PROJECT_SOURCE_DIR}/machine_adc.c
${PROJECT_SOURCE_DIR}/machine_i2c.c
... snip ...
${PROJECT_SOURCE_DIR}/rp2_pio.c
)
I don't know how that would need to be updated to include TinyUSB.
Added : I'm now thinking it's not that, not MICROPY_SOURCE_QSTR per se; that's a list of where QSTR are used, not a list of directories for '-I'. I am not really that knowledgeable about the MicroPython build steps.