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

Mac build fix #11

Open
wants to merge 111 commits into
base: master
Choose a base branch
from
Open

Mac build fix #11

wants to merge 111 commits into from

Conversation

bgebhardt
Copy link

@bgebhardt bgebhardt commented May 29, 2023

@ABaumher here's my pull request

  • Fixes what I noted in issue Getting mac builds working #10. Please check this pip-tools change on Windows.
  • Adds Mac dev instructions
  • Adds Mac dot files to the .gitignore

I inadvertently committed and reverted some other stuff too. Those are the first 2 commits.

LauraRozier and others added 30 commits March 16, 2023 03:27
…es i had to a minimal version of this to get the integration working in GOG Galaxy. This version is newer than what i am testing, so it may have errors
… this patch for the current version i have working in the plugin. Still need to add hello message
… webpage to go to step 2. various little bugfixes, including no more infinite loops on getters
…sic code to display all the other pages. This is largely unchanged from the original, but the login page has evidently changed. the code-behind isn't implemented.

Various bugfixes as well
…Windows 11, macOS12,13). Other tweaks, idk anymore
… 2FA, but hopefully i haven't broken anything else
…ning about types overshadowing the standard types. Removed authentication.py. Moved all enums i could find in Steam_network to a dedicated enums.py. Moved All top level functions that may have been called in multiple spots to a utils.py Internally, downgraded my environment to 3.7 as per GOG Galaxy instructions. The resulting file was added to .gitignore
…perly. Removed an exceptions import that did nothing and randomly caused an error. Apparently i don't know how to stash things.
… of that is implemented. oops. layed out the empty methods for it.
…e, the py versions of proto files were not updated
… plugin works from task.py. Not finished; switching gears to localization so i don't go insane.
…n't print like i want them to, which annoys me immensely. Need to retrieve old py files in the repo before calling build install, which broke them
…few conflicts, i'll have to figure out the best way to handle them
…uld now be able to get the latest proto and py files from them
… finally build this thing and it'll run properly.
…d remaining logged in. will likely need to revert some changes in this commit, and possibly others back to the original fork.
@ABaumher
Copy link
Owner

ABaumher commented May 30, 2023

For the pip-tools 5.4.0 issue, the old code used pip 22.0.4 so that wasn't an issue. Currently that is set at

did you run pip install -r dev.txt in your virtual environment? if so, that line isn't working properly for whatever reason. I know a later pip would break on our code because some of our modules drop support for python 3.7 and their old versions use deprecated calls, which newer pip versions will not allow.

I made a couple changes on MacOS_Fix branch which should hopefully fix the certificate issue without requiring you install the certificates manually. It also grants execute permission on protoc for all users when you run inv InstallProtoc. Unfortunately, it only applies to a new protoc install, it won't work on an existing version. I probably could change that to work there as well. let me know if they work. Unfortunately you may need to test it on a different Mac if all your settings are already working, or uninstall python and the certificates and try again.

Disclaimer: i have done almost no programming on a Mac, so idk if these will work. The best i can do is ensure the InstallProtoc change would work on Linux and the underlying call is the same, but idk.

@ABaumher ABaumher linked an issue May 30, 2023 that may be closed by this pull request
To regenerate protobufs you must get and install the protobuf compiler.

1. `inv InstallProtoc`
2. `chmod a+x protoc/bin/protoc` # the InstallProtoc task does not set the protoc to be executable
Copy link
Owner

Choose a reason for hiding this comment

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

I have hopefully made this part of the install protoc call. See https://github.com/ABaumher/galaxy-integration-steam/blob/MacOS_Fix/tasks.py#L151-L152

Comment on lines +28 to +31
First time Install Python OpenSSL Certificates so the request library can pull Stream protobufs.

1. Install python 3.7 from https://www.python.org/downloads/. It puts Python in your Applications directory
2. `"/Applications/Python 3.7/Install Certificates.command"` You must install for Python 3.7.
Copy link
Owner

Choose a reason for hiding this comment

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

@ABaumher
Copy link
Owner

I'm rewriting the comments, and i'll make sure to use your inputs as a base for the MacOS section. Unfortunately, the changes are on my home computer and i didn't push them, so i can't access them for a few hours. If the certifi and os.chmod fixes work, i can simplify the macos install instructions.

This was referenced May 30, 2023
@ABaumher
Copy link
Owner

I have hopefully fixed all of this on e46968f. Let me know if this is correct for you.

@ABaumher ABaumher force-pushed the master branch 6 times, most recently from bfb80ad to 4a8d717 Compare June 27, 2023 15:19
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.

Getting mac builds working
7 participants