Add FPDFAPIJPEG_ prefix to more libjpeg functions

Add FPDFAPIJPEG_ prefix to more libjpeg functions

Original patch by Evangelos Foutras.

Chromium built with use_system_libjpeg=1 can mistakenly try to use
symbols exported by the libjpeg library that's bundled with pdfium.

These name conflicts result in failure to encode the contents of a
canvas element using toDataURL('image/jpeg').

BUG=505226
R=tsepez@chromium.org

Committed: https://pdfium.googlesource.com/pdfium/+/1b5084321ed924ad3fcc437c3effc81baafd18ac

[Evangelos Foutras, 2015-10-19 09:33:42]

evangelos@foutrelis.com changed reviewers:
+ thestig@chromium.org, tsepez@chromium.org

[Evangelos Foutras, 2015-10-19 10:02:28]

While I'm not 100% sure this is the correct fix, it seems like a reasonable
change and it corrects the "toDataURL('image/jpeg')" Chromium issue in my
testing.

[Tom Sepez, 2015-10-19 16:16:08]

On 2015/10/19 10:02:28, foutrelis wrote:
> While I'm not 100% sure this is the correct fix, it seems like a reasonable
> change and it corrects the "toDataURL('image/jpeg')" Chromium issue in my
> testing.
Thanks for tracking down the missing prefixes.  Given the current approach, this
does seem reasonable.  LGTM.
[As a follow-up, I need to kill off the duplicate copies of jpeglib.h.]
Before I land this, I have to ask, Have you signed the (chromium) contributor
agreement?

[Evangelos Foutras, 2015-10-19 17:59:39]

On 2015/10/19 16:16:08, Tom Sepez wrote:
> Thanks for tracking down the missing prefixes.  Given the current approach,
this
> does seem reasonable.  LGTM.
> [As a follow-up, I need to kill off the duplicate copies of jpeglib.h.]

Thanks for the review.

> Before I land this, I have to ask, Have you signed the (chromium) contributor
> agreement?

Yes, I have signed the agreement (and have made two other minor contributions to
Chromium).

Cheers!

[Tom Sepez, 2015-10-19 18:47:14]

Description was changed from

==========
Add FPDFAPIJPEG_ prefix to more libjpeg functions

Chromium built with use_system_libjpeg=1 can mistakenly try to use
symbols exported by the libjpeg library that's bundled with pdfium.

These name conflicts result in failure to encode the contents of a
canvas element using toDataURL('image/jpeg').

BUG=505226
==========

to

==========
Add FPDFAPIJPEG_ prefix to more libjpeg functions

Original patch by Foutrelis.

Chromium built with use_system_libjpeg=1 can mistakenly try to use
symbols exported by the libjpeg library that's bundled with pdfium.

These name conflicts result in failure to encode the contents of a
canvas element using toDataURL('image/jpeg').

BUG=505226
==========

[Tom Sepez, 2015-10-19 18:48:18]

Description was changed from

==========
Add FPDFAPIJPEG_ prefix to more libjpeg functions

Original patch by Foutrelis.

Chromium built with use_system_libjpeg=1 can mistakenly try to use
symbols exported by the libjpeg library that's bundled with pdfium.

These name conflicts result in failure to encode the contents of a
canvas element using toDataURL('image/jpeg').

BUG=505226
==========

to

==========
Add FPDFAPIJPEG_ prefix to more libjpeg functions

Original patch by Evangelos Foutras.

Chromium built with use_system_libjpeg=1 can mistakenly try to use
symbols exported by the libjpeg library that's bundled with pdfium.

These name conflicts result in failure to encode the contents of a
canvas element using toDataURL('image/jpeg').

BUG=505226
==========

[Tom Sepez, 2015-10-19 18:50:00]

Committed patchset #1 (id:1) manually as
1b5084321ed924ad3fcc437c3effc81baafd18ac (presubmit successful).