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

Mac build using Xcode fails #8

Open
ryandesign opened this issue Mar 17, 2022 · 2 comments
Open

Mac build using Xcode fails #8

ryandesign opened this issue Mar 17, 2022 · 2 comments

Comments

@ryandesign
Copy link

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
Copy link
Owner

elasota commented Mar 17, 2022

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
Copy link
Author

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

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

No branches or pull requests

2 participants