Compiling shared libraries

[Karlos]

Hi all,

I'm working on some normal amiga '.library' files from (virtually pure) C. Now, for historical reasons beyond my control I am forced to use storm, at least for some of it...

Unfortunately storm has its gripes and what seems to be an intractable bug in the code generator has waylaid me. I am still seeing exactly what is wrong there but it doesnt look like its the code (having tested that part in another compiler).

Now, can the bulk of the library - as defined as those functions not part of the fd - be compiled in another compiler (I am thinking vbcc uses same object format IIRC) and then linked with stormc ?

Anybody tried this?

On the same note, I need to compile a WarpOS PPC version of the same library but don't have StormC PPC. Assuming that the code could be compiled in vbcc-wos, again, any chance of getting stormlink to make a .library from it?

Cheers,

K

[ncafferkey]

Karlos wrote:

Now, can the bulk of the library - as defined as those functions not part of the fd - be compiled in another compiler (I am thinking vbcc uses same object format IIRC) and then linked with stormc ?

Anybody tried this?

It should work, but I haven't tried it.

On the same note, I need to compile a WarpOS PPC version of the same library but don't have StormC PPC. Assuming that the code could be compiled in vbcc-wos, again, any chance of getting stormlink to make a .library from it?

Sorry, I don't know.

[Phx_]

Yes, vbcc uses the same object file format, which all Amiga compilers do (besides gcc).

Why do you need to link with StormLink at all? Have you tried to compile and link everything with vbcc?

To answer your question: Yes, although StormC is using other module and section names than vbcc it might be possible to link them together, although I didn't try it.

[Karlos]

Well, object formats aside, the last time I checked, vbcc couldn't directly create shared libraries and neither could gcc (unless you write the library header stuff yourself by hand).

-edit-

I appreciate this info may be out of date. Feel free to correct me here :-)

-/edit-

OTOH, storm c can create shared libraries fairly easily, just add the fd file and tell it to link as a shared library.

Anyhow, thanks for the replies :-)

[itix]

Creating shared libraries is fairly simple. There are quite many
comprehensive  examples available...

[Karlos]

@itix

Well, I was hoping for idiot proof simplicity and convenience, but creating the library by hand isn't likely to hurt me too much.

What about warpos ppc native shared libraries? Any good examples out there?

[RobinC]

I've only compiled them in gcc, but as stormc is using a slightly altered version of that for it's compiler - try grabbing one of my amirc plugins from aminet (the source archives obviously) and seeing if you can get that to compile ok - they have all needed non-system includes, and use SDI_compiler.h etc.

The order of files for compiling (and linking) is libinit.c then xxx.c,  with no start code. If it works, just rip out whatever you need... ;-)

Robin

ps. to find them just search for "amirc plugin" on aminet...

[Karlos]

Cheers, I will give that a bash later :-)

I actually got around the stupid bug that was the cause of my main gripe so I can use storm ok now. However, its just one of e depressingly long list of storm c v3 codegenerator problems (admittedly the first non C++ one I encountered)...