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

Cannot open solvespace.dmg on OSX #398

Closed
fredOnGitHub opened this issue Apr 30, 2019 · 32 comments
Closed

Cannot open solvespace.dmg on OSX #398

fredOnGitHub opened this issue Apr 30, 2019 · 32 comments
Labels
Milestone

Comments

@fredOnGitHub
Copy link

fredOnGitHub commented Apr 30, 2019

a

System information : Mac Mojave 10.14.4

SolveSpace version: solvespace.dmg

Operating system: Mac

Expected behavior

What should have happened?

Actual behavior

Cannot open solvespace.dmg on OSX

Additional information

@whitequark

This comment has been minimized.

@thmrtnz
Copy link

thmrtnz commented May 22, 2019

It's quite bizarre.
I can run SolveSpace 2.3 in macOS 10.14.5 given I delete the packaged dylibs first.
This from a freshly downloaded dmg from the releases section here, Github.

@fredOnGitHub
Copy link
Author

fredOnGitHub commented Jun 6, 2019

It's quite bizarre.
I can run SolveSpace 2.3 in macOS 10.14.5 given I delete the packaged dylibs first.
This from a freshly downloaded dmg from the releases section here, Github.

Hello,

Thank You for your helping,

Merci !

Yes ! On macOS 10.14.5 I have

  • brew install cmake libpng freetype
    (see after the Installation "section" in "Building" from the the README.md)
    Maybe it works without that

  • deleted (in blue)

  1. libfreetype.dylib
  2. libpng.dylib
  3. libz.dylib
    from tha solvespace's package
    Capture d’écran 2019-06-06 à 16 51 04
    in the bind
    Capture d’écran 2019-06-06 à 16 53 59
  • and after leaving the package, clicking on the application logo
    Capture d’écran 2019-06-06 à 16 57 30

It works when opening
Capture d’écran 2019-06-06 à 17 34 23

Thanks

@fredOnGitHub fredOnGitHub changed the title Cannot open solvespace.dmg on OSX Closes #398 Cannot open solvespace.dmg on OSX Jun 6, 2019
@whitequark whitequark changed the title Closes #398 Cannot open solvespace.dmg on OSX Cannot open solvespace.dmg on OSX Aug 1, 2019
@whitequark whitequark pinned this issue Aug 1, 2019
@tko
Copy link

tko commented Oct 30, 2019

From the looks of it, each of libz, libpng, and libfreetype is frozen to a (relatively old) vendored version.

solvespace/CMakeLists.txt

Lines 134 to 137 in 5d78f99

set(FORCE_VENDORED_ZLIB ON)
set(FORCE_VENDORED_PNG ON)
set(FORCE_VENDORED_Freetype ON)
endif()

As the vendored versions aren't working anymore, it might be better to remove the forced versioning, or update the versions. (Generally speaking, I'm not familiar with macos app distribution.)

@vespakoen
Copy link
Contributor

vespakoen commented Nov 28, 2019

! Testers needed !

I have worked on Catalina support, and some macOS related fixes.

I also updated the CI config so new installers can easily be built and released in the future.

I have signed (and notarized) SolveSpace with my own personal developer certificate.

This should install without any problems on macOS and i'd like to verify if that's really the case.

https://github.com/vespakoen/solvespace/releases

Note that I tagged it 2.4 3.0-vespakoen and that this is NOT an official release.

This PR adds the new CI config: #517

And the 3.0-vespakoen release is based on the latest commit on master (0472b9e)

@whitequark
Copy link
Contributor

Please do not make an one-sided choice of version numbers to distribute builds of. There will be no 2.x releases after 2.3, and the branch you have built is a development build from the 3.x series. Calling it something like 3.0.vespakoen would have been much better.

@vespakoen
Copy link
Contributor

Ok I'll change that.

I had to tag it with something to get the file out of travis, and that was the best I could come up with in that moment.

@altaic
Copy link

altaic commented Nov 29, 2019

! Testers needed !

I have worked on Catalina support, and some macOS related fixes.

I also updated the CI config so new installers can easily be built and released in the future.

I have signed (and notarized) SolveSpace with my own personal developer certificate.

This should install without any problems on macOS and i'd like to verify if that's really the case.

https://github.com/vespakoen/solvespace/releases

Note that I tagged it 2.4 3.0-vespakoen and that this is NOT an official release.

This PR adds the new CI config: #517

And the 3.0-vespakoen release is based on the latest commit on master (0472b9e)

Works for me on macOS 10.12.6!

On first opening (after copying it to /Applications), Solvespace did display an error "Couldn't read from file '/-psn_0_35709452'" though it has not reappeared since. I'm guessing it was due to detritus from my previous Solvespace install.

