!Boot image and AutoSense location

Hi,

I downloaded the latest hard disc image, 20th May 12, and checked out some elements as I noticed that some changes had gone on with the EtheUSB and autosense file namely as below:

https://www.riscosopen.org/viewer/revisions/logs?ident=1337414509-463281.html

On checking the lastest image it seems to put the EtherK and EtherUSB files in location:

!Boot>Resources>Configure>!InetSetup>

Should it not put them in location:

!Boot>Resources>Configure>!InetSetup>AutoSense ?

Should it not put them in location…

Not really sure how they get copied in at all: when I run an install rule on them manually they give an error (on ADFS), whereas inspection of the download shows they’re copied in one directory too high (unless it’s something odd about HostFS which the autobuilder uses).

Anyway – should fix itself overnight for tomorrow’s downloads.

Ok, I wonder if this has something to do with i as it was checked in this morning.

https://www.riscosopen.org/viewer/revisions/logs?ident=1337495775-575504.html

“Make sure the AutoSense directory is always created.
Even if it’s empty – since it’s referred to by !Run.”

Hi Sprow. Manually running the MkInstall file in a component doesn’t (always) install it into the same place as a build. You need to look at the Components file for the build and look at where INSTDIR points. For some components, it is the name of the directory into which to install and in others it’s the name of the directory to create during the install phase (and install more stuff in there). On balance, IMO, it’s pretty random which of these applies – it’s up to the author of the makefile.

Manually running the MkInstall file in a component doesn’t (always) install it into the same place as a build

In this instance, I did pass INSTDIR in manually, and my conclusion was it’s a HostFS oddity. A more clear illustration of this was
*HOSTFS
*COPY !Boot.Utils.BootRun totally.made.up.path
1 file copied, total 1496 bytes

so it seems the target path in HostFS isn’t vetted as existing. Never mind!

so it seems the target path in HostFS isn’t vetted as existing.

Oops!