Open jjcf89 opened 4 years ago
:+1: I plan to upgrade the plugin to an other parsing base, if the folder is still needed I will rename it. Thank you for the hint.
I'm using the extension bitbake v1.1.2. This folder is still being created as vscode-bitbake-build
. Any updates on when this will be renamed to be build-vscode-bitbake
or perhaps move it under the build
directory as in build/vscode-bitbake-build
? Either would satisfy my colleagues.
Not everyone is delighted when I have to make changes to all of our repos .gitignore
for the sake of vscode users. Incredibly, not everyone is a vscode user 😉.
Sorry to say that I haven't time anymore to work on this plugin.
Best Regards Eugen
LiveFreeAndRoam @.***> schrieb am Mo., 28. März 2022, 05:08:
I'm using the extension bitbake v1.1.2. This folder is still being created as vscode-bitbake-build. Any updates on when this will be renamed to be build-vscode-bitbake?
Not everyone is delighted when I have to make changes to all of our repos .gitignore for the sake of vscode users. Incredibly, not everyone is a vscode user 😉.
— Reply to this email directly, view it on GitHub https://github.com/EugenWiens/vscode-bitbake/issues/33#issuecomment-1080131672, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4D7GUGMSA66CDWRJINRSLVCEPDNANCNFSM4MEBAFWA . You are receiving this because you commented.Message ID: @.***>
In case others find this... there is a solution by adding this to your settings.json
:
"bitbake.workingFolder": "build-vscode-bitbake",
Thank you for sharing this information. :+1:
The Poky git repo by default has /build*/ in its .gitignore file. It would be great if the default build directory for this project could be "build-vscode-bitbake" instead so it doesn't show up as untracked changes in git.