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

[WIP] Overhaul macOS build process #403

Closed
wants to merge 6 commits into from
Closed

[WIP] Overhaul macOS build process #403

wants to merge 6 commits into from

Conversation

droark
Copy link

@droark droark commented Dec 21, 2017

  • Completely change the macOS build process. No external libraries outside of the cppForSwig subdirectory are now built. Users will have to rely on brew and pip in order to install certain required third-party libraries.
  • Fix up the notes as required.

The idea is to make macOS compilation more like Linux compilation and remove the need to maintain/modify third-party libraries. This will also make it far easier to transition Armory from Python 2 to Python 3, Qt 4 to Qt 5, etc., along with making deterministic builds far easier to obtain down the road.

This is a work-in-progress. Objective-C code isn't compiled (and related code is commented out of the Python code), the notes need to be finalized and checked against a fresh macOS VM, Armory needs to be run for awhile to see if it's stable, etc.

- Completely change the macOS build process. No external libraries outside of the cppForSwig subdirectory are now built. Users will have to rely on brew and pip in order to install certain required third-party libraries.
- Fix up the notes as required.

The idea is to make macOS compilation more like Linux compilation and remove the need to maintain/modify third-party libraries. This will also make it far easier to transition Armory from Python 2 to Python 3, Qt 4 to Qt 5, etc., along with making deterministic builds far easier to obtain down the road.

This is a work-in-progress. Objective-C code isn't compiled (and related code is commented out of the Python code), the notes need to be finalized and checked against a fresh macOS VM, Armory needs to be run for awhile to see if it's stable, etc.
@droark
Copy link
Author

droark commented Dec 21, 2017

As mentioned in the original commit message, this is a work-in-progress. I also need to mod ArmoryQt.py to be in line with what was in the repo. (I yanked the file from a different repo by accident.) This PR can be ignored for now. I'll report back when the PR's ready for review.

Kick off Armory using standard Python, not an Armory-built Python.
- Make macOS build script Python3-compatible.
- Adjust the Mac notes to better reflect what users should expect. (Subject to change.)
- To make future merges easier, sync Mac READMEs with the mainline.
@goatpig goatpig deleted the branch goatpig:py3 December 8, 2021 11:22
@goatpig goatpig closed this Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants