Building RISC OS

Thank you for the information. I guess, for now, I’ll skip keeping up to date with changes (my Pi connects to the internet by piggy-backing off the PC – http://www.heyrick.co.uk/blog/index.php?diary=20131230). I guess I would need to go the !CVS route eventually, just not looking forward to the eternityplussome it would take to sort all that out, for the sake of maybe a handful of changes?
The alternative, perhaps, is to consider writing a program to strip off the CVS data and merging the files into the already-existing source code? I might have a crack at that over the weekend.

I’ll bookmark this for the CVS info. That little obey file may become very important in the future. ;-)

Edit: the ‘*’ in the path name in untarBZ2 is so that it works for all devices.

Only, it has yet to work for me. Keeps on saying that the file is not found.

Hmmm… turns out to be a problem if your destination directory contains another folder which is alphabetically less than the build folder name ie if you have a folder ‘a’ in the destination directory the wildcarded path name won’t find BCM2385dev.Prepare.!run. The prepare phase copies over your C/C++ tools.

I’ll have to think about it.

Well, this is a novelty.

The slow SD card that I was using turned out to be a Class 2. Could explain the speed.
The uSD that I am using now is a Class 4…. But…. It feels as if it has taken half the damn night. I’ll be able to tell when it is done as the log usefully drops in times.

Edit: started 22h55 and finished 00h54 for a full Pi build. A card supposedly twice as fast takes more than twice as long. Hmmm!

On the other hand – just swapped images and this one boots and runs just fine. Phew! After today, if that blew up on me I would probably have faceplanted into my bowl of porridge…
So at least I can retire to my bed now and listen to something relaxing, like… Oh, I don’t know… Evanescence ? (^_^)

More edit: actually listening to Ai Ōtsuka – pon pon pon pon-pon pon pon pon, pon, pon pon pon pon-pon pon pon pon, pon pon pon pon-pon pon pon pon, pon, pon pon pon pon-pon pon pon pon" … Um… Just look up “Ōtsuka pon” on YouTube, you’ll understand… !

Rick: Were both SD cards in the motherboard slot using SDFS?

Rick: Were both SD cards in the motherboard slot using SDFS?

Yes.

Hmmm. If the only change was the SD card then I suspect one or both of the cards are not the CLASS they say or some weird incompatibility.

Rick, you do know that you can use a CVS client to check out a local repository? So if you have the repo files – ie the big CVS archive plus the delta archives dropped over it to merge them (I assume that’s how the archives work) you can just tell the CVS client to use the local repo. You’ll have to experiment as I forget how RISC OS CVS mangles the filenames, but normally instead of :pserver:riscosopen.org/blah/blah you just use the filename of the local repo – in Unix terms that’s /home/foo/thing so either ADFS::HardDisc.$.foo.thing or /ADFS::HardDisc/$/foo/thing

Google ‘cvs local repository’ for some guides.

That doesn’t help you commit changes back to the server, but should be enough to follow development.

the big CVS archive plus the delta archives dropped over it to merge them (I assume that’s how the archives work)

As long as you’ve got forced overwrites enabled(!) it should work fine because one thing about our CVS repository is you’ll only ever get new stuff added; we don’t ever remove anything (FSVO ‘ever’).