> Pull it like this...
Thanks. The code at that link compiled, no problems.
Will that link always work? I usually pull the .rar file from https://github.com/Robbbert/mameui/tree/master/docs/release, which is where the link on the MameUI home page goes. I then copy that over vanilla Mame's source. That worked fine up until release 0.178. Then I started to have compile problems, I'm guessing because the builds started to be on some arbitrary snapshot of git daily code instead of stable release code.
If this is the best way to get the source now, John IV may want to link it on the MameUI home page, instead of the release directory. If Robbbert is using git daily builds of Mame instead of release builds, then it makes sense to just pull the entire source from the MameUI repo as you described.
Since you can't get the vanilla code from mamedev and then add the source .rar any more, it might make sense to just stop releasing that .rar file. Of course, that is if the decision to go with a daily snapshot of the source instead of the release code is final. The .rar simply isn't useful if you can't pull the exact snapshot the MameUI source package is expecting.
The good news, however, is that it compiles just fine with GCC 6.2.0, which is in the current toolchain. I don't know why it's treating strict syntax warnings as compile interrupting errors, but I'll happily test it on the current tools for you on each release.
I can report back here when it does and does not compile with the current tools. Let me know.
BTW, I think
git clone https://github.com/Robbbert/mameui.git
also works for getting the current source for MameUI. Is that right, or will that sometimes pull unstable development code?