cancel
Showing results for 
Search instead for 
Did you mean: 

Some problems of Create Empty Project

LionC
Associate

LionC_0-1766626390650.png

LionC_1-1766626413494.png

Question 1

The first image shows the toolchain configuration of my previous project, and the second image shows the configuration displayed in my newly created project. Why do I need to reinstall the toolchain when creating a new project on the same computer?

Question 2

I remember that when I first used the extension, these tools were all specified through scripts. However, after using it for a period of time, I found that CMake, programmer, and other tools could not find the specified paths, so I had to add them all to the environment variables.

 

2 REPLIES 2
Cartu38 OpenDev
Lead III

@LionC 
According to me first snapshot shows your first project setup i.e. tools locked / assigned to this project.

Second snapshot shows what tools are installed on your local system ... no the ones locked / assigned to your second project.
Comparing pears and apples here.
Assigning tools to a project is for sure not requiring to install them back. They are already on your system what's fine. Assigning / locking is just making explicit which tools your project has to rely on. You may want to use one toolchain for a project, another for the second etc etc.

Assigning / locking tools to a given project is populating for you under the hood the local $PATH variable ...

In short one setup step is missing to you for your second project. Let's have a try to force it:

Cartu38OpenDev_0-1766831361796.png

 

KnarfB
Super User

There is a system wide bundles store and a per-project list of used tools (bundles).

Both can be viewed via the bundles manager view.

Your second screen print seems to show the system wide bundles store.

From a vs code terminal there is the "cube" cli wrapper prog.

Running cube without options shows some help. Or like so (Win11):

C:\tmp\nucleo-l432_g0_g3>cube --verbose
cube wrapper version: 0.8.3
cube wrapper running on: x86_64-pc-windows
cube wrapper installed at "c:\\Users\\frank\\.vscode\\extensions\\stmicroelectronics.stm32cube-ide-core-1.1.0\\resources\\binaries\\win32\\x86_64\\cube.exe"
Reading Cube settings file: "C:\\Users\\frank\\AppData\\Roaming\\stm32cube\\CubeUserConfig.json"
Using bundles file at C:\tmp\nucleo-l432_g0_g3\.settings\bundles.store.json
Import: cmake@4.0.1+st.3 gnu-tools-for-stm32@13.3.1+st.9 ninja@1.13.1+st.1 st-arm-clangd@19.1.2+st.3
Using CubeUserConfig at "C:\\Users\\frank\\AppData\\Roaming\\stm32cube\\CubeUserConfig.json"
Using bundle installed repository at "C:\\ST\\cube"
Using metadata at "C:\\ST\\cube\\.metadata"
Using CMSIS_PACK_ROOT at "C:\\ST\\cube"
Using CUBE_CACHE_PATH "C:\\Users\\frank\\AppData\\Local\\stm32cube"
Using CUBE_LOG_PATH "C:\\Users\\frank\\AppData\\Roaming\\stm32cube\\logs"

 Note that I have changed some defaults.

hth

KnarfB