Chris Sarbora

@Lgt2x this is blocked on your changes requested btw; seems like you're ok with it so just flagging that

Looks like #637 has accomplished this and more in the meantime!

Actually, I'm gonna reopen this one - @winterheart / @Lgt2x I still think it'd be overall better to use @Lgt2x's approach of treating HogMaker as an external (rather than sub-)...

It's good to be back again :) The benefit to me of having CMake treat HogMaker as an external project is that the overall process is better-encapsulated into how Android's...

~Ok, I've got Android working honestly pretty smoothly with the HogMaker cross-compilation as-is (without this PR).~ I do still think it's a nicer build to encapsulate it, as I like...

Update: I **am** blocked on this. The Android build additions needed to configure a second, host-only, native build - _correctly_ - are janky and complex. It will be much better...

Actually, I've just merged this into https://github.com/DescentDevelopers/Descent3/pull/459 - that PR is now ready for review, and this change makes more sense in the context of that one overall.

> The way the game finds game data is very primitive currently, simply looking what's in at the current directory or -setdir argument if set I am actively working on...

> but for some reason, it quits immediately, even after setting the executable bit on it @Kreeblah, try running `xattr -c ` (the overall `.app`, _not_ just the executable inside...

Hmm. This is a bummer. I suppose it's a good forcing function to make us think hard about exactly what information we want from non-dev testers however.