Page 1 of 1

Release build not defining compiler

Posted: Fri Mar 30, 2018 10:19 pm
by daverj
I am using the latest TrueStudio with a project for STM32L452 created using the latest STM32CubeMX.

The created project contains both a debug and a release build. When I set the debug as active and look in one of the files that contains conditional compiles based on the compiler (core_cm4.h) I see that the lines for __GNUC__ are not grayed out. So obviously that compiler is defined somewhere.

However when I set the release build as active and look at that same file, all the conditional statements based on compiler are grayed out, and the final "else" for "unknown compiler" is the one not grayed out. So clearly __GNUC__ is not being defined anywhere.

Also, when I go to the build settings and select the release build I see a warning at the top that says "Orphaned configuration. No base extension cfg exists for com.atollic.truestudio.exe.release.1518366166". I don't get that when I select the debug build.

So, what does that warning actually mean, and why is the compiler not defined in the release build? (and where is it normally defined?)

Re: Release build not defining compiler

Posted: Sun Apr 01, 2018 8:24 pm
by daverj
Any idea what that "Orphaned Configuration" error means???

I tried using a copy of the same project to create an output for System Workbench (SW4STM32), and that one does not have this error in the release configuration, and it does define "GNUC" in both the debug and release builds. So it's not the project that is at fault. It's something to do with how STM32CubeMX is generating files for TrueStudio.

Re: Release build not defining compiler

Posted: Thu Jan 31, 2019 7:00 am
by RR4711
I have the same problem with 9.2.0 and Cube MX Generated Project (Cube MX V5.01). Any Updates on that?

Re: Release build not defining compiler

Posted: Thu Jan 31, 2019 8:19 am
by kurta999
Write here if it isn't fixed yet, I already reported it on ST.

https://community.st.com/s/question/0D5 ... -build-bug