-
Notifications
You must be signed in to change notification settings - Fork 50
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
Meson isn't picked up from the PATH
#181
Comments
@lukester1975 can you check this out? |
Erm, dunno. Looks like it's all changed since those mods by me! I did mention That said, FWIW, I just Maybe it's best for @paveloom to try running with those mods and see how it goes; seems a bit silly me making a PR for it? |
If you don't want to PR it, I can. I'll take your experience as an endorsement for merging. When do you think you'll get your multiple build directory branch up for PR? I'd be really likely to merge it given you run it all the time. |
OK #186. As long as I don't get blamed... R.e. multiple build dirs - lord knows. So much has changed and cursorily it looks like more stuff assumes a single build dir. It would be a complete rewrite I imagine, so probably unlikely until either a) my old branch no longer works with current vscode or b) there's something so good in the latest meson plugin that I want both bits of functionality... Maybe I could rebase some of the trivial stuff one day and at least make a start that way. Cheers |
No problem. Thanks for looking. |
This reverts commit 5a103c4.
ProcessExecution() does not lookup into PATH. Fixes: mesonbuild#181
ProcessExecution() does not lookup into PATH. Fixes: mesonbuild#181
ProcessExecution() does not lookup into PATH. Fixes: #181
I'm using Nix,
direnv
, andnix-direnv
to setup a development environment. I'm using thedirenv
VSCode extension to load that environment in VSCode. This extension can't find Meson that is provided by the environment:I think that's because you're using
ProcessExecution
instead ofShellExecution
. I poked around and found that you made a switch toProcessExecution
in #47 to avoid shell escaping issues. Are those issues still relevant? And if so, won't the second constructor forShellExecution
bypass them?The text was updated successfully, but these errors were encountered: