2017-11-01 12:39 PM
CubeMX 4.23.
Board nucleo-f429zi and STM32CubeF4 is of v1.17.0
Compiling with makefile arm-gcc-none-eabi version: 5.3 2016q1
All is done on linux
I just noticed another thing,
Completely freshly generated makefile has duplicate entries for some of the source files:
I see gpio.c, main.c, usb_otg.c have been duplicated, maybe more, it's just some I've noticed by quickly reading the list my self.
C_SOURCES = \
Middlewares/Third_Party/LwIP/src/netif/ppp/ccp.c \Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal.c \Middlewares/Third_Party/LwIP/src/core/ipv6/nd6.c \Src/gpio.c \Src/gpio.c \Here is a link to full makefile generated by cubemx
2017-11-02 03:11 AM
Hello
Strogonovs.Raivi
This issue is raised internally to CubeMx team for investigation and we will be back to you as soon as possible.
Thanks for your contribution.
Best Regards
Imen
2017-11-08 12:05 PM
Hi,
I'm not sure why it happened, but once I deleted all the entries under C_SOURCES = \....
In Makefile it has been working since.Maybe by accident I somehow locked the file while generating the code from CubeMX
2018-02-12 07:15 AM
hello
Strogonovs.Raivi
,This is not an issue on your side but an issue when CubeMX generates the code with makefile.
As you say, the workaround is to suppress every duplicated source files and it compiles and links successfully after.
Sorry for the inconvenience it may cause.
Our development teams are working on that point, I will keep you inform as soon as the correction is available in a CubeMX release.
BR. Jeanne
2018-06-04 12:56 AM
Hi
Strogonovs.Raivi
,The correction is available in CubeMX 4.0 version (available this week).
Regards,
Houda
2019-02-04 10:50 AM
Greetings:
I am having the same issue with v5.0.1
Each time I try to regenerate the build files for uVision, I get 3 duplicate files - two are links back to the exact same file :
and one where the files were in different locations, but the same file
Is this a different bug, or did the fix not get moved into 5.0?
If it is different, how do I prevent it from happening again (I'm moving to a different project soon and need to document or fix this issue) ?
Thanks.