Mac build using Xcode fails

[ryandesign]

I want to build Aerofoil 1.1.2 from source on macOS 10.15.7 using Xcode. First I had to disable the code-signing stuff. Then the build failed with:

AerofoilMac/Resources/Houses/Titanic.gpf: No such file or directory
AerofoilMac/Resources/Houses/Teddy World.mov.gpf: No such file or directory
AerofoilMac/Resources/Houses/SpacePods.mov.gpf: No such file or directory
AerofoilMac/Resources/Houses/Slumberland.mov.gpf: No such file or directory
AerofoilMac/Resources/Houses/Titanic.mov.gpf: No such file or directory
AerofoilMac/Resources/Houses/SpacePods.gpf: No such file or directory
AerofoilMac/Resources/Houses/The Asylum Pro.gpf: No such file or directory
AerofoilMac/Resources/Houses/Teddy World.gpf: No such file or directory

In Aerofoil/Resources there is a README.TXT which says

Extract resources from the Windows build

but it is not explained how to produce the Windows build.

Ideally, it is desirable to be able to produce the Mac build without needing any files from elsewhere.

[elasota]

The main way to build the Windows build is to install WiX Toolset and build the ReleasePackageInstaller project in the solution, which will also generate the game data.

If you want to do this without VS then the batch file that generates the game data is ConvertResources.bat. Getting that to work will also require porting most of the command-line tools (at minimum, MiniRez, gpr2gpa, FTagData, MergeGPF, GenerateFonts, ConvertColorCursors, hqx2gp, and HouseTool all need to be ported, and for most of those, WindowsUnicodeToolShim also needs to be ported).

Most of those should be self-explanatory, except for WindowsUnicodeToolShim which is basically just a wrapper of some functions for porting the tools. Since macOS uses UTF-8 for arguments and file paths natively, most of what's in that just has to be single-line functions there, except for the directory scan which I know nothing about off-hand.

[ryandesign]

Thanks for the explanation! Porting those tools to UNIX looks like a good project for another day.

[Diomendius]

Now that #19 has been merged, it should be possible to build Aerofoil and its resources from scratch on macOS and Linux. I have only tested this on Linux, but I tried to implement everything using interfaces also supported on macOS, so with luck it should work.

This is probably more relevant to #9, as it only applies to the CMake build, but that issue does not mention the resources while this issue does. AerofoilMac/AerofoilMac.xcodeproj is older than the most recent Mac-specific commit to CMakeLists.txt, but appears to reference a few files that the CMake build doesn't. @ryandesign, you were actually the author of that commit (e78b01a), so you probably know more than me about whether these files are necessary for a working macOS build.

CMake can generate an Xcode project instead of using make with cmake -G Xcode. Otherwise, to use the AerofoilMac/AerofoilMac.xcodeproj project for a from-scratch build, you'll have to update it to add the tools and resources somehow. It shouldn't be necessary to modify the source files unless I overlooked something when porting the tools.

This should build AerofoilMac and all the conversion tools under build and the resources under build/Packaged:

cmake -B build -DPLATFORM=MAC
cmake --build build

This should install AerofoilMac under /usr/local/bin, the resources under /usr/local/lib/aerofoil/Packaged and the conversion tools under /usr/local/lib/aerofoil/tools:

cmake --install build

You may want to install under a different prefix fo /usr/local by appending -DCMAKE_INSTALL_PREFIX=<prefix> to the cmake -B command.

If you do try this build again, please let me know if you encounter any issues.