Re: [Libjpeg-turbo-devel] Enabling the in-memory source/destination managers in libjpeg-turbo's def
SIMD-accelerated libjpeg-compatible JPEG codec library
Brought to you by:
dcommander
From: DRC <dco...@us...> - 2013-01-17 10:11:54
|
On 1/16/13 9:04 AM, Adam Tkac wrote: > since libjpeg-turbo uses libtool, it should be fairly simple on UN*X systems: > > http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html > > When you only add new interface, you should perform steps 3., 4. and 5. > > So the "-version-info" parameter in Makefile.am will be "-version-info 63:0:1" > and the output library will be libjpeg.so.62.1.0. However you are right that > application which uses mem_* functions will fail due to unresolved symbols when you > run it with old libjpeg.so.62.0.0. > > I'm not sure about Windows but I think you don't have to change anything, just > add new functions. OK, that's easy enough. Follow-up Q: How best to handle the version script? (libjpeg.map.in) Does it really matter if these new symbols are also under the version node LIBJPEG_6.2? Or should they be moved into the LIBJPEGTURBO_6.2 node? |