How to build RO on an A9Home

After struggling through a few problems, I managed to build a ROM on the A9Home recently. I’ve added a Wiki page about it here in the hope that it might help others. Actually, some of the problems may affect other systems too.

Note this is building on an A9Home, not for an A9Home. That’s a bit further down the line! ;-)

During the build process (of the OMAP3 ROM at least), some special utilities get built from source which are subsequently used themselves in the build process.

Rather than laboriously changing all the makefiles, why not just replace the ‘squeeze’ binary with an empty obey file of the same name, or an empty BASIC file with a REM statement in it. Both of these can be run as usual but have no side effects.

Rather than laboriously changing all the makefiles, why not just replace the ‘squeeze’ binary with an empty obey file of the same name, or an empty BASIC file with a REM statement in it. Both of these can be run as usual but have no side effects.

Yeah, that’s a good idea, Sprow. As it seemed to be only one makefile change, it wasn’t too much bother, but perhaps building other products would require more changes, in which case your approach would be better. Feel free to edit the Wiki page! Cheers!

InstallTools and SetPaths32$Dir: for me, the first few lines of !SetPaths.!Boot and !SetPaths.!Run look like this:

|Following Line added by Castle CC
/<Obey$Dir>.SetUp
|##
|
| Desktop C/C++ !SetPaths

and then, in !SetPaths.SetUp:

IconSprites <Obey$Dir>.!Sprites
|32bit17
Set SetPaths32$Dir <Obey$Dir>

So if your files don’t start with that then it’s possible that the tools weren’t installed properly (I seem to remember there being reports that the installer will only work from a CD drive – which the A9home obviously lacks). And if they do start like that but it still doesn’t work then it’s anyone’s guess why ;)

DefMod:

DefMod works fine, here, even though it’s quite obviously a folder. My guess is that it’s some feature of amu that allows it to work, but that this feature is either broken in your copy of the tools or doesn’t work on Select.

InstallTools and SetPaths32$Dir: for me, the first few lines of Boot and Run look like this:

That’s interesting. Indeed, I don’t have that in my Run file, nor do I have a file called ‘SetUp’ in there. I installed the tools from an ISO image using a CD faker. The installer did indeed fail with “File ‘Install_LogDir’ not found” in the CCInsLog file in !Boot. It didn’t seem overly serious at the time, and everything had been copied in place and appeared to work (after xpand-ing binaries). I guess it was probably this step that failed. Hopefully not something as ugly as it failing because I was installing onto IDEFS: rather than ADFS:!