Marcin Owsiany <[EMAIL PROTECTED]> immo vero scripsit:
> I read somewhere that code compiled with -fPIC is a little larger and
> slower. Is this the only reson for that policy requirement? If not,
> please give me for some information/pointers on that requirement.
I think that is mostly so.
Without -fPIC shared libraries will have problems,
with -fPIC, code gets larger, and slower.
I would convince upstream to use libtool.
Besides, adding rules to build different objects is trivial.
Call the library objects .lo, and add rules to :
sources=whatever.c somethingelse.c other.c
libtarget.whatever.so: ${sources:.c=.lo}
libtarget.a: ${sources:.c=.o}
%.lo: %.c
gcc -fPIC ......
%.o: %.c
gcc ....
regards,
junichi
--
[EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
