Bug#329762: Relaxation and documentation of the "-fPIC" constraint
Hi,
On Mon, Oct 03, 2005, Adeodato Simó wrote:
> Then, I'd say it should be mentioned that such libraries are expected
> (must?) be named like this: libfoo_pic.a.
I removed the explicit interdiction of using -fPIC with static libs
because I thought this had nothing to do in policy. I don't think we
should write things such as "your library MUST be named like this".
What you want to say with "libraries are expected to be named like
this" is that "it's currently best to name them like this", it's the
recommended way, it's correct style to name them like that.
And again, I think this ought to be in the developers reference, or the
library packaging guide, or what ever best practices and
recommendations guide is fit.
But heh, it's only me.
--
Loïc Minier <lool@dooz.org>
Reply to: