| From: | Colin Wenzel |
| Date: | 09 Jul 2000 at 15:32:34 |
| Subject: | Re: Linker libraries |
On 10-Jul-00, Andrew Markwell wrote:
>> From: Colin Wenzel <colstv@hotkey.net.au>
>>
>> If you are using Aztec-C I would just tell you to look in the
>> bin drawer for an executable called "lb" it is the librarian.
>> But since I don't know what system you are using,
>> I can't give more specific advice than what I have....
>>
>> This setup may be applicable to other environments too
>> so I will elaborate incase it can be usefull...
>>
>> Compile the source as usual with:
>> usage: *cc path:sourcefile.c*
>>
>> That generates the .o file, then use the librarian.
>>
>> usage: * lb path:libname.lib -v -a+ path:objectfile.o*
>>
>> That will add that particular object module to the library.
>> Be carefull what order you put them in, incase one function calls
>> another one in the same library...
>>
>> The lowest level functions, go in last.
>>
>>
> I am using the featureless and manual-less HiSoft C++ so I have no
> "lb" tool. Although it does generate #?.o files (woopee) so I'll look
> on Aminet and see if there is some tool that'll do it.
> Andrew Markwell
My particular LB is designed for my linker & I believe it is
also compatible with the lattice compiler system linker,
so if you want to try it, I can send you (privately) my LB &
a sample script & options doc for you to try & see if your
particular linker likes it... ??
Regards
Colin Wenzel. Australia.
EMAIL: colstv@hotkey.net.au
URL: http://www.hotkey.net.au/~colstv/
ICQ: 17608330
AMIGA: 4000T, 68060/50, 150Mb RAM,
OS 3.5, Spectrum Gfx Card.
_________________________________________
------------------------------------------------------------------------
Best friends, most artistic, class clown Find 'em here:
http://click.egroups.com/1/5533/1/_/451227/_/963153227/
------------------------------------------------------------------------