-
Notifications
You must be signed in to change notification settings - Fork 25
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
Need two more branches legacy & post Mojave #30
Comments
Sorry, didn't had the time to answer properly before. How do I create those branches? Btw, have you and Chris already joined the Porting Team Discord? |
Since my current pull requests are not merged yet you should be able to just make two branches from within Xcode using the current Head. Then upload them might even be able to do it from GitHub but I never looked I rather do it all from Xcode. Also don't merge yet anyway I want to do some more work before we merge that into the master branch, I will just rebase one of my branches and open a new pull-request so its a cleaner
@chrisballinger did you join the Porting Team Discord? |
Just created the new branches :) I just made them from inside the other branch, Also added two more branches: |
Yeah I noticed but that's nothing they can easy be updated to also include the updated z7a |
@Gcenx I wasn't invited, where is it? |
@chrisballinger, Oh you don’t use http://portingteam.com no wonder. Let you want me to send you a invite to the email listed on your github account? |
As the title says
Gonna need a legacy branch for that 10.6.8 support & one for post Mojave.
I already have a working branch for post Mojave with some caveats;
Still needs a 64bit replacement for 7zip for Wineskin/winery & wsgamma I believe is only 32bit so need a replacement for that.
That’s all Mojave beta complained about Wineskin/winery of course it still complains about WINE but that’s not really on us to implement.
The text was updated successfully, but these errors were encountered: