Closed badvision closed 3 years ago
First, you'll need to get SDL. This can easily be done through homebrew or macports. Due to a boost API change, you'll need to edit frontend/config.cpp and change all instances of
boost::property_tree::xml_writer_settings<char> settings ('\t', 1);
to
auto settings = boost::property_tree::xml_writer_make_settings<std::string> ('\t', 1);
source: http://www.pcl-users.org/problem-getting-PCL-1-7-1-on-osx-10-9-td4035213.html Then, when configuring your makefile with cmake, make sure to pass it your sysroot. I had trouble passing the TARGET argument, so I just changed the default target to macosx. Finally, I had to change the architecture flag in the makefile from x86 to x86_64 so that Cannonball could be linked with 64-bit SDL. That should be all you'll need to do. Roms should be stored in a folder called "roms" in the same directory as the executable.
Thanks! Yeah that is basically what I had to do, but I did manage to get it working as well. Is the master branch going to be updated to reflect the boost API change or should this sort of thing be maintained in a fork for the newer Boost library?
On Mon, Jan 12, 2015 at 5:57 PM, Ford Seidel notifications@github.com wrote:
First, you'll need to get SDL. This can easily be done through homebrew or macports. Due to a boost API change, you'll need to edit frontend/config.cpp and change all instances of
boost::property_tree::xml_writer_settings
settings ('\t', 1); to
auto settings = boost::property_tree::xml_writer_make_settingsstd::string ('\t', 1);
source: http://www.pcl-users.org/problem-getting-PCL-1-7-1-on-osx-10-9-td4035213.html Then, when configuring your makefile with cmake, make sure to pass it your sysroot. I had trouble passing the TARGET argument, so I just changed the default target to macosx. That should be all you'll need to do. Roms should be stored in a folder called "roms" in the same directory as the executable.
— Reply to this email directly or view it on GitHub https://github.com/djyt/cannonball/issues/11#issuecomment-69671381.
Some preprocessor directives might be the best option in order to maintain compatibility with both the old and new boost APIs.
Any chance of a binary release of a current macOS port? Thanks!
I don't maintain the Mac port unfortunately. But anyone is welcome to create one from the latest source code.
The Mac binary is not up-to-date and crashes when you try to use Japan tracks. Are there tips on how to build mac binaries from the current source?