|
3 | 3 | Here's how to run all the development stuff.
|
4 | 4 |
|
5 | 5 | ## Setup Development Environment
|
6 |
| -* `pyenv global 3.6.8-amd64` |
| 6 | +* `pyenv global 3.7.6-amd64` |
7 | 7 | * `pipenv install --dev`
|
8 | 8 |
|
9 | 9 | ## Building
|
10 | 10 |
|
11 |
| -Building is a little convoluted because we build a x64 and an x86 binary... |
| 11 | +Building is a little convoluted because we build a x64 and an x86 binary, because we don't have it in the Pipfile because it didn't play nicely with CI the last time I tried, and `pipenv` doesn't play nicely with bitness. |
12 | 12 |
|
13 |
| -* `pyenv global 3.6.8-amd64` |
14 |
| - * Originally wasn't able to get this to run on Python 3.7 when it was new, but 3.6 is guarenteed to build the `.exe` |
15 |
| -* `pyenv exec python -m venv venv64` |
16 |
| -* `venv64\scripts\activate.bat` or `venv64/scripts/activate` for Linux |
17 |
| -* `pip install -r requirements-dev.txt` (Installs `pyinstaller` and `pytest`) |
| 13 | +If this project accumulates and Pipfile dependencies that `pyinstaller` needs to know about, we either have to stop using `pipenv` or find a new way to manage this... |
| 14 | + |
| 15 | +EDIT: `pipenv` is apparently dead? No new releases? So... don't use it to build with for now... |
| 16 | + |
| 17 | +* `pyenv global 3.7.6-amd64` |
| 18 | +* `pipenv run pip freeze > tmp-requirements.txt` |
| 19 | +* `pip install -r tmp-requirements.txt` |
| 20 | +* `pip install pyinstaller` |
| 21 | + * pyinstaller is a slower dependency so might not work with the latest Python |
18 | 22 | * `python build_exe.py`
|
19 |
| -* `venv64\scripts\deactivate.bat` (or you'll use the wrong python when you make another `venv`) |
20 |
| -* Do the same with `pyenv and 3.6.8` and make a folder called `venv32` instead |
| 23 | +* Do the same with `pyenv global 3.7.6` (without `-amd64` suffix) to build the x86 .exe |
21 | 24 |
|
22 | 25 | ## Testing
|
23 | 26 | * `pipenv run pytest -v` in the root directory
|
|
0 commit comments