Error log/ console view
Dear Sir ,
Thank you once again.
Yes, you picked up very key point here.
I did see this thing before, but problem is compiler shows different errors in different time you compile.
As far as I remember I have #include header file in main c.
To be honest, my huge project has 2 main files, 1 from cubemx, other is little modified with user code in cubemx.
Its true many times I have added constants in c like #define contant.
For this time being lets talk about the project which has less compile time.
In this case I think, include paths and CMSIS header files are well linked in system.
Take a look now,
Info: Internal Builder is used for build
arm-none-eabi-gcc -mthumb -mfloat-abi=soft -E “-IC:\STM32_toolchain\bin” “-IC:\STM32_toolchain\arm-none-eabi\bin” “-IC:\STM32_toolchain\common\Drivers\STM32F0xx_HAL_Driver\Inc” “-IC:\STM32_toolchain\common\Drivers\STM32F0xx_HAL_Driver\Src” “-IC:\STM32_toolchain\lib\gcc” -O0 -g3 -Wall -fmessage-length=0 -ffunction-sections -c -o “startup\Src\stm32f0xx_hal_pcd.o” “..\startup\Src\stm32f0xx_hal_pcd.c”
arm-none-eabi-gcc -mthumb -mfloat-abi=soft -E “-IC:\STM32_toolchain\bin” “-IC:\STM32_toolchain\arm-none-eabi\bin” “-IC:\STM32_toolchain\common\Drivers\STM32F0xx_HAL_Driver\Inc” “-IC:\STM32_toolchain\common\Drivers\STM32F0xx_HAL_Driver\Src” “-IC:\STM32_toolchain\lib\gcc” -O0 -g3 -Wall -fmessage-length=0 -ffunction-sections -c -o “inc\Src\stm32f0xx_ll_utils.o” “..\inc\Src\stm32f0xx_ll_utils.c”
..\inc\Src\stm32f0xx_ll_utils.c:38:30: fatal error: stm32f0xx_ll_rcc.h: No such file or directory
compilation terminated.
13:40:20 Build Finished (took 803ms)
We can think number of question ...
1.If the HAL header file is already exsists in project tree folder, does it make trouble?
2. How about staying Debug folder in project tree, does it make sence ?
3. Is there anything with pre=prossesor setting?...I did tick on project properties>C/C++ build>setting>preprocessor>Preprocess only(-E)
Take a look on some setting in this attacment.
Regards
Hasan
;){kind=link}