ryan/mozjpeg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Since Windows doesn't use lazy loading, clarify that a Windows application that uses jpeg_mem_dest() or jpeg_mem_src() must use the DLL containing those functions at run time. Other wordsmithing

Browse Source 
git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@915 632fc199-4ca6-4c93-a231-07263d6284db
This commit is contained in:
DRC
2013-01-19 00:13:57 +00:00
parent 736fb06278
commit dc4645d422
1 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
README-turbo.txt
View File

@@ -376,9 +376,10 @@ jpeg_mem_dest() functions, even when not emulating the libjpeg v8 API/ABI.
Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8 Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8
API/ABI emulation in order to use the in-memory source/destination managers, API/ABI emulation in order to use the in-memory source/destination managers,
but several projects requested that those functions be included when emulating but several projects requested that those functions be included when emulating
the libjpeg v6b API/ABI as well. This allows the use of those functions the libjpeg v6b API/ABI as well. This allows the use of those functions by
without breaking backward ABI compatibility with libjpeg v6b, and it allows programs that need them without breaking ABI compatibility for programs that
those functions to be provided in the "official" libjpeg-turbo binaries. don't, and it allows those functions to be provided in the "official"
libjpeg-turbo binaries.
Those who are concerned about maintaining strict conformance with the libjpeg Those who are concerned about maintaining strict conformance with the libjpeg
v6b or v7 API can pass an argument of --without-mem-srcdst to configure or v6b or v7 API can pass an argument of --without-mem-srcdst to configure or
@@ -390,12 +391,14 @@ On Un*x systems, including the in-memory source/destination managers changes
the dynamic library version from 62.0.0 to 62.1.0 if using libjpeg v6b API/ABI the dynamic library version from 62.0.0 to 62.1.0 if using libjpeg v6b API/ABI
emulation and from 7.0.0 to 7.1.0 if using libjpeg v7 API/ABI emulation. emulation and from 7.0.0 to 7.1.0 if using libjpeg v7 API/ABI emulation.
Note that, on most operating systems, the dynamic linker will not look for Note that, on most Un*x systems, the dynamic linker will not look for a
a function in a library until that function is actually used. Thus, if a function in a library until that function is actually used. Thus, if a program
program is built against libjpeg-turbo 1.3+ and uses jpeg_mem_src() or is built against libjpeg-turbo 1.3+ and uses jpeg_mem_src() or jpeg_mem_dest(),
jpeg_mem_dest(), that program will not fail if run against an older version of that program will not fail if run against an older version of libjpeg-turbo or
libjpeg-turbo or against libjpeg v6b until the program actually tries to call against libjpeg v7- until the program actually tries to call jpeg_mem_src() or
jpeg_mem_src() or jpeg_mem_dest(). jpeg_mem_dest(). Such is not the case on Windows. If a program is built
against the libjpeg-turbo 1.3+ DLL and uses jpeg_mem_src() or jpeg_mem_dest(),
then it must use the libjpeg-turbo 1.3+ DLL at run time.
Both cjpeg and djpeg have been extended to allow testing the in-memory Both cjpeg and djpeg have been extended to allow testing the in-memory
source/destination manager functions. See their respective man pages for more source/destination manager functions. See their respective man pages for more