mirror of
https://github.com/zeldaret/oot.git
synced 2025-07-03 14:34:32 +00:00
Use virtualenv in Makefile for python dependencies (#1619)
* Use virtualenv in Makefile for python dependencies * Create separate targets for venv creation and installation * Fix install-python-deps prerequisite * Try simplifying Jenkinsfile * Simplify venv targets * Fix merge * Update README.md Co-authored-by: Dragorn421 <Dragorn421@users.noreply.github.com> --------- Co-authored-by: Dragorn421 <Dragorn421@users.noreply.github.com>
This commit is contained in:
parent
584e61a849
commit
5dd19e4862
4 changed files with 40 additions and 50 deletions
|
@ -2,6 +2,27 @@
|
|||
|
||||
This list gives brief information on the most common usage cases. For more information, first try using `-h` or `--help` as an argument, and failing that, ask in #oot-decomp-help or #tools-other in the Discord.
|
||||
|
||||
Many tools require activating a Python virtual environment that contains Python
|
||||
dependencies. This virtual environment is automatically installed into the
|
||||
`.venv` directory by `make setup`, but you need to **activate** it in your
|
||||
current terminal session in order to run Python tools. To start using the
|
||||
virtual environment in your current terminal run:
|
||||
|
||||
```bash
|
||||
source .venv/bin/activate
|
||||
```
|
||||
|
||||
Keep in mind that for each new terminal session, you will need to activate the
|
||||
Python virtual environment again. That is, run the above `source .venv/bin/activate` command.
|
||||
|
||||
To deactivate the virtual environment, run
|
||||
|
||||
```bash
|
||||
deactivate
|
||||
```
|
||||
|
||||
and your terminal session state will be restored to what it was before.
|
||||
|
||||
## m2ctx
|
||||
|
||||
This generates the context for mips2c to use to type objects in its output. It lives in the tools directory. Running
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue