Basic link using F3?

[SWenn.1]

I am coming at the cubeIDE as a newbie AND as a hardware guy. With that said can someone tell me why when I am on a function / header file / or even a #define that SOMETIMES when I hit the F3 on the keyboard I do not jump to the corresponding definition? I realize it's a simple question (am coming from a Code Composer Studio background and it always seems to jump to the link).....I am guessing it could be I don't have something set up correctly in cubeIDE?? For instance I downloaded the BLE_p2pServer project.....Within this I go to the SystemClock_Config function where they call the following...__HAL_RCC_LSEDRIVE_CONFIG. If I place my cursor there and hit F3 nothing happens BUT I have a similar project that I am working in with an identical call and when I hit F3 with cursor on function I jump right to the file...I downloaded and installed this from github....The intereseting thing is if I right click on properties of this project I don't have options for C/C++ Build.

Thanks

Steve

[TDK]

STM32CubeIDE needs to be know where the definition is, which means it needs to be properly linked in your project files.

Sometimes you can rebuild the index to get definitions to work correctly.

> The intereseting thing is if I right click on properties of this project I don't have options for C/C++ Build.

Sounds like it's just not set up as a buildable project.

[SWenn.1]

Yes I do NOT have the hammer when I hover over the project....Seems odd that I wouldn't be able to pull off of github a buildable project for quick testing understanding how to use the various modules of the board??? Is there something I can do to make it buildable or is this something the originator does?

[TDK · Accepted solution]

It has something to do with the way you import it. Generally it's your responsibility to get the project working in your environment, rather than something pre-set up, since different people use different IDEs. It's one of the major headaches with setting up a project in a new IDE, especially when your'e new.
Consider creating a new project for your chip and copying files into that project to get it running.

[Pavel A.]

IIRC this is an issue in the upstream Eclipse CDT. The TI IDE is based on a similar but different Eclipse.

Please look at list of known issues in the CubeIDE release notes.