Struggling with vbcc

[Jherek Carnelia]

Firstly I am only used to using an IDE where I press a button and a file is created and I can run it. However now I'm on furlough I thought I'd try to set up a cross compiling environment.

I downloaded the binaries for using vbcc from the internet (Blitter studio) and followed the instructions for setting up the folders and environment etc using the same path as in the example.

I can create the obligatory Hello World! and I get a file that, when copied to WinUAE, works. So far so good.

Next I tried an example from the RKMs, but I can't create a file. It seems to be a linker issue, but as I don't really know what I'm doing, I don't know how to fix it!

This is a sample of the errors I get (I've removed a few because I guess that they are referring to the same issue):

c:\vbcc>vc -o simplegadget simplegadget.c

>{

warning 121 in line 70 of "simplegadget.c": return type of main is not int

\Users\Me\AppData\Local\Temp\vbcc068c.o: In "_main":

Error 21: \Users\Me\AppData\Local\Temp\vbcc068c.o (CODE+0xa): Reference to undefined symbol _OpenLibrary.

\Users\Me\AppData\Local\Temp\vbcc068c.o: In "l3":

Error 21: \Users\Me\AppData\Local\Temp\vbcc068c.o (CODE+0x22): Reference to undefined symbol _OpenLibrary.

\Users\Me\AppData\Local\Temp\vbcc068c.o: In "l6":

\Users\Me\AppData\Local\Temp\vbcc068c.o: In "l40":

Error 21: \Users\Me\AppData\Local\Temp\vbcc068c.o (CODE+0x29a): Reference to undefined symbol _GT_GetIMsg.

vlink -bamigahunk -x -Bstatic -Cvbcc -nostdlib "C:\vbcc/targets/m68k-amigaos/lib/startup.o" "C:\Users\Me\AppData\Local\Temp\vbcc068c.o"   -s -Rshort -L"C:\vbcc/targets/m68k-amigaos/lib/" -lvc -o simplegadget failed

If someone could point out where I'm going wrong, I would be grateful!

[Hedeon]

-lamiga

You need to link to the vbcc amiga library for amiga OS functions.

[Jherek Carnelia]

Ah okay, thank you!

Not sure how to do that though. Can you give me an example of the line/s I need to add to the vc.cfg file, please?

[Hedeon]

Most simple to test would be

c:\vbcc>vc -lamiga -o simplegadget simplegadget.c

if the library is in the same spot as the vc library (which is called with -lvc automatically through the config file).

[Jherek Carnelia]

Brilliant that worked a treat! Thank you for your help.

Just need to study the manuals now...

[phx]

Originally Posted by Hedeon

c:\vbcc>vc -lamiga -o simplegadget simplegadget.c

Note, that the position of the library on the command line matters. For example to override/replace functions from it. It is recommended to specify libraries last.

[Jherek Carnelia]

That's good to know. I'll do it that way from now on. Couldn't see where it said that in the manual?

[phx]

Sorry. Forget what I said! It only matters when you call vlink directly.
When using the vc frontend it makes sure that -l libraries appear after the object files for the vlink-call. But it's a good habit nevertheless.