-
Notifications
You must be signed in to change notification settings - Fork 2
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
VSCode build is broken #189
Labels
Comments
zedaav
added
bug
Something isn't working
plugin:vscode
VsCode plugin related issue
labels
Feb 6, 2024
Terminal settings should be updated to get something like this (for each supported shell): "terminal.integrated.profiles.linux": {
"bash": {
"args": [
"--init-file",
".buildenv/shell.sh"
]
},
}, Tasks should be updated to directly call nmk instead of buildenv. Except for setup, which should run |
See also how to integrate vscode shell script |
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 11, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 18, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 18, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 19, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 19, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 19, 2024
zedaav
added a commit
to dynod/nmk-vscode
that referenced
this issue
Feb 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see https://code.visualstudio.com/docs/python/environments#_environment-variable-definitions-file
and https://github.com/microsoft/vscode-python/wiki/Activate-Environments-in-Terminal-Using-Environment-Variables
First problem: python venv is now loaded before build commands are issued. And buildenv refuses to run since already executed from a venv.
Second problem: activation scripts are not executed anymore, so it breaks the buildenv paradigm. Typically completion setup is not executed, etc...
The text was updated successfully, but these errors were encountered: