Iff.library and gcc

[watertonian]

Hello all. Trying to write a video game, and I'm using gcc to compile it. I can open the screen, but I can't get the title pic to show. (320x200x32 Iff pic done in Deluxe Paint) I have the header for iff.library, but none of the commands link. I think the problem is with the sas/C header style, but I'm not sure. Anybody else have this problem?

[thomas]

You can create all kinds of header files with fd2pragma. For GCC you need inline/iff.h IIRC.

http://aminet.net/package/dev/misc/fd2pragma
the latest version comes with VBCC: http://sun.hasenbraten.de/vbcc/

[watertonian]

Ah, thanks. Will try when done with my after work nap.

[watertonian]

OK, gave up on gcc, and went with vbcc. (gcc doesn't like to put stuff into chip ram for some reason, kind of essential when dealing with bitmaps..) got everything gfx-wise to work, now just have to figure out how to parse joystick input. Along with drawing some better graphics.

[desiv]

Seems like a good thread to poke at for this..
Just going with vbcc..

I'm going to want to poke around with iff.library, but not sure what I need to do to add it..

I tried just copying the iff.h file to /opt/m68k-amigaos/os-include/libraries/ and then compiling the test app (EasyExample.c) and got some errors.
(Didn't really expect it to work just like that, but.. ;-)

-------------

villdesi@dbv-lnx-vm:~/amigaos$ vc -o EasyExample EasyExample.c
>struct Library *IntuitionBase,
warning 68 in line 34 of "EasyExample.c": redeclaration of var <IntuitionBase> with new type
>{
warning 121 in line 133 of "EasyExample.c": return type of main is not int
fileiOdhbV.o: In "_DisplayILBM":
Error 21: fileiOdhbV.o (CODE+0x136): Reference to undefined symbol _IFFL_OpenIFF.
Error 21: fileiOdhbV.o (CODE+0x148): Reference to undefined symbol _IFFL_GetBMHD.
Error 21: fileiOdhbV.o (CODE+0x1ba): Reference to undefined symbol _IFFL_GetViewModes.
Error 21: fileiOdhbV.o (CODE+0x1ea): Reference to undefined symbol _IFFL_GetColorTab.
fileiOdhbV.o: In "l29":
Error 21: fileiOdhbV.o (CODE+0x224): Reference to undefined symbol _IFFL_DecodePic.
fileiOdhbV.o: In "l37":
Error 21: fileiOdhbV.o (CODE+0x288): Reference to undefined symbol _IFFL_CloseIFF.
fileiOdhbV.o: In "l46":
Error 21: fileiOdhbV.o (CODE+0x3c6): Reference to undefined symbol _IFFL_IFFError.
vlink -bamigahunk -x -Bstatic -Cvbcc -nostdlib /opt/m68k-amigaos/vbcc-lib/startup13.o "/tmp/fileiOdhbV.o" -s -L/opt/m68k-amigaos/vbcc-lib -L/opt/m68k-amigaos/vbcc-include -lvc -lamiga -o EasyExample failed

--------------

Any pointers on where I should start looking?

Thanx!

desiv

[Samurai_Crow]

Sounds like you need to link something.

[desiv]

Originally Posted by Samurai_Crow

Sounds like you need to link something.

Hmm..
That sounds familiar (it has been 20+ years!!! :-)...
There's a makefile in the iff.library examples directory, so I'll take a look..

Thanx

Probably going to have to dig deeper into vbcc..
I can't see any command line options for vc (vc --help and vc /? don't do anything)...

As for the iff.library, I don't see any .o files in the archive to link. There is of course, the iff.library, which goes with the program (i.e. not linked). There is also a file called iff.lib, but for now, I'm not sure what to do with it...
Looked at the makefile, but didn't see anything obvious. It does mention something called lcr.lib, but I'm not sure how that would help the error I'm seeing... (Then again, I don't know) And I don't see an lcr.lib file around...
(Oh, I think the lcr.lib is something that would be used if I were using lattice C)

Long day anyway, maybe it'll make more sense after I read some docs.. ;-)

desiv

[thomas]

Same reply as above: you need to create proper proto and inline header files with fd2pragma. For vbcc the inline file is called iff_protos.h. Check the options section of vbcc:doc/fd2pragma.guide.

In your program always #include <proto/iff.h> rather than <clib/iff_protos.h>. And never include <pragmas/iff.h>, it has no meaning for vbcc.

[matthey]

Originally Posted by desiv

Hmm..
Probably going to have to dig deeper into vbcc..
I can't see any command line options for vc (vc --help and vc /? don't do anything)...

The vbcc docs are at the following link and they are useful.

http://server.owl.de/~frank/vbcc/docs/vbcc.pdf

The vc utility is fairly minimal currently.