Currently chromium compiles and uses its own libjpeg. There is a typedef type "boolean" which defaults to unsigned char. On linux we've run into a problem with this because GTK is also compiled against libjpeg, but expects boolean to be int. GTK ends up using our libjpeg, and that causes problems. The possible solutions include
a) using the system libjpeg (at least on linux, if not the other platforms as well) b) compiling our libjpeg with boolean = int (at least on linux) c) packaging our own version of gtk along with chrome (ha ha ha ha) d) somehow use the system libjpeg for gtk, and our libjpeg for chrome Of course our code that uses libjpeg directly (jpec_codec.cc) will only work with one or the other, which I guess is why we package libjpeg with chrome in the first place. Dan Kegel asserts that (a) is the correct solution, and cites the LSB as defining boolean = int: <http://refspecs.linux-foundation.org/LSB_3.1.0/LSB-Desktop-generic/LSB-Desktop-generic/libjpeg-ddefs.html>. Any objections to doing this? Additionally, any build system oriented folk want to assist with making this switch? -- Evan Stade --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
