Building a single RISC OS module using DDE
Pages: 1 2
Michael Gerbracht (180) 104 posts |
I managed to setup DDE with !Builder to build the whole RISC OS ROM. However I wonder how you can build a single module only, e.g. one of the toolbox modules. I couldn’t find any documentation for this case – only for the whole ROM. So any hint is welcome – thanks! |
Chris Gransden (337) 1148 posts |
Once you’ve built the ROM and with !Builder running with the ‘Build Directory’ and ‘Environment’ set. Just go to the folder. e.g. RiscOS.Sources.Toolbox.Gadgets. |
Michael Gerbracht (180) 104 posts |
Thanks Chris, actually I have tried this before but I do get the following error: do mkdir -p aif
AMU: * ‘standalone’ not re-made because of errors * |
Chris Gransden (337) 1148 posts |
That just means the default ‘Next’ size (640KB) in tasks is too small. Just drag the ‘Next’ bar in tasks to make it bigger. |
Michael Gerbracht (180) 104 posts |
Ok, stupid mistake, I thought ist is more complicated but it worked now! Also changed in boot choices now. |
Paolo Fabio Zaino (28) 1792 posts |
yeah also just for future ref… DDE right now requires at least 1MB (works better with 2MB) So either change Wimpslot -next OR you can set a Wimpslot -min 1024k on your Mk TaskObey if you use one, they both work fine… |
David J. Ruck (33) 1495 posts |
I think I’ve got my next slot set to 32MB, as that’s just enough for gcc. |
Rick Murray (539) 13392 posts |
I hacked my ROM to set it to 4096K, as 640… made sense in 1990. Not so much these days. |
Steve Pampling (1551) 7925 posts |
I think changing the Desktop fie might be easier for most users |
Stuart Swales (1481) 351 posts |
!Amu.Desc needs its slot size increasing. I do this each time I get an updated DDE. Don’t know which bit of !Builder needs changing, but an analogous change would be best done there. |
David J. Ruck (33) 1495 posts |
Bill gates said 640K ought to be enough for anybody in 1981, according to RISC OS its the only thing he ever got right :) |
Michael Gerbracht (180) 104 posts |
Ok, I have a follow up question: I managed to build a ROM module and would like to test it. How can I replace a ROM module? I can’t RMKill it because it is in use. |
Stuart Swales (1481) 351 posts |
Build a ROM! |
Steve Pampling (1551) 7925 posts |
It depends is the straight answer. If it’s something like Window Manager then you can do the replacement in the early !boot with an RMKill and RMLoad of your replacement. If it’s something more fundamental then Stuart is right and you build a ROM |
Sprow (202) 1113 posts |
If the particular module you’re wanting to test is related to…
…then beware the irony that !Builder is a toolbox application, and so you have to quit it in order that there are no toolbox applications running as clients, and therefore the underlying module(s) can be softloaded without needing to brew a ROM. |
Michael Gerbracht (180) 104 posts |
Yes, it is about one of the toolbox modules. I managed now to kill the ROM module and load the RAM module in predesk. But of course you are right that you can also build the whole ROM. I was just afrait of using a ROM were I made changes because if I do something wrong I may not be able to start the raspberry anymore. But I remebered now that this part can be accessed from windows so that I can exchange rom images quickly if something goes wrong. So this is also a good option. |
Andreas Skyman (8677) 170 posts |
I’m having a similar problem. I am interested in the |
Stuart Swales (1481) 351 posts |
Try first building a ROM with zero changes. Did you make sure that you had selected the correct target for the ROM? |
Andreas Skyman (8677) 170 posts |
After some tinkering I managed to get a bootable ROM (thanks Stuart, should have thought of that myself). It boots to before desktop (though I get a mouse pointer), then errors out to Anyway, I decided to ignore this for now, reapplied changes, and can confirm that I could add a new keyboard option that work the way I want it to (that is to say, |
Rick Murray (539) 13392 posts |
That’s Squash_Decompress. https://www.riscosopen.org/wiki/documentation/show/Squash_Decompress Is your ROM being built correctly? Yup, progress. Well done on adding a new keyboard handler! Edit: Good call Julie, that’s a possibility too. |
Julie Stamp (8365) 462 posts |
Do you have anything unplugged? |
Rick Murray (539) 13392 posts |
Hmm, the ISO version of EurKEY Colemak-DH looks interesting. I’d tweak that to put " over 2 (UK style), but otherwise, looks like a pretty well thought out layout. |
Andreas Skyman (8677) 170 posts |
Well… Evidently not? :) It’s about twice the size of the ordinary ROM, so perhaps it hasn’t squashed as it should? I’ll have a look again, but I think the Build/Join/Install stages passed without error.
Thanks! I’ll be honest, now that I know that it works, I’m not sure I’m going to finish it. |
Andreas Skyman (8677) 170 posts |
Such as? Everything that was normally plugged in was plugged in when I tested, I think.
This is the version I’m using and started implementing: UK (or GB, according to X) version of Colemak, as defined in my Linux distro (Debian). |
Julie Stamp (8365) 462 posts |
I meant if you do |
Pages: 1 2