gnupic: Re: [gnupic] relocatable code libraries
Subject:
Re: [gnupic] relocatable code libraries
From:
Craig Franklin ####@####.####
Date:
30 Dec 2005 23:11:14 +0000
Message-Id: <43B5BF37.604@users.sourceforge.net>
There is a tool in gputils called gplib. It will archive many objects
into one file. That file can be added to the link list. The linker
will extract any files it needs to satisfy dependency. Only those files
will be included.
There are generic processor types that can be used to make the archive
generic for one family (p16cxx, p18cxx, ...). The linker will allow you
to link these generic families against code for specific devices
(p18f448). This is convenient, but there are some disadvantages to
doing it. For example, banksel has to generate code for switching both
bank bits even if the target device only uses 1. An optimization could
fix that, but I don't see it happening any time soon.
gplink has a default library path. It is reported in gplink help. The
default can be changed by using the GPUTILS_LIB_PATH variable. More
paths can be added using -I.
John De Villiers wrote:
>What is the best way to organise relocatable code?
>
>I dont want to sit with the situation where i have copies of the asm
>files all over the place for routine libraries that i have made. I
>becomes a real pain to hunt them all down to fix a problem that was
>detected in one of them.
>
>John
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
