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

Frameworks for 10.6-10.7 engines and 10.8+ engines #25

Closed
vitor251093 opened this issue May 25, 2018 · 3 comments
Closed

Frameworks for 10.6-10.7 engines and 10.8+ engines #25

vitor251093 opened this issue May 25, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@vitor251093
Copy link
Owner

In order to support 10.6 and 10.7 systems, there needs to be a separated Frameworks folder (so basically, a different master wrapper) for those systems.

@vitor251093 vitor251093 added the enhancement New feature or request label May 25, 2018
@Gcenx
Copy link
Collaborator

Gcenx commented May 25, 2018

We can just use the Frameworks from 2.6.2 and leave it alone, that way we won't break anything.

Once X11 is removed we can scrap most of the Frameworks dylibs and use actual updated ones since we don't need to worry about maintaining compatibility between WineskinX11 and newer dylibs

@vitor251093
Copy link
Owner Author

Uhn, makes sense.

@chrisballinger
Copy link
Collaborator

If I were to vote I'd say drop support for anything under 10.8 and possibly even 10.10.

vitor251093 pushed a commit that referenced this issue Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants