The envsetup configuration for building WebView using the Android build
system has rotted. Rather than try to share the non_sdk_build_init code,
just repeat the (few) parts we need to avoid setting all the parts that
are inappropriate, and fix the parts that are wrong or outdated.
Also, upstream the common.gypi settings that are specific to the WebView
build.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11026038
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160188 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
It stores mapping between object's starting addresses and their
allocated types when a build option 'clang_type_profiler=1' is
specified. It enables information like
"an object at 0x37f3c88 is an instance of std::string."
Nothing is changed when the option is not specified.
It depends on a modified version of the LLVM/Clang compiler
introduced at deps/third_party/llvm-allocated-type.
BUG=123758
TEST=build with clang_type_profiler=1 and run type_profiler_unittests and type_profiler_map_unittests manually.
Review URL: https://chromiumcodereview.appspot.com/10411047
git-svn-id: http://src.chromium.org/svn/trunk/src/build@158752 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
If the DoneCallback returns false, breakpad should reinstall the old
signal handlers. Specifically, it will reinstall the Android tombstone
handler. This change ensure that on Android we always return false from
these callbacks. When this happens, the minidump should still be
created/uploaded as normal.
Also, just prior to returning we log a Chrome build fingerprint. This
should appear in the log just above the tombstone.
Requires breakpad DEPS roll to >=1025
(http://breakpad.appspot.com/440002/) to work correctly, but fails
safely without it.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10908115
git-svn-id: http://src.chromium.org/svn/trunk/src/build@156063 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Restructures content_app.gypi, content_common.gypi, and content_tests.gypi
slightly to support building them for iOS.
One target, content_browsertests, is excluded entirely for iOS.
More files will be added to the iOS build later, once the content/ build
is working for iOS.
BUG=None
Review URL: https://chromiumcodereview.appspot.com/10917130
git-svn-id: http://src.chromium.org/svn/trunk/src/build@155759 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
1474: Emacs mode for gyp: font-lock edition.
1475: Tidy up default toolset for msbuild-based builds.
1476: add -Gstandalone flag
1477: Enable pretty xml generation.
1478: msvs: Ensure trailing slash on IntermediateDir and OutputDir.
1479: mac ninja&make: Pass OTHER_LDFLAGS to libtool for static libraries.
Also don't pass -faddress-sanitizer to libtool.
BUG=113085
Review URL: https://chromiumcodereview.appspot.com/10876059
git-svn-id: http://src.chromium.org/svn/trunk/src/build@153250 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Is causing warnings for Official build in PDF code. Boo.
-----------------
Can't quite be fully enabled yet due to not-yet-fixed third party
dependencies. Without it enabled, other packages regress while we're fixing
things. So, add a flag for now so warnings-freeness can be ratcheted forward
by having it on for most packages, but off for a few.
Also, disable warning in qcms (fixed upstream by a large refactoring, not
worth rolling for), and disable two minor warnings in yasm (patch posted
upstream for a few months, but maintainer does not seem motivated to merge).
Fix release-only warning in leveldatabase/env_chromium.cc. Was calling exit(1)
in a leaky destructor.
Fix a warning in lzma_sdk (missing an include).
Disable a silly warning in Release builds of skia and memory_watcher (that
/GS is not working because optimization is disabled).
Warning are currently tolerated in libvpx and mesa.
Cannot be committed until http://chromiumcodereview.appspot.com/10823426/ has
landed.
R=thakis@chromium.org
BUG=126483,140121, 143877
TEST=
Review URL: https://chromiumcodereview.appspot.com/10827429TBR=scottmg@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10872063
git-svn-id: http://src.chromium.org/svn/trunk/src/build@153223 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Can't quite be fully enabled yet due to not-yet-fixed third party
dependencies. Without it enabled, other packages regress while we're fixing
things. So, add a flag for now so warnings-freeness can be ratcheted forward
by having it on for most packages, but off for a few.
Also, disable warning in qcms (fixed upstream by a large refactoring, not
worth rolling for), and disable two minor warnings in yasm (patch posted
upstream for a few months, but maintainer does not seem motivated to merge).
Fix release-only warning in leveldatabase/env_chromium.cc. Was calling exit(1)
in a leaky destructor.
Fix a warning in lzma_sdk (missing an include).
Disable a silly warning in Release builds of skia and memory_watcher (that
/GS is not working because optimization is disabled).
Warning are currently tolerated in libvpx and mesa.
Cannot be committed until http://chromiumcodereview.appspot.com/10823426/ has
landed.
R=thakis@chromium.org
BUG=126483,140121, 143877
TEST=
Review URL: https://chromiumcodereview.appspot.com/10827429
git-svn-id: http://src.chromium.org/svn/trunk/src/build@153092 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
without this CL
fastbuild=1 => no debug information
win_z7=1 => debug information available (with /Z7)
fastbuild=1 win_z7 => *.obj has debug info, but linker doesn't generate debug info in *.exe. it would be useless, and just makes build slower
This CL makes win_z7 wins against fastbuild.
R=scottmg,arthurhsu
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10866016
git-svn-id: http://src.chromium.org/svn/trunk/src/build@152953 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The enable_themes and enable_extensions gyp variables were in a different
scope that prevented the grit_defines from having the correct value when
evaluating the condition. Moves the variable assignment into the same
scope as the variable declaration and now everything is happy.
TEST=touch chrome/browser/browser_resources.grd && \
make chrome_resources (check about_version does not have theme icon)
BUG=
Review URL: https://chromiumcodereview.appspot.com/10828396
git-svn-id: http://src.chromium.org/svn/trunk/src/build@152455 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
supports the debug MSVS libc dll. Also disabled debug build inlining
and FPO to support increasing debug build optimization.
Re-add unit_tests to the "Windows Tests (DrMemory)" bot. (The
unit_tests cannot be linked with static_library, which is why they
were removed from the bot.)
BUG=137180
R=rnk@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10834341
git-svn-id: http://src.chromium.org/svn/trunk/src/build@151770 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This CL removes our custom GYP flag and modifies the build so both the SRPC and IPC proxies are built side by side. In addition, NaClBrowser now checks the '--enable-nacl-ipc-proxy' flag to determine which IRT to load. The IPC proxy's name is of the form 'nacl_ipc_irt_*'.
BUG=116317
TEST=builds and runs NaCl apps with --enable-nacl-ipc-proxy
TBR=bbudge@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10831316
git-svn-id: http://src.chromium.org/svn/trunk/src/build@151693 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Before this change we build Release builds size-optimized code with DCHECK,
while we almost never use the Debug build which is not size-optimized.
Now change Debug build to build size-optimized code with DCHECK but still
temporarily keep Release build and default configuration unchanged before
everyone (the bots, scripts and developers) knows how to deal with this change.
Next steps will be:
Step 2: update developer scripts and buildbot scripts to handle the new
configuration.
Step 3: change Release configuration to no DCHECK and change default
configuration to Debug.
After all steps finish, this new configuration will better match Chromium
and WebKit (e.g. better matches the DEBUG and RELEASE tags in WebKit layout
test expectations), and makes it easier to build a performance build.
Review URL: https://chromiumcodereview.appspot.com/10827273
git-svn-id: http://src.chromium.org/svn/trunk/src/build@151589 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This CL removes our custom GYP flag and modifies the build so both the SRPC and IPC proxies are built side by side. In addition, NaClBrowser now checks the '--enable-nacl-ipc-proxy' flag to determine which IRT to load. The IPC proxy's name is of the form 'nacl_ipc_irt_*'.
BUG=116317
TEST=builds and runs NaCl apps with --enable-nacl-ipc-proxy
Review URL: https://chromiumcodereview.appspot.com/10836220
git-svn-id: http://src.chromium.org/svn/trunk/src/build@151581 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
shashishekhar@chromium.org
michaelbai@google.com
glotov@chromium.org
saintlou@chromium.org
torne@chromium.org
maruel@chromium.org
msarda@chromium.org
mihaip@chromium.org
dmikurube@chromium.org
tony@chromium.org
michaelbai@chromium.org
joi@chromium.org
ilevy@chromium.org
stuartmorgan@chromium.org
jamesr@chromium.org
cjhopman@chromium.org
thakis@chromium.org
droger@chromium.org
glider@chromium.org
scottmg@google.com
xhwang@chromium.org
scottmg@chromium.org
ukai@chromium.org
wangxianzhu@chromium.org
tedchoc@chromium.org
lliabraa@chromium.org
blundell@chromium.org
peter@chromium.org
bruening@google.com
flackr@chromium.org
bbudge@chromium.org