Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option for setting/changing an active MACHINE #383

Open
PatrickVog opened this issue Jan 16, 2025 · 1 comment
Open

Option for setting/changing an active MACHINE #383

PatrickVog opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@PatrickVog
Copy link

PatrickVog commented Jan 16, 2025

Is your feature request related to a problem? Please describe.
We usually have one build directory where we build one custom distro but for multiple devices. The local conf is not modified individually and contains a MACHINE ??= <default_machine> entry. When building we just set MACHINE= bitbake ... or export MACHINE. Such a process is in my opinion not covered in the plugin. I can have multiple build directories where I can set the MACHINE differently in the local.conf but I cannot tell which MACHINE to use over the plugin.

Describe the solution you'd like
Provide the option to set and change the MACHINE variable. This could be included in the "Change active build configuration" option that a MACHINE variable is provided there.

Describe alternatives you've considered
None

Additional context
It would also be useful if there is the option to have different command wrappers within a build configuration.

@PatrickVog PatrickVog added the enhancement New feature or request label Jan 16, 2025
@PatrickVog PatrickVog changed the title Option for setting the current MACHINE Option for setting/changing an active MACHINE Jan 16, 2025
@deribaucourt
Copy link
Member

Hello, thanks for reaching out!

It seems the setting bitbake.buildConfigurations is what you are looking for. You can configure multiple commandWrapper and change the MACHINE environment variable (shellEnv). You will be able to switch between build configurations through the bottom-right selector that will appear.

There's an example in the README and also as you type in your .vscode/settings.json.

Let me know if you have further issues/limitations while using this feature.

@deribaucourt deribaucourt self-assigned this Jan 16, 2025
@deribaucourt deribaucourt added the question Further information is requested label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants