How to build Toolbox application using GCC?

Hello.
I am trying to create an app using toolbox. I make a new one based on MinApp toolbox example. Everything was compiled and working.
But now I want to use curl in my code. And it looks like the curl code could be compiled with gcc only. But I fail to compile the toolbox app with gcc.
I tried to change and add to Makefile these lines after include CApp line
CC = gcc
STDTOOLOPTIONS = -mlibscl -O3
ELF2AIF = elf2aif
C_NO_FNAMES =
C_WARNINGS =
it fails that it does not find the event.h file. I think i need to include eventlibs, wimp and toolbox somehow. but I cant find a way how to do it. Could anyone help? Is it really possible?
Or maybe i can compile with a curl with DDE compilers?

Thanks

I’m not sure if many people have experience of using Toolbox (only supplied with Acorn/Castle/ROOL C tools) and GCC (free).

You’d probably need to recompile the Toolbox supporting libraries with GCC maybe first?

Might be better to just use ordinary Templates files rather than Toolbox resources and OSLib (or DeskLib?) to do things there. That’d be a closer map to the ROOL programmers’ wiki pages on here (the online Programmers Reference Manuals) as OSlib is very close to the base SWIs. Steve F might also have some suggestions on this, as he wrote some excellent wimp-C-programming guides.

Ultimately, the difficulty you’ll have using Toolbox is that only a subset of the community use/understand Toolbox. Most others have older libraries that they use/are familiar with, and haven’t found a need for Toolbox’s more high-level facilities. Also, from personal experience, Toolbox only takes you so far, eventually you’ll be using the low-level SWIs to do something that Toolbox wasn’t envisioned for.

Also, for curl, there’s a command-line curl port which can be called from your code (eg. in the background as a taskwindow or something) which could help too.

Or, Rick M may be able to document how he’s used the OS-supplied http fetchers to download stuff for use with his Manga application? That’d avoid the need to hook in curl.

Further thought…

The toolbox is entirely SWI-based at heart, so the libraries that go with it are merely veneers to the modules. The source for those libraries may be in the C tools distribution, or if not, it’ll be in the RISC OS source tree (or should be). That should allow the libraries to be rebuilt with GCC.

If using with ported code, you may wish to use the more recent ELF shared-lib GCC stuff – GCCSDK and possibly cross-compiling. I’m fairly certain that curl already exists as a shared library and if you create a toolbox sharedlib, that would probably be rather elegant solution.

There is a toobox header in oslib (oslib/toolbox.h) so it might work, but I never tried.

Thanks for your answer.
Well my final goal is to create application with UI that will be able to send and receive data via http protocol. so I am looking for a way how it could be done.

unfortunately at the moment i can’t try to compile using GCCSDK from a linux machine as too much dependencies are not building and needs to fix it manually. So that is why i am trying to build from RISC OS machine. I could compile a code which incudes curl using gcc compiler but still was not successfull to build both curl + some ui example. at the moment i tried without success to build the Desklib examples with gcc, hovewer it seems to have an example code and make files for gcc compiler, it did not work for me.

where i can read about OS-supplied http fetchers? I cant find anything about it in PRMs

One more question.
why the DDE compiler can include files like event.h with success but gcc is not? Maybe it would be enough to tell to GCC somehow where they are? Or I am wrong?

Here is a example in using oslib with toolbox:
http://web.mit.edu/ghudson/dev/mangband/src/client/main-acn.c&sa=U&ved=2ahUKEwiqz-eS06PkAhWw-ioKHXEeAII4ChAWMAd6BAgIEAE&usg=AOvVaw37oUOVvSk8r_1AoXVEus74

Those headers are for DDE and not GCC (they are not compatible) I strongly recommend using OSLib.

If you want to use curl and other uninxy libs , use GCCSDK. I have a VirtualBox VM, that I build in. Just follow the build instructions (which also mentiones a compatible ubuntu version).

Don’t expect RISC OS to behave anything near some kind of linux!

An example of using the fetchers – but note that the program got messed up in the copy-paste, so note the corrections the follow.

https://www.riscosopen.org/forum/forums/4/topics/14691

The actual specs are in the “Docs” directory of the relevant sources. I really ought to write a blog article about this soon……..

