Skip to main content
Knut_Knusper
Knut_Knusper
Associate II
May 6, 2019
Question

Where can I change the Runtime Library in STM32CubeIDEv1.00

  • May 6, 2019
  • 5 replies
  • 6297 views

Hello,

after importing my True Studio projects to the Cube IDE, I can not build my projects anymore.

I think this is because the Runtime Library newlib-nano is set as standard.

However, I have not found a way to change this to the newlib standard.

Does anyone know a possibility to change this in the STM32CubeIDE?

Thank you

This topic has been closed for replies.

5 replies

mfrank9
mfrank9
Associate III
May 6, 2019

Hello,

i have the same problem.

I import my projekt to STM32CubeIDE and now there is following error:

The float formatting support (-u _printf_float) is not enabled from linker flags.

Because this error i tried to use my old version (True Studio 9.2.0).

But now the project is damaged (see attachment)

I hope STM will fix it fast.

Markus GIRDLAND
Markus GIRDLAND
ST Employee
May 6, 2019

@Knut_Knusper​ The runtime library is changed inside Project Properties -> C/C++ Build -> Settings -> Tool Settings, the red circle in the picture below.

@mfrank9​  Same place as mentioned above but the blue circles.

The project might have been damaged because it doesn't look like it was properly imported. Please follow the instructions in the import manual, UM2578.

0690X000008BKeVQAW.png

mfrank9
mfrank9
Associate III
May 7, 2019

Now if have the following Error:

"The float formatting support (-u _printf_float) is not enabled from linker flags"

This are my settings:

mfrank9
mfrank9
Associate III
May 7, 2019

0690X000008BLoqQAG.png

Knut_Knusper
Knut_KnusperAuthor
Associate II
May 7, 2019

@mfrank9​ I think it could be an error from the Code Analysis (Window -> Preferneces -> C/C++ -> Code Analysis ).

Because in my project I have the same error in the Tab "Problems" but the build finished without errors.

There is a new option called STM32CubeIDE CodeCheckers: Float formatting support. 

In Atollic was no option with this name.

Maybe the Code Analyzes has an Bug and it does not recognize that the flag has been set.

Terms & ConditionsAccessibility statement