STM32L4+ CubeIDE: Legacy project names causing linker issues and include path confusion

[nik-markovic]

This issue existis with Azure_RTOS_6.1_STM32L4+-DISCO_STM32CubeIDE_Samples_2020_10_10.zip

I suspect that netxduo/threadx/stm32l4xx_libwere once named nxd/tx/stm32l475_lib respectively. This left some residue in .cproject files that cause issues if a new project gets created with STM32CubeIDE and references netxduo/threadx/stm32l4xx_lib.

Besides extra and incorrect non-existent include paths paths in the newly created project, the linker will fail unable to find nxd/tx/stm32l475_lib because linker flags would be included adding -ltx -lnxd and -lstm32l475_lib.

The following sed substitutions partially resolve these issues, but I would suggest to remove .project and .cproject files and recreating those projects from scratch:

sed -i '/stm32l475_lib/d' ./stm32l4xx_lib/.cproject
sed -i '/nxd/d' ./netxduo/.cproject
sed -i '/stm32l475_lib/d' ./threadx/.cproject
sed -i 's#\/tx#\/threadx#g' ./threadx/.cproject
sed -i 's#"tx"#"threadx"#g' ./threadx/.cproject

[ghost]

thanks for the suggestion, we will create new project in the l4 project sand evaluate if the changed names cause such issue.

[nik-markovic]

@wangwen-ms The changed names also seem to be affecting the NXP 1060 MCU Expresso project. In C/C++ build -> Refresh policy the item name is "tx" instead of "threadx", which causes a full rebuild instead of incremental.

[ghost]

thanks for bring this up, we will evaluate the consequence caused by changed names and see how to fix it.

[ghost]

we will fixed it in next release.

[bo-ms]

Closing it since we already fixed it internally and this bug fix will be in next release.