Skip to main content
NCTUser
NCTUser
Associate II
January 23, 2019
Question

Using multi-project workspace in TrueSTUDIO

  • January 23, 2019
  • 2 replies
  • 846 views

Hello,

I am working on an bootloader in TrueSTUDIO. The application and the

bootloader are different projects in a single workspace. While I used

this multi-project workspace I faced some inconvenience. I share it

because maybe it can help improve TS or there is a solution/workaround

to my problems which I did not notice.

1. The TrueSTUDIO IDE does not show which project is the active

project. Sometimes when I jumped between files I did not know which

was the active project (which project will be compiled, debugged, ect.

when I click the icons).

2. I use several build configurations (not just Debug/Release) and

the IDE does not show which build configuraton is active.

3. Same is true in case of debug configuration. (For example the Debug

icon's tooltip now shows something irrelevant information. When I point

to the Debug icon, it would be better if it shows debug configuraton's name

which will launch.)

4. I can't exclude non-source files from build. I would like to use three

build configuraton (e.g. BOOTBUILD, STANDALONE, RAMBUILD) which

need three different linker command file. Each build configuration

contains only one linker command file and the other two are excluded, but

I can't exclude the linker files.

Is there any other way to assign linker command files to build

configurations? Or could anyone suggest a standard way to solve

this problem?

5. The Problems window shows the errors and warnings from both

project. Is it possible to filter them to the active project?

I am switching form an another eclipse based IDE (Code Composer Studio)

where these problems are mostly solved. I appreciate any answer!

Thank you!

This topic has been closed for replies.

2 replies

mattias norlander
mattias norlander
ST Employee
January 25, 2019

Hi NCT,

Thanks for your feedback. We share many of your opinions. Some of these can be fixed with user installation preference configuraiton. Other requires development and possibly even patching of Eclipse/CDT. Patching of Eclipse/CDT is something we don't want to do unless we can upstream our patches, since it creates maintenance problems.

Let's see what we can do about your quesitons:

  1. Hmm, what you can do is to use the "Link with editor" feature. It is a toggle button in the project explorer which expands the resource folder structure to show the location in the project of the specifici file currently opened in the editor view. Down-side of this is that after opening a couple of different files your project explorer has expanded a lot of folders and it becomes difficult to navigate resources. Instead toggle ON/OFF this busson quickly as soon as you feel uncertain as to in which project the file is located.
  2. It is up to you to choose which build configuration that is active in "manage build configurations". There is a new build/launch toolbar in the Eclipse/CDT project which solves this issue. TrueSTUDIO does not use it.
  3. Yes, would be good to show this in the tooltip. In general the decision logic for what is being launched is based one: 1. Which project is currently in context. 2. Which was the last launched configuration in the given context
  4. The Exclude from build is only for C-files. Instead for linker script go to Build settings --> Tool Settings --> C Linker --> General --> Linker script. The linker script field is configurable per build configuration.
  5. In the Problems view there is an "arrow pointing downwards" in the upper right corner. Eclipse style of icon indicating configuration options available. You will under the arrow find "Configure content" it has the checkbox "All items" enabled. Disable it and configure to your own liking.

I hope this sheds some light on some of the issues.

NCTUser
NCTUserAuthor
Associate II
January 29, 2019

Dear Mattias Norlander,

your suggestions work well, thank you for your

exhausting answer, you helped a lot!

Best regards,

NCTuser

Terms & ConditionsAccessibility statement