Ok cheers, if you get really stuck let me know I'll ask some guys who did the MIPS version and see what they think.
I'm still poking at it but will be giving it a break for a day or two. Here's what I've learned so far, though.
Building with the default GCC 4.2 isn't feasible as it is too old. It does not support CXX14 which appears to be a C++ dialect. I worked around that by telling it to use Macports GCC7 compiler.
The Macports GCC7 compiler is complaining (see my previous post) because the case statements
here reference constant variables instead of hard coded values. That's not legal in regular C but it is in Objective-C, so I don't know why it's complaining about it as that should be fine. For the time being, I've stripped out media key support just to see if I could get it to compile with the intention to fix it later.
That worked, but then I encountered "-fobjc-exceptions is required to enable Objective-C exception syntax" errors due to the use of @try,
@Catch,
@Finally. I added that compile flag to the Portfile and it got to 87% compiled.
Now I'm running into errors that say "error: cannot convert 'objc_object *' to 'double' in initialization". I stopped there for now. And will try again tomorrow.
Full disclaimer, I have zero prior experience with Objective-C and come from a web development so this isn't my wheelhouse, but I'm learning a fair amount about patching Portfiles from this experience. Here's the thing,
@Steve030. None of the issues so far have been related to the Barrier C code itself. They've all been in the 0.12% of the code that is Objective-C and OS-X specific. So I think that all of these are strictly Mac related Objective-C issues.
I did take a full diff of the Irix code base and the original Barrier source code. It looks like all their changes are Irix and X11 specific so none of them really apply here.
Either way, I'm hopeful that I can get this working. Some help would certainly be appreciated. Hopefully all this info can help someone else figure out what needs to be done.