Is your feature request related to a problem? Please describe.
Currently in variant management, it is necessary to copy from variant folders the correct variant_data_file and compile_commands (maybe even more other parameters) to a generic build folder, so these infos can be fetched by ubcode.
This is bad, as these scripts have to be executed somehow. If a project is using cmake , the official cmake extension for vscode offers an API for other vscode extensions to fetch the current selected variant informations.
Describe the solution you'd like
If in vscode cmake extension a variant is been selected, the correct configuration in ubcode (ubproject.toml) shall be fetched.
Usage pattern: getCMakeToolsApi(Version.v5) → returns a CMakeToolsApi with getProject(workspaceFolderUri) → returns a Project object per CMakeLists.txt.
Even other parameters could be configured like this. e.g. current needs-variants like eu and us make in our examples?
A integration for testing can be supported by Philip in SPLed
Describe alternatives you've considered
None.
Additional context
None.
Is your feature request related to a problem? Please describe.
Currently in variant management, it is necessary to copy from variant folders the correct
variant_data_fileandcompile_commands(maybe even more other parameters) to a generic build folder, so these infos can be fetched by ubcode.This is bad, as these scripts have to be executed somehow. If a project is using
cmake, the official cmake extension for vscode offers an API for other vscode extensions to fetch the current selected variant informations.Describe the solution you'd like
If in vscode cmake extension a variant is been selected, the correct configuration in ubcode (ubproject.toml) shall be fetched.
Usage pattern:
getCMakeToolsApi(Version.v5)→ returns aCMakeToolsApiwithgetProject(workspaceFolderUri)→ returns aProjectobject per CMakeLists.txt.Even other parameters could be configured like this. e.g. current needs-variants like eu and us make in our examples?
A integration for testing can be supported by Philip in SPLed
Describe alternatives you've considered
None.
Additional context
None.