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

environmentSetupScript support for Presets #4227

Open
sinemakinci1 opened this issue Jan 7, 2025 · 0 comments
Open

environmentSetupScript support for Presets #4227

sinemakinci1 opened this issue Jan 7, 2025 · 0 comments
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature

Comments

@sinemakinci1
Copy link
Contributor

Brief Issue Summary

From comment on #4117

we are heavily relying on the environmentSetupScript key in cmake-kits.json. It doesn't seem to exist in CMake Presets.

According to this issue over at the CMake project it seems to be intentionally left out: https://gitlab.kitware.com/cmake/cmake/-/issues/21619

The environmentSetupScript makes it really easy to use Yocto SDKs, since this the default way to use it with cmake tool chain files (sourcing the environment setup script for e.g. $CC and then using the cmake tool chain file): https://docs.yoctoproject.org/dev/sdk-manual/using.html#running-the-sdk-environment-setup-script

Unfortunately Yocto is lacking documentation on using the SDK with cmake, here is what I found:
https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/

https://docs.yoctoproject.org/sdk-manual/working-projects.html

Sourcing the environment script from command line and then opening code from the terminal is also only partially solving the issue. We use the remote ssh/WSL extension a lot, and sourcing an environment before opening the remote/WSL session doesn't seem to be possible.

It would be great to somehow have the environmentSetupScript key available when used with CMake Presets, otherwise we still need to rely on CMake Kits (here is to hope that the cmake tools extension will not drop CMake Kits support).

Thanks in advance :)

CMake Tools Diagnostics

Debug Log

Additional Information

No response

@github-project-automation github-project-automation bot moved this to Blocked in CMake Tools Jan 7, 2025
@github-actions github-actions bot added the triage label Jan 7, 2025
@Amy-Li03 Amy-Li03 added enhancement an enhancement to the product that is either not present or an improvement to an existing feature and removed triage labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature
Projects
Status: Blocked
Development

No branches or pull requests

2 participants