Build Error

After my DDE Install and ROOL Source download, I tried my first ever ROM Build.
I followed the instruction detailed here –

Beginners Guide to Building RISC OS

At the end of Join Stage of the process it comes up with an error.
Error cannot stat 'HostFS::HostFS.$.Sources.IOMDHALDEV.Install.Rool.IOMD32.RISC_OS.IOMD'. Fatal error cannot stat 'HostFS::HostFS.$.Sources.IOMDHALDEV.Install.Rool.IOMD32.RISC_OS.IOMD'. Batched errors...

Any ideas on what I need to do to remedy this?

In the ‘register build directories’ window did you drag in the IOMDHALDEV directory

In the build options window did you:
select that build directory.
select the ‘ROOL.IOMD32’ Environment
tick ‘Export Headers’, ‘Export libraries’, ‘Export resources’, ‘Make ROM’, ‘Install ROM’ and ‘Join ROM’
click on ‘build’.

It should then compile.

Any ideas on what I need to do to remedy this?

None at, he said helpfully. Is the file is present, here it is a data file of 12144 bytes. I have just successfully built the IOMDDEV ROM here on OS4.39 VRPC.

None at, he said helpfully. Is the file is present,
No. the Images folder is very empty looking. ;-(

I’m going to try again, and see my luck. Sometimes just asking for help somehow makes things work!

In the build options window did you:
select that build directory.
select the ‘ROOL.IOMD32’ Environment
tick ‘Export Headers’, ‘Export libraries’, ‘Export resources’, ‘Make ROM’, ‘Install ROM’ and ‘Join ROM’
click on ‘build’.

Yes, I believe I did all this.
I’m just set off the Build Tool again and see how I get on again. Perhaps I missed one of them (as I was pretty excited at the prospect of Building my own very copy of RISC OS).

I’ll let you know how I get on.

I’ll let you know how I get on.

My Second attempt failed at the same joining stage, but the third time, I opened the DDE Apps folder first(did not click on anything) and I now have my first RISC OS Image file cUV100-00. And it even works. So I can only assume it needs to see a particular !App.

Thanks for the help guys.

You might want to compare what you did with what Rick documented; I’ve successfully used his instructions with no errors.

Excellent Alan. Again odd that you needed to open DDE apps. I run !builder from a shortcut so never see that directory.

Once you have !builder running you can get to the image and build directories via the menu button on the builder window and now that you have successfully done a first build you only need ‘Make ROM’, ‘Install ROM’ and ‘Join ROM’ ticked for rebuilds.

Chris – yes an excellent set of instructions from Rick. He should move it to the ROOL wiki then it could be modified if necessary.

Strange. I boot my machine differently to build RISC OS. My boot normally sets up the DDE but I found that could mess things up. Builder installs bits of the DDE inside itself so running that (alone) ought to be sufficient?

– yes an excellent set of instructions from Rick.

Thanks. <blush!>

Yes I never boot the DDE anymore – as you say it confuses things. I just run builder if I want to compile something.

I have a nice little taskobey file that you may find useful. After you have compiled a rom with builder you click on the file and it copies the successfully compiled rom to ramdisc changing the name to suit the different machines. The only different one is if I’m compiling an Iyonix image where it copies directly to the softload directory – I compile on the iyonix. When you change the build directory in !builder the script will find the correct rom image. It saves you having to work out which is the latest image.

Then what I do is I share the iyonix ram disc and on every machine I have a taskobey file to copy the file from the iyonix ramdisc to the relavant location.

So the process is modify the sources, click on the file below, switch to the machine whose rom i’m changing, run the copy script and reboot.

if "<build$dir>" = "" then ERROR Builder needs running
set copyrom$temp 0
if ("<build$dir>" RIGHT 8 = "OMAP3Dev") AND (("<Build$ImageName>" LEFT 4) RIGHT 3 = "UV8") then set copyrom$temp 1
if <copyrom$temp> AND 1 then copy <build$dir>.Images.<build$imagename> RAM:$.riscos ~CF

if ("<build$dir>" RIGHT 11 = "TungstenDev") AND (("<Build$ImageName>" LEFT 4) RIGHT 3 = "UIT") then set copyrom$temp 2
if <copyrom$temp> AND 2 then copy <build$dir>.Images.<build$imagename> ADFS::HardDisc4.$.!Boot.Choices.Boot.PreDesk.!!SoftLoad.riscos ~CF

if ("<build$dir>" RIGHT 8 = "OMAP4Dev") AND (("<Build$ImageName>" LEFT 4) RIGHT 3 = "UV9") then set copyrom$temp 4
if <copyrom$temp> AND 4  then copy <build$dir>.Images.<build$imagename> RAM:$.riscos ~CF

if ("<build$dir>" RIGHT 10 = "BCM2835Dev") AND (("<Build$ImageName>" LEFT 4) RIGHT 3 = "URZ") then set copyrom$temp 8
if <copyrom$temp> AND 8 then copy <build$dir>.Images.<build$imagename> RAM:$.riscos/img ~CF

if ("<build$dir>" RIGHT 8 = "OMAP5Dev") AND (("<Build$ImageName>" LEFT 4) RIGHT 3 = "UVF") then set copyrom$temp 16
if <copyrom$temp> AND 16 then copy <build$dir>.Images.<build$imagename> RAM:$.uImage ~CF

|if (<copyrom$temp> AND NOT 2) <> 0 THEN filer_opendir RAM::RamDisc0.$

if (<copyrom$temp> AND NOT 0) <> 0 then echo finished else echo No rom to copy
unset copyrom$temp

p.

I opened the DDE Apps folder first(did not click on anything)

In my “normal” setup (which I don’t use for building ROMs) I have the SetPaths app in my boot sequence (under “look at”). This is the one that makes everything work for standard development, but like Rick and Colin say it seems to conflict with Builder so I’m surprised that it worked for building a ROM!