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

Use Python venv if detected when building VS project #84593

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

brno32
Copy link
Contributor

@brno32 brno32 commented Nov 7, 2023

resolves #84555

this works for me and solves my problem. I want to use a venv to isolate my scons installation from the rest of my system but using it is incompatible with the generated godot.sln since the call to scons assumes it's installed globally.

If a virtual environment is activated, the VIRTUAL_ENV env var should contain a path to its root, and from there we can build the proper command.

No hard feelings if we don't wanna merge this, but it's useful to me ;)

@brno32 brno32 requested a review from a team as a code owner November 7, 2023 21:36
@Calinou Calinou added bug topic:buildsystem cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release labels Nov 7, 2023
@Calinou Calinou added this to the 4.3 milestone Nov 7, 2023
@akien-mga akien-mga changed the title use venv if detected when building godot.sln Use Python venv if detected when building VS project Nov 11, 2023
methods.py Outdated Show resolved Hide resolved
Copy link
Contributor

@yedpodtrzitko yedpodtrzitko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but I'm not part of the devteam :)

@akien-mga akien-mga merged commit 81a30b6 into godotengine:master Dec 4, 2023
15 checks passed
@akien-mga
Copy link
Member

Thanks!

@brno32 brno32 deleted the vs-venv-fix branch December 4, 2023 22:55
@YuriSizov YuriSizov removed the cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release label Dec 5, 2023
@YuriSizov
Copy link
Contributor

Cherry-picked for 4.2.1.

@YuriSizov YuriSizov removed the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Jan 23, 2024
@YuriSizov
Copy link
Contributor

Cherry-picked for 4.1.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Virtual environment not detected by build scripts
5 participants