On Mon, Aug 22, 2011 at 02:36:57PM +0200, Pierre Ossman wrote: > On Mon, 22 Aug 2011 07:08:21 -0500 > DRC <dcomman...@users.sourceforge.net> wrote: > > > Yuck! I am really averse to setting flags specific to building vnc.so > > when most people won't be building it. I'm not sure if I understand how > > the new system differs from the old in this respect. Didn't you have to > > specify --with-pic to get PIC code under autotools? Can't we do the > > same thing here and add a WITH_PIC CMake variable? > > > > AFAICT libtool used -fPIC by default for the convenience stuff (i.e. > noinst_*). I initially intended to add a knob for it, but I changed my > mind as PIC is basically harmless on x86_64 (AFAIK). In other words, > since the stuff I committed should do the right thing<tm> in every case > anyway, why would we need a setting for it?
Libtool builds to version automatically: One with -fPIC and one without. While linking, libtool selectes the correct version automatically. Regards, Martin Koegler ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