Yes I have installed Ubuntu on VM and build GCCSDK. but i cant to build anything with autobuilder. it always cant patch sources because they are different at the moment and it is a big pain to patch all of them one by one. Thats is why I am trying to find a way how to build something with UI and http sending-receiving libs inside RISC OS.

Yes I have installed Ubuntu on VM and build GCCSDK. but i cant to build anything with autobuilder. it always cant patch sources because they are different at the moment and it is a big pain to patch all of them one by one.

The patches not applying is probably due to debian buster recently being released. If you edit the file ‘fetch-program’ and look for the line with distros=“stable oldstable” and change it to distros=“oldstable”.

If running linux from a VM the most compatible OS to use seems to be Ubuntu 16.0.4. Anything newer can cause problems building certain packages.

I am trying to create an app using toolbox. I make a new one based on MinApp toolbox example.

If you’re looking for a simple example toolbox wimp app I can make one available for download including an example makefile. It’s a JPEG viewer using the OS routines built with GCCSDK using the OSLib and OSLibSupport library. It’s just a case of building OSLIb using the GCCSDK autobuilder.

You can download jpegview including source and makefile here.

Well my final goal is to create application with UI that will be able to send and receive data via http protocol. so I am looking for a way how it could be done.

At this point I’ll just plug my (admittedly unfinished) HTTPLib, which wraps the system-wide HTTP modules and makes them more “C-like”.

EDIT: link http://www.update.uu.se/~micken/minapp_gcc.zip

Here we go , this build with GCCSDK, you just need to add OSLibSupport headers:
I did put res,Messages, Sprites in Obey$Dir
Built with following command:
../../gccsdk/cross/bin/arm-unknown-riscos-gcc minapp.c -I../../gccsdk/env/include/ 2>&1 -L../../gccsdk/env/lib -lOSLib32 -lOSLibSupport32 -o min

And ObeyFile:
Set MinApp$Dir <Obey$Dir>
Iconsprites <Obey$Dir>.!Sprites
*min

/**************************************************/
/*

• Minimal Toolbox application, using the event veneers library.
  */
  #include <unixlib/local.h>

#include
#include <oslib/wimp.h>
#include <oslib/toolbox.h>
#include <oslib/Event.h>
#include <oslib/Wimptypes.h>

#define Wimp_MQuit 0×0
#define Wimp_MPreQuit 0×8
#define WimpVersion 310
#define action_Quit 1
#define action_Iconbar 2
#define action_Save 3
#define action_New 4
#define action_OpenRecall 5
#define action_OpenChoice 6
#define action_OpenAngband 7
#define action_DefaultCols 8
#define action_SaveChoices 9
#define action_OpenMirror 10
static WimpPollBlock poll_block;
static toolbox_block id_block;
static messagetrans_control_block mfd;
/*

• Event handler to be called when toolbox event 1
• is generated (by click on the ‘Quit’ entry of
• the iconbar menu.
  */

int quit_event(int event_code, toolbox_o *id_block,void *handle)
{
event_code = event_code;
id_block = id_block;
handle = handle;

}

/*

• Message handler to be called on receipt of a
• Quit or PreQuit message from the Wimp.
  */

int quit_message(wimp_message *message,void *handle)
{
message = message;
handle = handle;

}

