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

Binary only supports 11.0 and up #1

Closed
prayerie opened this issue Jan 26, 2022 · 5 comments
Closed

Binary only supports 11.0 and up #1

prayerie opened this issue Jan 26, 2022 · 5 comments
Assignees
@prayerie
Labels
bug Something isn't working urgent
Milestone
0.2.0

Comments

@prayerie
Copy link
Owner

This is due to the installer basing the bundled binaries on the installed version of python on my system (12.1).

Building with MACOSX_DEPLOYMENT_TARGET set to 10.9 results in a binary having a min version of 11.0.
@prayerie prayerie self-assigned this Jan 26, 2022
@prayerie prayerie added bug Something isn't working urgent labels Jan 26, 2022
@prayerie prayerie added this to the 0.2.0 milestone Jan 26, 2022
@thenetstud
Copy link

Tested on Catalina 10.15.7 and the app failed to launch. Will keep an eye on this project incase it is supported in the future.

@prayerie
Copy link
Owner Author

Tested on Catalina 10.15.7 and the app failed to launch. Will keep an eye on this project incase it is supported in the future.

I'm honestly not sure why this is happening as all binaries and frameworks when inspected with otool now have a minimum build version of 10.9 in the newest release.

Could you possibly try (with version 0.1.1) posting the output of running .../CrystalRCM.app/Contents/MacOS/CrystalRCM from the terminal please?

@thenetstud
Copy link

Tested on Catalina 10.15.7 and the app failed to launch. Will keep an eye on this project incase it is supported in the future.

I'm honestly not sure why this is happening as all binaries and frameworks when inspected with otool now have a minimum build version of 10.9 in the newest release.

Could you possibly try (with version 0.1.1) posting the output of running .../CrystalRCM.app/Contents/MacOS/CrystalRCM from the terminal please?

So I launched the CrystalRCM file from within the CrystalRCM.app/Contents/MacOS/ and it opened for me. Now opening the app itself works too. Strange, glad its working though.

@prayerie
Copy link
Owner Author

Tested on Catalina 10.15.7 and the app failed to launch. Will keep an eye on this project incase it is supported in the future.

I'm honestly not sure why this is happening as all binaries and frameworks when inspected with otool now have a minimum build version of 10.9 in the newest release.

Could you possibly try (with version 0.1.1) posting the output of running .../CrystalRCM.app/Contents/MacOS/CrystalRCM from the terminal please?

So I launched the CrystalRCM file from within the CrystalRCM.app/Contents/MacOS/ and it opened for me. Now opening the app itself works too. Strange, glad its working though.

Ah glad to hear, maybe there was a mixup with the old version

@prayerie
Copy link
Owner Author

fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prayerie prayerie

Labels
bug Something isn't working urgent
Projects
None yet
Milestone
0.2.0
Development

No branches or pull requests
2 participants
@prayerie @thenetstud