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

Edits to CMakeLists.txt to use existing Raspbian binaries for SDL2 and SDL2 Mixer #306

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Gravesy91
Copy link

The CMakeLists.txt file has been edited so that Shockolate can be compiled on Raspbian Buster without needing to run ./build_deps.sh and will instead use the binaries for SDL2 and SDL2 mixer as provided by the Raspbian repository. This is a major time saver when compiling Shockolate on the Raspberry Pi. This in turn should mean that Shockolate will compile on Debian without any issues in a few weeks when Debian Buster is released.

Here's the changes I've made:

-Removed the m32 compiler flags since Raspbian's compiler does not recognize it.

  • Changed the find_library command for SDL2 to find_package.
  • Removed NO_DEFAULT_PATH from the find_command for SDL2 Mixer.

The CMakeLists.txt file has been edited so that Shockolate can be compiled on Raspbian Buster without needing to run ./build_deps.sh and will instead use the binaries for SDL2 and SDL2 mixer as provided by the Raspbian repository. This is a major time saver when compiling Shockolate on the Raspberry Pi. This in turn should mean that Shockolate will compile on Debian without any issues in a few weeks when Debian Buster is released. 

Here's the changes I've made:

-Removed the m32 compiler flags since Raspbian's compiler does not recognize it.
- Changed the find_library command for SDL2 to find_package.
- Removed NO_DEFAULT_PATH from the find_command for SDL2 Mixer.
@Interrupt
Copy link
Owner

This breaks the builds for the rest of the platforms, so we should probably add this in as a CMake Option to toggle this behavior specifically for Raspberry Pi builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants