Trying out ROOL C/C++
David Thomas (43) 72 posts |
I was under the impression that I’d be able to build a full Beagle ROM straight from the original source (i.e. without modifications) once I had the upgraded toolchain. I tried the most tricky component build I’m aware of – SpriteExtend – but found that objasm barfs on the v6 instructions the compiler outputs. I was also expecting updates to the changelogs in the upgrade but there’s nothing. |
Steve Revill (20) 1361 posts |
These sources build with the latest set of the tools here. Where are your sources coming from, when did you download them and are you sure the latest version of the tools is installed? When you install the AcornC/C++ stuff from the CD, you then need to install the tools into the ROOL build, too – this may do nothing if you’ve already installed the older set. Ideally, start from a clean set of sources from the ROOL site and run the script in RiscOS.Library which installs the tools from your AcornC/C++ directory. As for change logs, no we haven’t pulled all of that information out of cvs. We could certainly do that at some point. It’s worth noting that a lot of the changes which have been made historically have been of the: “Fixed lots of bugs” type which is completely useless. That’s as much as we know, too, so short of diffing the sources, it’s the best you can hope for. :( |
Steve Revill (20) 1361 posts |
Also on the change logs front, it’s only in the very latest build that ROOL got all of the C Tools CD stuff building from CVS. I don’t think Castle ever bothered with that (doing stuff by hand) so we have no record of what versions of what went into previous releases. Hopefully, if we do a future Tools CD release, we will have a much clearer idea of what has changed since the previous version. |
David Thomas (43) 72 posts |
I wiped my copy of the source, obtained a clean copy, merged it all together and rebuilt—it worked. I guess I must have munged one of the CFLAGS at some point. |