konichiwa
11-01-2009, 11:20 PM
just wanted to let you guys know, i need to use libjpeg in a project and was having some problems, so i decided to plug in the clanlib precompiled static non-debug multi-threaded libjpeg from here:
http://clanlib.org/download-binaries-win32-vc80.html
http://clanlib.org/download/binaries-win32-vc90/all-2.0-external-libs-msvc90.zip
which helped a lot in solving my problem, because i knew the bug (probably) wasn't in the library.
BUT after solving the problem, i went back to the libjpeg i had been compiling in my own visual studio solution (2008), and was able to compare the performance. in my own compile of libjpeg, i turned on every optimization i could, including link-time optimization (whole program optimization), and the difference was huge, based on a rough measure: using the clanlib version, the program was taking up 30 percent of my CPU to decompress jpegs for use in an animation. using the optimized version i compiled myself, it was taking up 3 to 5 percent.
so ClanLib might want to check the optimizatioin settings you're using on your non-debug version of libjpeg.
http://clanlib.org/download-binaries-win32-vc80.html
http://clanlib.org/download/binaries-win32-vc90/all-2.0-external-libs-msvc90.zip
which helped a lot in solving my problem, because i knew the bug (probably) wasn't in the library.
BUT after solving the problem, i went back to the libjpeg i had been compiling in my own visual studio solution (2008), and was able to compare the performance. in my own compile of libjpeg, i turned on every optimization i could, including link-time optimization (whole program optimization), and the difference was huge, based on a rough measure: using the clanlib version, the program was taking up 30 percent of my CPU to decompress jpegs for use in an animation. using the optimized version i compiled myself, it was taking up 3 to 5 percent.
so ClanLib might want to check the optimizatioin settings you're using on your non-debug version of libjpeg.