Age | Commit message (Collapse) | Author |
|
This CL moves the conditionals inside the target_defaults configuration. This
causes the -fPIC to get picked up and allows component=shared_library to build
correctly.
BUG=pdfium:218
R=thestig@chromium.org
Review URL: https://codereview.chromium.org/1407903002 .
|
|
R=thakis@chromium.org, tsepez@chromium.org
Review URL: https://codereview.chromium.org/1330173002 .
|
|
R=vogelheim@chromium.org
BUG=
Review URL: https://codereview.chromium.org/1146933002
|
|
Code might someday be made clean for -Wmissing-field-initializers
and -Wsign-compare, but for now this produces too much noise to be
useful.
The -Wmissing-field-initializers warning is misguided in a high
percentage of cases, and actually leads to bad fixes.
R=brucedawson@chromium.org
Review URL: https://codereview.chromium.org/1094713002
|
|
This change disables several warnings that fire frequently
in pdfium and are not practical to fix at this time.
R=tsepez@chromium.org
BUG=440500
Review URL: https://codereview.chromium.org/1096463005
|
|
Also update build files to deal with the new revision. The main issue
is the external startup files for v8. The default is not to use them
(simpler for standalone users to deploy), but can be built either way.
R=thestig@chromium.org
Review URL: https://codereview.chromium.org/1059023003
|
|
R=scottmg@chromium.org
Review URL: https://codereview.chromium.org/849113002
|
|
Linux pdfium builds have 215 warnings of this form:
command line option -std=gnu++11 is valid for C++/ObjC++ but not for C
The obvious fix is to not request C++11 for C compilations. The only
complication was the the switch we are using is actually gnu++0x, not
gnu++11.
BUG=https://code.google.com/p/pdfium/issues/detail?id=102
R=tsepez@chromium.org
Review URL: https://codereview.chromium.org/839163002
|
|
pdfium builds on Win32 have about 85 warnings (250 in the XFA
branch, totaling over 480 lines!), mostly from four lines in
a header file and a warning that should be disabled. This
change resolves all but two of them and turns on
warning-as-errors. Bugs have been filed for the two
remaining warnings:
https://code.google.com/p/pdfium/issues/detail?id=100
the 64-bit warnings:
https://code.google.com/p/pdfium/issues/detail?id=101
and the Linux warnings:
https://code.google.com/p/pdfium/issues/detail?id=102
The fix to the double->float truncation bugs will also
improve code-generation.
R=bo_xu@foxitsoftware.com, scottmg@chromium.org, tsepez@chromium.org
Review URL: https://codereview.chromium.org/792953005
|
|
BUG=423883
R=scottmg@chromium.org
Review URL: https://codereview.chromium.org/663633002
|
|
This adds the necessary directives to the standalone gyp file.
R=jschuh@chromium.org, jam@chromium.org
BUG=22
Patch from Michael Doppler <m.doppler@gmail.com>.
Review URL: https://codereview.chromium.org/360273002
|
|
BUG=20
R=jschuh@chromium.org
Review URL: https://codereview.chromium.org/349033008
|
|
R=thakis@chromium.org
Review URL: https://codereview.chromium.org/300993002
|
|
R=thakis@chromium.org
Review URL: https://codereview.chromium.org/302653009
|
|
BUG=msvs build
R=jam@chromium.org
Review URL: https://codereview.chromium.org/295323004
|
|
needed when linking pdfium_test as part of other projects' gyp files as well where standalone.gypi isn't used.
R=scottmg@chromium.org
Review URL: https://codereview.chromium.org/302453004
|
|
|
|
|
|
|
|
I moved pdfium_test from chromium's repo to pdfium's. It's now buildable as a sample following the instructions on the wiki.
|