Detail:
Makefile
to use shared makefile fragmentsmodgen
to create the !Alarm module, which obsoletes some source filesResources:$.Apps.!Alarm
are now registered by the !Alarm
module, so you can kill or unplug the module to hide itCode
blob used to be installed in ResourceFS both by the Messages
module and by the !Alarm module - now de-duplicated (only in Messages).gitignore
filesAdmin: Requires RiscOS/BuildSys!32
ROOL (74ce8405) at 14 Aug 14:35
Modernise build structure
MkInstalls in <Install$Dir>.Apps
Nice to understand why it happened, but yuck to the Do
workaround.
It's rarely useful to install is inside Obey$Dir, so we should follow ChangeFSI/Chars/CloseUp/etc etc and install in HardDisc4 somewhere.
Ooooookaaaay, that's beyond subtle! I'll leave it to someone fussing about whitespace in future to remove it.
That last update is to support building with GNU make with TARGET
specified on the command line (as srcbuild
does during the resources
phase).
I reckon what's happening is that it's now using BasCrunch
to do the crunching, which is an Obey file - so <Obey$Dir>
has been changed by the time we reach the copy step. I found a suspicious copy of !Alarm
in RiscOS.Library.Build
, which supports this! The other way to fix it (which I've included in the latest push) is to stick a Do
at the start of the line in !MkInstall
.
INSTAPP_FILES
, RES_FILES
and RESAPP_FILES
make up a kind of table, indicating which files are installed at which locations. They're sorted alphabetically horizontally, and where there's a gap, that file is not installed at that location. I could shuffle the intermediate lines to below them all if that would make it clearer?
... which were necessary at the time of authoring
For some reason I can't fathom this stops !MkInstall working.
It goes through the motions, all the commands to create things in <obey$dir> go past, but zero output. Perhaps <obey$dir> isn't pointing where I think?
My quality workaround is just to edit !MkInstall to have INSTDIR=<install$dir>.HardDisc4.Apps
which does work and is more like other apps do anyway.
Slightly curious gap between !RunImage and Alarms, same on RES_FILES
line?
Unnecessary edits