Joined: 6-May-2007 Posts: 10698
From: Greensborough, Australia
I think the show stoper number one for me, is just downloading some and be able to run configure, or this build system, and do it natively on AmigaOS, being able compile and change something and test it rapidly, is the key to being able to work efficiently, and actually getting things done.
I quite agree. Whenever I've tried to compile a port to OS4 it always breaks. Sometimes it tends to be the sh interpreter or the base tools breaking on path conventions. Everytime I try a configure it goes so far then starts asking for weird directory names. Apart from that it can fail to delete folders for the aforementioned reason then refuse to go futher. And it hasn't even tried to compile anything yet. Related to this is CMake. I once need to get the latest CMake OS4 build installed. But it needed all these sobjects that were not included and some were hard to find. To get it working I had to hack some sobjects into my system and kas1e is still talking about it!
I have set up a cross compiler on Linux and mostly because you just can't just port software to OS4 alone. Some takes a lot of work still to compile and even then it might not work. I think it was FreeCiv I was compiling one time. I got assistance to get it built (MickJT? IIRC) then it just didn't work. Loaded up but was faulty. Not sure but it may have been a threading issue. It may have been written for common threads but because OS4 doesn't have real threads it breaks.
There are other things like GDB I wanted to get working again. But it only gets so far. Or in some cases needs to run native PPC code as part of the process. Always got stuck on GDB as I applied the OS4 patches but they rely on an ancient compiler to work. And there is too much work compilng the latest. Apparently GDB needs to be majorly patched to compile a build for OS4 PPC. Perhaps like a browser. So why it lingers on in a broken state. I try and compile it once a year!