How to build Toolbox application using GCC?

Andrew McCarthy is correct, if you specify:

-IOSLibSupport: -IOSLib:

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

CurlLib works fine compiling it with GCC on RISCOS I started a client code to connect to JF-on-line-patches work some times ago and it uses curl and json.c to talk to the service, then I have left it unfinished ’cause I focused on other stuff… but the tests were all working fine.

Andrew McCarthy is correct

;-) Almost.

-IOSLibSupport: -IOSLib:

Results in

... collect2: error: ld returned 1 exit status

The following compiles

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

Questions:

• How do you configure StrongEd so that it opens a TaskWindow of 1600K on hitting F10 in C mode?
• What process would a RISC OS programming veteran follow to resolve GCC being unable to find a library file? (How do you check what paths have been set-up?)

How do you check what paths have been set-up?)

You can check what they have been set to with e.g.,

filer_opendir OSLib:

or

show *OSLib*

How do you check what paths have been set-up?

I imagine *show OSLib* would show the paths.
Personally I avoid all the clutter, and put actual libraries in
!GCC.arm-unknown-riscos.lib
and then link with -lOSlib32Hard or -lOSLib32Soft
Still need your subdirectories in !GCC.arm-unknown-riscos.include
for headers though.
#include <oslib/whatever.h>
Also works when linking to SharedLibs libraries.

How do you configure StrongEd so that it opens a TaskWindow of 1600K on hitting F10 in C mode?

You’ll need to edit the ModeFile for C mode. To open the ModeFile click with the right mouse button on StrongED’s iconbar icon. In the menu that opens, click with Shift held down on the ‘C’ entry to load the ModeFile.

In the ModeFile locate the ‘Functions’ section, near the end of the file. Within the ‘Functions’ section find the ‘Key’ line for F10. The line below that defines what a ‘Select’ (left mouse button) click on the associated toolbar icon does. It’s also the action carried out when F10 is pressed.

You can change the action(s) tied to the ‘Select’ line to suit your needs. It can be a simple command to open a TaskWindow but it could also run a specific (make) file. The ‘Select’ and ‘Adjust’ lines present in the ModeFile should give you some idea of what’s possible.

The ‘Run’ function takes a single string as parameter and executes that as a *command so if you know the *command required, binding to F10 should be easy. If you want the current file to be saved first use the ‘SaveRun’ function.

When done, click with right mouse button on the ‘Save’ icon on the toolbar. If asked where to save, click on ‘Save to UserPrefs’. Now open a text in C mode and check if pressing F10 has the desired effect. If not, edit the ModeFile some more then save and check again.

Hopefully this is clear enough but if you have further questions just ask.

How do you configure StrongEd so that it opens a TaskWindow of 1600K on hitting F10 in C mode?

StrongED mode configuration file has pre-defined 8000K wimpslot for GCC which is good for the old gcc, but you can change that value to 16000. However I personally prefer to write a TaskObey file and double click on it to kick start a compilation and use Makefiles to control gcc and or other compilers/linkers and every aspect of the building process…

What process would a RISC OS programming veteran follow to resolve GCC being unable to find a library file? (How do you check what paths have been set-up?)

I do not define myself a veteran… however you can check if specific system variables have been defined in an Obey script and if not rise an error. for instance:

If OSLib$Path = "" THEN Error OSLib not see by the filer! Hey dude get this sorted first please!

Problem is that Obey doesn’t really work as some may expect and so if the variable above is set everything goes well, but if it’s not set then Obey will throw an Unknown Operand error…

Some may want to use some logic there and put the variable between "" (that’s the bash way for example), but in that case Obey will interpret the variable name as a literal value…

So the best way I know is to use BBC BASIC as your build management or Lua, for instance create some BBC BASIC checking code you run from your TaskObey:

DIM buff%255

checkvar$="OSLib$Path"

SYS"OS_ReadVarVal",checkvar$,buff%,255,0,3 TO ,,bytes%,type%

buff%?bytes%=13
result$=$buff%

REM Finally let's do what we want to do!
IF result$ = "" THEN *Error Ouch OSLib has NOT been seen by the filer, we are all gonna die!!!!

REM and you can also add after
*IfThere OSLib:h THEN Error OSLib has been seen by the filer, but it appears empty... did you eat the content?

Hope this helps

You need

If “<OSLib$Path>” = "" THEN …

[Edited for single equals in case it’s stumbled on out of context]

If you would use GCC and TBX you can compile and link under RISC OS e.g. for the provided sample toolbox APP !Graphics

g++ -o ^.!RunImage a.libtbx cc.main cc.GraphicsWnd cc.SaveAsSprite

@ Stuart

You need If “<OSLib$Path>” == "" THEN …

That kinda work, should be:

If "<OSLib$Path>" = "" THEN

Obey wants a single “=” not a double “==”, but yes in that specific case it can help, however I have long abandoned to use Obey for this, given the limited scope of the < > syntax. It would be cool if the < > worked in more cases thought.

Excellent. Thank you for all the tips and replies.

My learning C “The Hard Way” and Toolbox journey has led me to this point.

Toolbox: Menu → Quit, utilises QUIT_QUIT (&82a91). OSLib provides the following function
event_register_toolbox_handler()

What, as an easy to understand, minimal set of parameters can I use to enable quit on my app using the Toolbox aspects of OSLib?

I recognise that I need a handler function, but I’m struggling with what the bare minimum is, in terms of values for the function event_register_toolbox_hander()?

Context. I’m utilising GCC ©, OSLib, OSLibSupport and I have created a bare bones !App which puts an Icon on the IconBar.

There’s a couple of example apps with source in this topic.

https://www.riscosopen.org/forum/forums/5/topics/14713#posts-94420

The values you need are

event_register_toolbox_handler(-1, action_QUIT_QUIT, your_event_handler, NULL);

The minus one means you don’t care what object the event comes from (you can use the constant event_ANY from Event.h for that).

The handler will be

int your_event_handler(int event_code, ToolboxEvent *event, IdBlock *id_block, void *handle)

Please don’t forget to put the action_QUIT_QUIT in the list of actions you pass to toolbox_initialise.

Happy New Year and thank you. I managed to implement QUIT! Thanks also for the referenced examples. Yay! progress… :)