-
Notifications
You must be signed in to change notification settings - Fork 3
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
gossip with ffmpeg support builds new libSDL2 when it exists already in homebrew #3
Comments
@mikedilger @jacany any idea how to fix this? I tried modifying ENV.prepend "CPPFLAGS", "-I#{HOMEBREW_PREFIX}/include"
ENV.prepend "LDFLAGS", "-L#{HOMEBREW_PREFIX}/lib -Wl,-rpath,#{HOMEBREW_PREFIX}/lib" |
Building on MacOS is not my specialty. I do it for releases because people asked me to. But I haven't booted that machine for a few months. When I get time I'll try to compile it again over there, and to look also at @jacany 's gossip tap. I hope you guys can work out how gossip should be compiled on MacOS, and I'll follow on from that result. |
Fixed by using SDL2 crate feature That feature is not really necessary except maybe for Windows right? |
Ok. I'll have to try it on the other platforms but it sounds right |
I had some issue building on linux with that patch. And I forgot about packaging stuff -- it should be |
Can we somehow unlink from the system SDL2 library and only link to the bundled one? |
Some references:
Seems like a common problem for ios developers. |
gossip is building its own libSDL2 and leaves linking ambiguous. ideally it would just use the existing SDL2 from homebrew.
When modifying the formula to not include the new libSDL2:
Possible solutions?
rpath
tolibexec
?bundled
feature forsdl2
crate?The text was updated successfully, but these errors were encountered: