Not necessarily. The Feature (devcontainer-feature.json, install.sh, and
NOTES.md) could be part of the vscodeext repo and published to GitHub
Container Registry using the devcontainers cli or GitHub Action.
Or it could be in its own separate repository if you prefer, in which case
you would likely
I think for single repo projects devcontainers work really nice to get all
dependencies and tools in place. There are two usecases for the devcontainers:
1. User projects (as OP's approach)
This would build and install the full qt6 stack. This could be useful if the
user wants to test and build
On 1/27/25 18:07, Alex Shaw wrote:
Is anyone interested in seeing this officially added to Qt?
That seems interesting. Do I understand correctly that the devcontainer
spec [1] would go into a repo different from vsccodeext?
And vscodeext would merely announce its existence?
Cheers,
Joerg
