I think it would be different for other libraries, but realistically, how long has it been since the jpeg-6b code base has changed? 15 years? Sun had probably the most stringent packaging guidelines of anyone in the world, and yet we were able to convince their architectural review committee of the necessity of statically linking certain libraries with VirtualGL. The justification was different-- in the case of VirtualGL, we did so to avoid application interaction issues. But with TigerVNC, it's an easy sell to say that we're statically linking JPEG so we can get 2X better performance.
And again, I'm not proposing to eliminate the capability of linking with the system libjpeg. I'm just proposing that that not be the default. Instead of having a 'configure --with-included-jpeg' switch, have a 'configure --with-system-jpeg' switch. Pierre Ossman wrote: > The primary reasons are rather that they want a single library that > they have to keep track of for bug and security fixes. So the general > policy tends to be to avoid any bundled copies of general libraries. > > But I definitely agree that people should be using the optimised > version. I'm just saying that reality might be different once > distribution packaging guidelines enter the picture. > > Rgds > ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
