ROOL Forum: Recent posts

Tue, 16 Dec 2025 04:03:59 +0000

Very definitely on both IPv6 and IPv4

So what dig -6 returns to you?

dig -6 riscosopen.org

; <<>> DiG 9.10.6 <<>> -6 riscosopen.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36068
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;riscosopen.org.			IN	A

;; ANSWER SECTION:
riscosopen.org.		33	IN	A	91.203.57.12

;; Query time: 19 msec
;; SERVER: ::1#53(::1)
;; WHEN: Tue Dec 16 04:02:58 GMT 2025
;; MSG SIZE  rcvd: 59

Tue, 16 Dec 2025 03:51:43 +0000

@ Timo

Besides the usual 20 billion examples from Gerph XD, here is what I do with really complex C projects on RISC OS, and when using DDE. The example below is almost as complex as the JVM, so it should fit almost every possible need.

First, some of the project structure:

This should give you an idea. The OS-dependent portion is somewhat similar to your gpl→bluetooth. It is a module that allows Ultima to use RISC OS features, so let’s follow that as an example. You can also see that there are other entire sections, like libs, and also an “arch” module that contains all the ASM used to access hardware acceleration where Norcroft C just cannot do the job. That part, in some cases, uses ObjASM, and in others experimentally uses GCC to prebuild certain built-ins and SIMD, as well as to access things like EGL and more.

The first thing I would like you to focus on is the presence of multiple Makefiles, as also suggested by Gerph. This is really important for complex projects, in my opinion.

To compile a module like the RISC OS wrapper library for Ultima with DDE, I can use ROOL shared Makefiles. This is fine when a module is self-contained and builds as a library, for example, so no external linking is required:

I can also pass defines to it. For example, I use this simple mechanism to trigger a build for old Archimedes machines and RiscPCs, (and a big thanks to Sprow for having added back full support for 26-bit builds in the latest DDE).

Next, the slightly more complicated part: the master Makefile that controls the build of many of these “child” modules for the main executable. This is one of the two master Makefiles. I am only sharing one to avoid confusing you. For your project, this should be more than enough, I think:

You can see that the MODS variable contains the OS wrapper C module to build, and then the relative section below reaches it and builds it using the previous Makefile. Note that I call the Makefiles for DDE MakefileDDE and the ones for GCC MakefileGCC. You can also see how I am passing defines to them, in case you need that.

Now, the next picture shows the final part, where I put some of the pieces together for the final executable:

I hope this gives you an idea. If not, I can get onto your repo and help you with that, but I think that between all these examples you should have a good grasp of how you could do it for your project.

HTH and good luck! :)

Mon, 15 Dec 2025 22:47:00 +0000

I wouldn’t use a single Makefile in for that sort of thing. If each part is distinct then I would build them into libraries and import the library instead of having a monolithic Makefile.

Either that or use a VPATH to reference each subdirectory you’ve got sources in, and then `-I` include on your compilation line to ensure that you search all the locations. You’ll find documentation for both in the DDE manual and within general Makefile documentation (eg GNU make).

http://www.riscos.com/support/developers/dde/appa.html… gives a basic overview of VPATH, albeit with some confusing examples (which look like they’re taken from the compiler source).

As I remember you may find that ShareFS has a subdirectory as part of its build which was originally defined using a VPATH, so looking at its source may be helpful. I’m not sure if the Internet module did that too – it’s quite possible. Oh, ShareFS isn’t available is it.

(the autolinking in the forum appears to break this link so I’ve converted to a code element)

https://gitlab.riscosopen.org/RiscOS/Sources/Networkin…

That’s the Internet module’s Makefile which has a VPATH in.

Here’s one for a port of the berry language to RISC OS 64: https://github.com/gerph/riscos64-berry/blob/riscos/ri…

And one for the PocketPy language which has a few more in: https://github.com/gerph/riscos64-pocketpy/blob/riscos…

And the Debugger module I created pulls in separate libraries (Armadillo and Darm are built separately as libraries and then pulled into the Debugger module):

• https://github.com/gerph/riscos-debugger-c
• https://github.com/gerph/armadillo
• https://github.com/gerph/darm

Which solution works for you really depends on the structure of your project.

Mon, 15 Dec 2025 21:39:36 +0000

I’ve had a response from Andrew already, but he says “it may take a day or two of cycle time to resolve.” It seems to be a failure of infrastructure somewhere, likely within Arachsys, ROOL’s hosting provider.

Mon, 15 Dec 2025 21:29:25 +0000

I have :
bluetooth
|
+—c
| |→ several files
|
+—h
| |→ several files
|
+—gpl
| |
| +—> include
| | |
| | +—>net
| | |
| | +—>bluetooth
| | |
| | +—>h (nr of files, no issues there)
| |
| +—>drivers
| | |
| | +—>bluetooth
| | |
| | +—>h ( nr. of files)
| | |
| | +—>c ( nr. of files which I like to compile and link in the main app )
| | ( which I not get working )
| |
| +—>net (etcetra )

As compiler I use the DDE from ROOL. If you want to share an example make file that would be great if that works with the DDE.

Mon, 15 Dec 2025 21:27:16 +0000

You’re most likely on IPv4?

Very definitely on both IPv6 and IPv4. I was surprised when I tried a Three SIM and found it gave me an IPv6 address (not to be confused with what WiFi gives me!). The IPv6 support is the primary reason I moved (just a few days ago) from O2 to Three.

The killer test, which I’ve just repeated, is to access one of my IPv6-only sites from my phone after turning WiFi off. The web page and the site’s log both show the Three IPv6 address of my phone, which has a very different prefix from that given to me by WiFi.

Mon, 15 Dec 2025 21:15:42 +0000

or if there are ways to record the screen ?

If the VNC approach turns out to be not as good as you’d like, You could use RPCEmu and record nativelly on Linux or mac or (as I do) use a capture card which is what gives you most close to real experience, you can see many video recorded here:

https://www.youtube.com/@RiscosCommunityOnGithub

HTH

Mon, 15 Dec 2025 21:12:56 +0000

What are you building with?

Mon, 15 Dec 2025 21:12:28 +0000

Timo,

Could you please share a bit more detail? For instance:

1) The specific subdirectory or tree and the Makefile
2) The compiler you are using (DDE or GCC)?

I have a ton of projects and some of them with files in subdirectories, but the subdirectory structure always have this:

src
 |
 +- module 1
 |    |
 |    + c
 |    | |
 |    | +-> MyCFile
 |    |
 |    + h
 |      |
 |      +-> MyCFileHeader
 |
 +- module 2
 ...

Mon, 15 Dec 2025 21:07:11 +0000

I’m on Three Mobile and i loaded the site fine with my iPhone

You’re most likely on IPv4?

Mon, 15 Dec 2025 20:48:41 +0000

I’m on Three Mobile and i loaded the site fine with my iPhone