Skip to content

Conversation

loganek
Copy link
Collaborator

@loganek loganek commented Jul 25, 2025

Installing pip packages system-wide is no longer recommended, therefore we create virtual environment for setting up the build environment for LLVM.

@lum1n0us lum1n0us added the enhancement Check if this issue/PR enhances a feature; scripts will use this info. label Jul 28, 2025
@TianlongLiang
Copy link
Collaborator

Maybe we should add venv/ to .gitignore? What do you think

Installing pip packages system-wide is no longer recommended, therefore
we create virtual environment for setting up the build environment for LLVM.
@loganek loganek force-pushed the loganek/venv-llvm branch from 4011626 to 57e2354 Compare July 29, 2025 09:16
@loganek
Copy link
Collaborator Author

loganek commented Jul 29, 2025

Maybe we should add venv/ to .gitignore? What do you think

There's no venv directory created as part of this process; instead, we create a venv folder in the system's temp directory.

@TianlongLiang
Copy link
Collaborator

Got it, thanks

@lum1n0us lum1n0us merged commit 2685f2c into bytecodealliance:main Jul 30, 2025
452 checks passed
trap cleanup EXIT INT TERM

/usr/bin/env python3 -m venv --clear "$TEMP_DIR"
source "$TEMP_DIR/bin/activate"
Copy link
Collaborator

Choose a reason for hiding this comment

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


trap cleanup EXIT INT TERM

/usr/bin/env python3 -m venv --clear "$TEMP_DIR"
Copy link
Collaborator

Choose a reason for hiding this comment

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

why do you use /usr/bin/env?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Check if this issue/PR enhances a feature; scripts will use this info.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants