A Few questions on Builder Process
Alan Robertson (52) 420 posts |
Just installed the RISC OS Development Toolkit and downloaded the ROOL Sources and having a little bit of a play with it all and have a few questions that I’m hoping someone can answer I’m interested in updating some of the standard Applications that come with RISCOS. When It Build a new version of some Apps such as Alarm and Chars, they get Built and the resulting Application is built in the current Obey$ Folder, whereas other Apps such as Paint will get Built and the resulting file will appear in the Install.App Folder. Is there a reason for this? And which method is the correct/preferred method? Where multiple resource files exist for different geographic locations, how does one go about updating each Template file? I would have suspected that they should be the same but with perhaps different string used in them. Again, what’s the preferred way of handling this? Alarm has Template files for both Germany and the UK. Hopefully there is a nice simple approach to this. Once a developer is happy with their changes and wants to submit them back into the ROOL Source, what is the actual end-to-end process? Is there a vetting process whereby people refuse to accept things if they don’t like the changes (I’m thinking more like changes to GUI, rather than a Linus Trovald’s ‘bad programming style’ rant) Apologies if these are all obvious questions. |
Colin (478) 2433 posts |
This is what I would do. 1) Run Builder The trick is to always create the build environment using !builder – do not boot the DDE. You submit your changes to ‘code at riscosopen dot org’ |
Steve Pampling (1551) 8170 posts |
The makefiles are two different styles (from two different eras)
I believe the newer method is to build into the Install.App folder
Shortcut on the Pinboard, run that and the rest of the contents around Builder don’t get the chance to !boot and register. |