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.

Sign up for GitHub

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

Jump to bottom

Use virtualenv and requirements.txt in setup instructions #33

Closed
matatk opened this issue May 22, 2017 · 4 comments
Closed

Use virtualenv and requirements.txt in setup instructions #33

matatk opened this issue May 22, 2017 · 4 comments
Assignees
@matatk
Labels
enhancement

Comments

@matatk
Copy link
Owner

matatk commented May 22, 2017

This will make the process a lot simpler.
@matatk matatk self-assigned this May 22, 2017
@francipvb
Copy link

Hi,

What about Docker? It should be even simpler ... It needs more resources than a virtualenv, though.

Cheers,

@matatk
Copy link
Owner Author

matatk commented Jun 15, 2017

Thanks for the suggestion. Haven't used Docker before (so might be fun to learn). The problem to be solved is to simplify the management of third-party libraries that are needed for development. Virtualenv is focused solely on this, so it's a natural fit, but I will check out Docker too.

I'm working on some improvements in the mac-build branch and have moved to using "requirements.txt" to specify dependencies. That addresses the problem of making development environments consistent and easy to set up. But I think that soon it will also be necessary to isolate the environment for AudioQuake from other projects people may be working on.

@francipvb
Copy link

I was thinking more about docker and I found a problem. It can only produce linux builds in all platforms. To build windows or mac releases it needs native container support.

Using windows hosted CI it can build windows programs too but I don't know so much about it.

About Mac native containers I don't know anithing, but MacOSX native containers are supported too.

See this link.

With this for Windows and this for linux and Mac you have a complete hosted toolkit to test and build releases for major platforms using CI.

Ope this helps.

Cheers,

@matatk matatk mentioned this issue Mar 14, 2018
Merged
matatk added a commit that referenced this issue May 14, 2019
@matatk
feat: Python-based Build; New launcher GUI; Cleanup (#36)
c8885db 
* Rewrite build system (including manual generation) in pure Python.
* Use requirements.txt for dependencies.
* Use PyInstaller for building packages on macOS and Windows.
* Use wxPython 4 for the UI.
* Better TTS performance via rolling own on macOS (not implemented on Windows).
* Removes the DocBook XML manual files (using the Markdown ones only now).

Fixes #29

Partly addresses #30, #33, #34.

Tested on macOS Mojave. Windows installation instructions are progressing well, but more work will be needed to bring it up to par.
@matatk
Copy link
Owner Author

matatk commented Aug 2, 2020

This was closed by #44.

@matatk matatk closed this as completed Aug 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matatk matatk

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matatk @francipvb