Edit: After messing around for a few minutes, it seems to be a solid build. Fast, too! Thanks!

@vespakoen
Copy link
Contributor

Thanks for the report!
Interestingly I remember seeing a similar error popup in first load.

I didn't find psn anywhere in the source code though so I am not sure where it comes from.

Glad the dmg / app is working though

@whitequark
Copy link
Contributor

Could the psn thing be related to macOS opening on startup what it thinks the files that were opened the previous time?

@vespakoen
Copy link
Contributor

vespakoen commented Nov 29, 2019 via email

@stiff
Copy link

stiff commented Apr 13, 2020

Runs on 10.15, with /-psn complaints. Maybe it's related to this question https://stackoverflow.com/questions/10242115/os-x-strange-psn-command-line-parameter-when-launched-from-finder ?

Also for some reason locale doesn't match the system one, but this is minor issue.

@gon
Copy link

gon commented May 5, 2020

+1 Thanks @vespakoen, great build indeed!

@tthrift
Copy link

tthrift commented May 5, 2020

@vespakoen Thanks! :)
The 3.0-vespakoen dmg seemed to work fine on macos 10.15.4 (19E287).
Upon first launch only, solvespace did show an error dialog with the message
" Couldn't read from file '/-psn_0_204850' "
This dialog seems consistent with what others have seen.
Otherwise, solvespace seems to be working well so far.

@whitequark
Copy link
Contributor

@stiff Thanks for investigating. I've opened #602.

@vespakoen
Copy link
Contributor

Good news!

I just installed the macOS Big Sur (build 10) beta and SolveSpace seems to be running just fine!

Screenshot 2020-10-19 at 17 41 13

@vespakoen
Copy link
Contributor

I also made a new pre-release for macOS from the latest master branch which you can get over here: https://github.com/vespakoen/solvespace/releases/tag/3.0.0-alpha.4

Feedback & testing is appreciated!

@ruevs
Copy link
Member

ruevs commented Oct 19, 2020

I am curious what does it report here?

settings

@vespakoen
Copy link
Contributor

This is what I got:

Screenshot 2020-10-19 at 20 43 49

(It's on a MacBookPro14,1)

@phkahler
Copy link
Member

I'll try it on my old Macbook Air. I've never installed XCode or done any development on it other than Python, so my environment is not polluted ;-)

@ruevs
Copy link
Member

ruevs commented Oct 19, 2020

So is this Angle using Metal? Or is OpenGL still there in the Big Sur beta? Is there a way to know? (Just curiosity on my part.)

@vespakoen
Copy link
Contributor

I am not sure, but I'll look into that and report back.

@phkahler
Copy link
Member

I'm on Sierra 10.12.6 and it seem to work OK. Is it built as debug or release? With OpenMP or LTO? It does seem slow but this mac is slow compared to my desktop anyway.

@phkahler
Copy link
Member

@ruevs Looks like OpenGL is still there:
https://developer.apple.com/forums/thread/650427

@vespakoen can we build Universal Binaries to run on Apple silicon?

@vespakoen
Copy link
Contributor

It is a Debug build without OpenMP (I will try to enable that soon, I've already added it to OpenCamLib's CMake in the past)
And I will look into the Universal binaries as well.

@phkahler
Copy link
Member

phkahler commented Oct 19, 2020

The option is already there just add -DENABLE_OPENMP=yes and -DENABLE_LTO=yes to you cmake. LTO is probably a bad idea for debug builds that happen when we update a PR because it takes forever.

@vespakoen
Copy link
Contributor

There is a new edge build for macOS which from now on will always be up to date with whats on the master branch.
OpenMP is also included in the macOS build now, and I would love to hear if it's still working for everyone.

https://github.com/solvespace/solvespace/releases/download/edge/SolveSpace.dmg

@stiff
Copy link

stiff commented Oct 26, 2020

Seems to be working good 👍

@phkahler
Copy link
Member

@vespakoen I think it's finally time to close this issue. Thank you so much for all you've done!

@tko
Copy link

tko commented Oct 29, 2020

Can confirm. edge release runs fine for me. (macos Mojave)

@ruevs
Copy link
Member

ruevs commented Oct 29, 2020

We should close it when 3.0 is released and downloadable from the official site.

@ruevs ruevs added this to the 3.0 milestone Apr 7, 2021
@ruevs
Copy link
Member

ruevs commented Apr 7, 2021

@phkahler Added this to the 3.0 milestone so that we remember to close it and remove it from the pinned issues.

@phkahler phkahler unpinned this issue Apr 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests