On Mon, Dec 27, 1999 at 02:41:59PM +0100, Niels M�ller wrote:
> I thought that libargp.a was not used until at the final linking, say
>
> gcc -g -O2 -ggdb3 -Wall -W -Wmissing-prototypes
> -Wmissing-declarations -Wstrict-prototypes -Waggregate-return
> -Wpointer-arith -Wbad-function-cast -Wnested-externs -o lsh lsh.o
> liblsh.a symmetric/libsymmetric.a memxor.o argp/libargp.a -lutil
> -lnsl -lcrypt -lz -lgmp
>
> But apprearantly I changed that some time ago. I don't know what is
> the best way to handle this; should object files that are needed on
> some platforms but not others be included in liblsh.a, or linked into
> the executables later?
I was originally going to say that they should be keep separate, but
upon rethinking, the liblsh library is useless without them, so perhaps
they should be linked in?
It's only really an issue if it's planned to use liblsh for purposes
other than the building of the rest of lsh - if it was to be installed
as a system shared library, for example.
J.
--
+----------------------------------------------+-----------------------+
| Oxford University Computer Society President | Ye Gods, I have feet? |
| Tel/Fax: +44-28-30252654/+44-28-30250834 | |
+----------------------------------------------+-----------------------+
