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 requires 10.12 (Sierra) #935

Open
unknown-- opened this Issue Jul 29, 2017 · 14 comments

Comments

Projects
None yet
6 participants
@unknown--

unknown-- commented Jul 29, 2017

Reporting a bug? Please make sure you've given the following information - thanks!

Operating system and version:

OS X - 10.11.4

Is this for single player or multiplayer?

Both

Description of the bug (and if possible, steps to reproduce the bug):

Mac builds since January are 10.12 only. Can you please explain why and if it's possible for the user to manually change the version requirement.

@ensiform

This comment has been minimized.

Show comment
Hide comment
@ensiform

ensiform Jul 29, 2017

Member

@MazterQyou are you still hosting the builder? Wonder what would have changed here

@redsaurus @xycaleth

Member

ensiform commented Jul 29, 2017

@MazterQyou are you still hosting the builder? Wonder what would have changed here

@redsaurus @xycaleth

@MazterQyou

This comment has been minimized.

Show comment
Hide comment
@MazterQyou

MazterQyou Jul 29, 2017

Contributor

I'm still hosting the builder, but I'm not configuring how it builds. Cat is in charge of that

Contributor

MazterQyou commented Jul 29, 2017

I'm still hosting the builder, but I'm not configuring how it builds. Cat is in charge of that

@ensiform

This comment has been minimized.

Show comment
Hide comment
@ensiform

ensiform Jul 29, 2017

Member

@deepy do you recall any configuration changes for mac builds recently?

Member

ensiform commented Jul 29, 2017

@deepy do you recall any configuration changes for mac builds recently?

@MazterQyou

This comment has been minimized.

Show comment
Hide comment
@MazterQyou

MazterQyou Jul 29, 2017

Contributor

@unknown-- how did you figure that Sierra is required? Can you provide crashlog or something?

Contributor

MazterQyou commented Jul 29, 2017

@unknown-- how did you figure that Sierra is required? Can you provide crashlog or something?

@deepy

This comment has been minimized.

Show comment
Hide comment
@deepy

deepy Jul 29, 2017

Member

As far as I know there's been no configuration changes in the Mac builds for a long time

Member

deepy commented Jul 29, 2017

As far as I know there's been no configuration changes in the Mac builds for a long time

@unknown--

This comment has been minimized.

Show comment
Hide comment
@unknown--

unknown-- Jul 30, 2017

@MazterQyou I get this message:
screen shot 2017-07-30 at 3 01 50 pm

unknown-- commented Jul 30, 2017

@MazterQyou I get this message:
screen shot 2017-07-30 at 3 01 50 pm

@deepy

This comment has been minimized.

Show comment
Hide comment
Member

deepy commented Jul 30, 2017

deepy added a commit that referenced this issue Aug 11, 2017

@deepy

This comment has been minimized.

Show comment
Hide comment
@deepy
Member

deepy commented Aug 11, 2017

@unknown-- could you please try https://builds.openjk.org/openjk-2017-08-11-a0828f06-osx.dmg and see if that works?

@unknown--

This comment has been minimized.

Show comment
Hide comment
@unknown--

unknown-- Aug 12, 2017

@deepy

I'm afraid it still gives the error.

unknown-- commented Aug 12, 2017

@deepy

I'm afraid it still gives the error.

@ensiform

This comment has been minimized.

Show comment
Hide comment
@ensiform

ensiform Aug 12, 2017

Member

@deepy did you force a fresh build with rerun cmake without cache?

Member

ensiform commented Aug 12, 2017

@deepy did you force a fresh build with rerun cmake without cache?

@Klezstyle

This comment has been minimized.

Show comment
Hide comment
@Klezstyle

Klezstyle Sep 15, 2017

The problem with that 2017-08-11 build is the path of the LibSDL2 library:

This is the straightforward error:
_

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/local/opt/sdl2/lib/libSDL2-2.0.0.dylib
  Referenced from: /Volumes/VOLUME/*/openjk_sp.x86_64.app/Contents/MacOS/openjk_sp.x86_64
  Reason: image not found

_

In macOS the SDL Library is:
"/Library/Frameworks/SDL2.framework"

Klezstyle commented Sep 15, 2017

The problem with that 2017-08-11 build is the path of the LibSDL2 library:

This is the straightforward error:
_

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/local/opt/sdl2/lib/libSDL2-2.0.0.dylib
  Referenced from: /Volumes/VOLUME/*/openjk_sp.x86_64.app/Contents/MacOS/openjk_sp.x86_64
  Reason: image not found

_

In macOS the SDL Library is:
"/Library/Frameworks/SDL2.framework"

@MazterQyou

This comment has been minimized.

Show comment
Hide comment
@MazterQyou

MazterQyou Sep 15, 2017

Contributor

Looks like CMake is building against Homebrew SDL2. I guess cmake args have to be changed to force build against system SDL2.framework.
Although afaik macOS doesn’t cone with SDL2 at all. So it should actually be bundled inside app and rpaths have to be set correctly upon packaging a .dmg.

Contributor

MazterQyou commented Sep 15, 2017

Looks like CMake is building against Homebrew SDL2. I guess cmake args have to be changed to force build against system SDL2.framework.
Although afaik macOS doesn’t cone with SDL2 at all. So it should actually be bundled inside app and rpaths have to be set correctly upon packaging a .dmg.

@ensiform

This comment has been minimized.

Show comment
Hide comment
@ensiform

ensiform Sep 15, 2017

Member

Mind trying to rearrange that ? So it doesn't require homebrew? The current wiki and instructions seem to discuss requiring it.

Member

ensiform commented Sep 15, 2017

Mind trying to rearrange that ? So it doesn't require homebrew? The current wiki and instructions seem to discuss requiring it.

@kencu

This comment has been minimized.

Show comment
Hide comment
@kencu

kencu Dec 16, 2017

Contributor

I just built it on 10.6.8 without any trouble using MacPorts sudo port -v install openjk (also builds and runs on every system up to 10.13).

Contributor

kencu commented Dec 16, 2017

I just built it on 10.6.8 without any trouble using MacPorts sudo port -v install openjk (also builds and runs on every system up to 10.13).

deathsythe47 added a commit to jkanewmod/NewJK that referenced this issue Aug 18, 2018

eternalcodes pushed a commit to eternalcodes/EternalJK that referenced this issue Aug 21, 2018

eternalcodes pushed a commit to eternalcodes/EternalJK that referenced this issue Aug 21, 2018

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