C Module include problem

Hello guys,

I am making a riscos c module build around the skeleton module ‘examplemod’.
The example module builds just fine but i want to include the file services.h for the service call names.

I can’t figure out how to include it as i always get the error: ‘Serious error: #include file “services.h” wouldn’t open’.
I have tried many different ways to include it(“services.h”, “global/services.h”).

Can any one please help me on how to include this and the other files in the folder “Export.APCS-32.C.Global.h”?

Thanks

You do not say which C compiler you are using. I suspect that the answer may depend on which.

"global/services.h"

should just work – it does for me and I haven’t made a change to the makefile to make it work.

Colin, I’m guessing you are using GCC?

For the DDE, I can get it to work with:

#include "<CExport$Dir>.Global.h.Services"

I can’t help but think there ought to be a simpler way, but looking at the system variables, I can’t see anything else pointing to that location…

Nope I’m using the latest DDE

Thanks for the quick replies.

I use the c compiler supplied with NutPi, DDE version 25.

If i include “global/services.h” it gives the same error: ‘Serious error: #include file “global/services.h” wouldn’t open’.

I can however include any of the library’s, for example RISC_OSLib and then use os.h.

OMG…

AMU: Don’t know how to make ‘LocalRes:Messages’
cc -zM -zps1 -c -depend !Depend -fah -gflv -o od.examplemod c.examplemod
Norcroft RISC OS ARM C vsn 5.71 [25 Aug 2014]
cc -zM -zps1 -c -depend !Depend -ff -fah -o o.examplemod c.examplemod
Norcroft RISC OS ARM C vsn 5.71 [25 Aug 2014]
AMU: Don’t know how to make ‘RISCOSLIB:o.romcstubs’

What did I do? I pressed Ctrl-Shift-C from !Zap which starts the build process by running the MakeFile.
Anything more complicated will make the user’s life more complicated.

How to build the module correctly? Double-click on the MkRAM file.
Oh how quaint. Find something and run it, and thus destroy useful functionality in any editor worthy of use.

<sigh>

It turns out it’s because if you compile after AcornC/C++.!SetPaths has been seen ‘Export.APCS-32.C.’ is not in C$Path but if you use !builder to set C$path – like I do – then it is included in C$path and “global/services.h” works.

So either add it to C$path – would be nice if ROOL did this – or if you use !builder use that.

Colin what do you mean with !builder? I see -builder !Builder in the parameters of cc so i guess i already use it?

Let me try to set add Export.APCS-32.C to the path anyway.

Forget about !builder – you’d know if you used it.

Oh how quaint. Find something and run it, and thus destroy useful functionality in any editor worthy of use.

Most impressed that your editor knows which flags you want to call makefile with.

Oke i will forget about it than :).
I added CExport$Dir to C$Path in !SetPaths.SetPaths and that fixed it.

Thanks for the help.

AMU: Don’t know how to make ‘LocalRes:Messages’

Ah, the joy of not having a < SourceDirectory >.Resources.UK.Messages file or a line in the Makefile that reads RES_OBJ ="" or indeed points to wherever the Messages file lives.

Me, novice, run builder to setup everything that needs to be used¹ then either do a quirky command line with interesting syntax or run the !MkRAM file (or modified clone of same for slightly altered syntax)
Then twiddle with bits in the makefile if required and maybe the source.

¹ Mostly because then I can use build setups that are rather like stuff in the ROM/HardDisc builds and I don’t have to learn the quirks of the sytem while trying to learn the programming.