Build Analyzer does not work after STM32CubeIDE update.

[Kim KyungTack]

Hi.

I was using STM32CubeIDE 1.14.0 until yesterday.

Build Analyzer worked fine in 1.14.0, but after updating to 1.15.0 using the update feature provided by CubeIDE, nothing is displayed in Build Analyzer. 

The build was successful and the <project>.map file was created, but the Build Analyzer information was not displayed, and I uninstalled and reinstalled CubeIDE, but it was the same.

[PR.10]

did you rename your project? It was broken for me after clone and rename. I checked all the properties in gui and fixed some to new name. There are still some areas with old name in .cproject file but it work now, so they are probably irrelevant. You can also try to delete all non-source files like build directory and ide .settings. I should create a new defaults and may fix some problems.

[BillFleming]

I had to change the "Build Views Refresh Mode" several times along with also attempting to change the "Complexity Ceiling". Hitting "Apply and Close" would then cause STM32Cube to either close or crash immediately in some cases.

But the last time I switched back to "Auto" and changed the "Complexity Ceiling" to 50 then hitting "Apply and Close" after e2 studio exited when I re-opened it back up all of the projects were working in the Build Analyzer again. I didn't need to hand-edit any of the project files, even though they look different compared to projects created from the newest STM32CubeIDE.

So this looks to be some issue with initializing a new workspace in the new STM32CubeIDE. I used the default new 1.15.1 workspace when installing this one, on a new PC that didn't even have the previous version workspaces.

[cjpeplin]

I just want to concur. I'm using 1.16 and whether or not the build analyzer refreshes seems completely random. I started a new project using 1.16 and the only way to get the build analyzer to update is to try a bunch of combinations of rebuilding, restarting, reconfiguring, etc. It's been this way for a while. I really like the build analyzer when it works. Next I'll go look for a way to open this as a bug.

[ThierryV]

I was reading section 2.4 and hadn't yet reached section 2.5. Section 2.4 only explains that you have to select the elf file in the Project Explorer view, or the project node itself. But this didn't work.
I found the solution here, and now I can continue with section 2.5 :smiling_face_with_smiling_eyes:

I think section 2.4 can be updated too (and also #4.1.2).

[Carl_G]

The build analyzer does have a problem. If the project is not selected and you hit refresh, it won't do anything. Or maybe it tries to refresh from the project that is selected (even if that project is closed) and fails. If only one project is open then the Build Analyzer should always refresh from that project no matter if its selected or not. Or even better the build analyzer should give some warning if its not going to do anything. such as stating that no project is selected. In fact, I think the FreeRTOS warning that pops up when I regenerate is taking the focus selection off of the project which is then making it so that refresh does not work even if the project appears to be selected, without first clicking on the project again.

Whichever engineer decided to include the file with the date and time that the Build Analyzer is using, in the displayed information, made a great decision.

Anyway, if you are hitting refresh and noticing that the information is not refreshing, then select the project or some item in the project and hit refresh again. It should take after that.

[PHolt.1]

I find three separate issues:

1) After a build one needs to click on the .map file (which is in the Debug directory) and then the Build Analyser appears

2) The .map file does not usually appear until a second build (i.e. another control-b).

3) The values shown in the Build Analyser magically change to the correct values (I think the initial ones are old ones) after some 10-20 seconds!

Cube IDE is based on a generic 3rd party (open source?) IDE called Eclipse and - along with the "semi-random" file opening bug - ST are clearly reluctant to dive in too deep to fix stuff on it. It is a massively bloated piece of code which basically nobody understands. Written in Java ;)

BTW the email notification one gets from this ST forum contains a dud URL and I get this

but a Reload just displays the same thing.

[Carl_G]

I've written applications using Eclipse platform. Its open source. Its backed by major players. I don't think its bloated. Its very componentized so an application builder simply doesn't include the parts they don't want.

The focus issue should be easily fixed by the developers.