int main(void)
{
int toolbox_events = 0,
wimp_messages = 0,
event_code;

• register ourselves with the Toolbox.
  */

• initialise the event library.
  */

• register handler for toolbox event 1,
• which is generated by the ‘Quit’ option on the
• iconbar menu. Also register message handlers
• to quit properly when quit messages are
• received from the wimp.
  */

#if 1
const
static toolbox_ACTION_LIST(2) action_nos=
{
action_Quit,

#endif
toolbox_initialise ((toolbox_initialise_flags)0, WimpVersion, (wimp_message_list*)&messages, (toolbox_action_list*)&action_nos, “<MinApp$Dir>”,
(messagetrans_control_block*)&mfd, (toolbox_block*)&id_block, 0, 0);
event_register_toolbox_handler(-1,1,quit_event,0);
event_register_message_handler(Wimp_MQuit,quit_message,0);
event_register_message_handler(Wimp_MPreQuit,quit_message,0);

• poll loop
  */
  wimp_poll_flags mask;
  wimp_block block;
  wimp_event_no reason;
  int done;
  int oldmousex,oldmousey;
  while (TRUE) {

}
}

Thanks to everyone. I will try

Well it seems I have another problem now.
1. I have install new VM with Ubuntu 16.04
2. Install and compile GCCSDK
3. run gccsdk/autobuilder/build -v oslib
4. everything seems build
when i try to build minapp_gcc.zip it fails that oslib/Event.h not found. also oslib/Wimptypes.h not found. and these files are not exists really in gccsdk/env/include/oslib/.
from where they comes from? what did I miss?

unfortunately compiline jpegview sources also failed with error conflicting types for ‘_kernel_oserror’. it comes from Systypes.h and unixlib/local.h. so i removed last one and it was built. did not check yet if it will work or not.

so I am glad that something was built. but i cant compile libcurl3 now. dont have much luck for today.

Event and Wimptypes headers are in OSLibSupport.

Here we go , this build with GCCSDK, you just need to add OSLibSupport headers:

OSLibSupport is a separate package.

I tried the build on RISC OS and had to do this :-

#include <stdlib.h>
#include <oslib/wimp.h>
#include <oslib/toolbox.h>
#include "oslibsupport:h.Event"
#include "oslibsupport:h.Wimptypes"

gcc  minapp.c  -IOSLibSupport: -IOSLib:  -LOSLib:   -LOSLibSupport: -lOSLib32  -lOSLibSupport32 -o min

I have not tried with GCCSDK.

but i cant compile libcurl3 now. dont have much luck for today.

libcurl3 should build now if you try it again. Due to stable moving to old-stable the version it was trying to build no longer exists.

In GCCSDK , for me OSLib32 and OSLibSupport32 was built at gcc build time. I just added the support headers from the riscos package (renaming from h.file to file/h).

Just in case it is of interest, to get this to work in RISC OS :-

#include <stdlib.h>
#include <oslib/wimp.h>
#include <oslib/toolbox.h>
#include <oslibsupport/Event.h>
#include <oslibsupport/Wimptypes.h>

a slight reorganisation of OSLibSupport was required.

Add an oslibsupport directory and move the headers into it, that is move OSLibSupport.h to OSLibSupport.oslibsupport.h. To match the structure of OSLib.

a slight reorganisation of OSLibSupport was required

I’ve downloaded GCC, Make, .., OSLib, including OSLibSupport from Packman and, attempting to compile the example MinApp from minapp_gcc.zip Still, when I compile the code, as expected, I get an error Event library not found.

What are the default #include paths to Event.h and Wimptypes.h on RISC OS?

The answer above suggests that OSLibSupport package needs a restructure for it to work on RISC OS.

The answer above suggests that OSLibSupport package needs a restructure for it to work on RISC OS.

I do not think that is true. It works fine if the DDE is being used. The question is what paths have been set up to point to oslib and oslibsupport. Also check that there aren’t any other libraries that have similarly named files. I found it was necessary to make sure that the include paths and lib paths pointed unambiguously to the oslib/support files, and that the appropriate #includes in the source files had the correct path prefix. That was with the DDE. I have never used GCC in anger.

Cheers…

;) OSLibSupport works out of the box with the following:

#include <Event.h>
#include <Wimptypes.h>

So for path consistency you could also add the directory oslibsupport to the !OSLibSupp.elf-unixlib directory, copying in the associated h directory.

OSLibSupport works out of the box with the following:

You shouldn’t need to change anything. The correct paths are already set up depending on which setvars file is double clicked on.

Just needs the following include paths when compiling.

-IOSLibSupport: -IOSLib:

You shouldn’t need to change anything.

True. However, the example contains the following

#include <oslib/Event.h>
#include <oslib/Wimptypes.h>

Compiling on RISC OS with GCC

*gcc minapp.c  -IOSLibSupport: -IOSLib: -o min 
minapp.c:9:25: fatal error: oslib/Event.h: No such file or directory
compilation terminated.

To fix that you need

#include <Event.h>
#include <Wimptypes.h>