MManager in PlingSystem

In PlingSystem.zip !Boot.310.Modules.MManager is v0.17, which is not the latest version of MBuf Manager. Is there a reason for it being an old version?

On a related note, is the source for MManager and Internet available? Appreciate they are probably closed source, but if someone has signed the NDA and has the source, perhaps they could help me create revised versions for RISCOS 3.20

MManager is v0.17

Are there other versions available (in 350 etc?)? If so, maybe that one is the last known to be specifically 3.10 compatible?

is the source for […] Internet available?

https://gitlab.riscosopen.org/RiscOS/Sources/Networking/AUN/Internet

Thanks. Of course I can’t get it to compile.

It wants Global/services.h which I can’t find in my copy of DDE or in the OS source tree (via search in Git at least.) Any idea where I can find that.

Do you have a working installation of the build environment for RISC OS?

If you set up to build the Pi version (probably others too), it’ll be in:

…BCM2835Dev.Export.APCS-32.Hdr.Global

via search in Git at least

Personally, the Git pisses me off because it’s so detached from the underlying directory layout that it can be a nightmare to try to find where stuff actually is.

It’s here in the older CVS:
https://www.riscosopen.org/viewer/view/apache/RiscOS/Sources/Programmer/HdrSrc/hdr/Services

Which means it’s probably lurking in the programmer resources in Git. I’d give you a link, but I’m using Netsurf… :-/

Personally, the Git pisses me off because it’s so detached from the underlying directory layout that it can be a nightmare to try to find where stuff actually is.

So for anyone not wanting bleeding edge source the route is probably to follow the instructions regarding fetching source for ROM builds – pull the appropriate tarball and search that.
There’s probably some fancy git instruction sequence to pull the source for a specific retro version.

So on my harddisc I have

ADFS::HardDisc.$.Projects.RISCOSOpen.RiscOS.Sources.Programmer.HdrSrc

which in CVS would be at

https://www.riscosopen.org/viewer/view/apache/RiscOS/Sources/Programmer/HdrSrc

but somehow you’re struggling to find

https://gitlab.riscosopen.org/RiscOS/Sources/Programmer/HdrSrc

despite it being both shorter and mapping 1:1 to where it is in the source tree? GitLab’s user interface choices are boggling at the best of times, but you can avoid most of it by just typing the path in per this illustration (translating dots for slashes).

Do you have a working installation of the build environment for RISC OS?

That’s what I’m struggling with. I’ve:

1. Downloaded the Git tree (which I did manually. Downloading via Git redirects to a login page and fails)
2. Run Library.InstallTools
3. Run Env.ROOL.PlingSystem
4. Run Sources.Networking.AUN.Internet.build.!MkRom

Which results in the error #include file “Global/Services.h” wouldn’t open

Have you run !Builder and set the environment?

I can’t help with Git, the times I get the source, I download one of the tarballs.

Have you run !Builder and set the environment?

No, I ran it manually in step 3 as I’m only trying to build one Module.

If I let DDE set the paths it finds DDE’s version of services.h, but it doesn’t compile. The build instructions do say not lot let DDE set the paths, so I guess !Common or PlingSystem isn’t setting the Global h folder path – or its set by something else when doing a full build? I’ll be honest, I don’t really understand how it maps DOS paths to Acorn paths and am not sure where or how to add the path in !Common.

Are Global/? paths treated specially, as it clearly doesn’t redirect to a Global subfolder?

Are there other versions available (in 350 etc?)? If so, maybe that one is the last known to be specifically 3.10 compatible?

There might possibly be newer versions in 350 etc I didn’t look if I’m honest. My point is, there’s a old copy in the 310 folder.

I’m also assuming MBuf Manager is closed source?

My point is, there’s a old copy in the 310 folder.

Does the newer one work on 3.10? If not, then what you describe isn’t impossible. The system looks in the numbered directories in reverse order, starting with the first one applicable to your OS.

I’m also assuming MBuf Manager is closed source?

Yup. It and Resolver are the two NDA’d bits.

You need to use !Builder. A lot of components have dependencies which won’t get built automatically when you run their !Mk scripts; so you either need to manually build those dependencies, or just ask builder to build all the possible dependencies for you.

1. Downloaded the Git tree in whatever way works for you
2. Run Library.InstallTools
3. Run !Builder
4. Register the PlingSystem folder as a build directory
5. In Builder’s main window, select the PlingSystem environment
6. Tick “export headers” and “export libraries”
7. Click Build
8. Once that’s done, run Sources.Networking.AUN.Internet.build.!MkRom

The “export headers” build phase, as its name implies, asks each component to export any headers which other components might rely upon (like Global/Services.h). “Export libraries” asks each component to build & export any libraries which other components might rely upon (which also includes the shared C library headers & stubs). All of these exports end up in the “Exports” folder.

Also note that because Internet is a C module, !MkRom will output a relocatable, partially-linked AOF file rather than a standard module. The build system then runs link -o Internet -rmf -base XXX aof.Internet RISC_OSLib:o.c_abssym in order to generate the final module (with XXX replaced with the address of the module in ROM, and c_abssym being a text file listing the addresses of all of the ROM CLib exported symbols).

I’m also assuming MBuf Manager is closed source?

Yup. It and Resolver are the two NDA’d bits.

And ShareFS, although a few months ago Andrew did mention that ROD have gained permission from all the original guys for the release of ShareFS etc sources. So there’s the possibility that the “etc” refers to MManager & Resolver, since I think they may have all been tied up together.

Thanks Jeffrey, I’ll give that a try. The information on the way the linker works is very useful.