Commit Graph

5 Commits

Author SHA1 Message Date
b0afd97d6e Revert of Only expose gflags target in non-Chromium and non-fuzzer builds. (patchset #1 id:40001 of https://codereview.webrtc.org/2321963002/ )
Reason for revert:
Eh, I forgot to run the libfuzzer trybot :( broke in the main waterfall.

Original issue's description:
> Only expose gflags target in non-Chromium and non-fuzzer builds.
>
> Since gflags is not present in Chromium nor the libfuzzer infrastructure,
> we have to ensure we don't accidentally depend on it in WebRTC code
> that is used in such places.
>
> BUG=chromium:645069
> NOTRY=True
>
> Committed: https://crrev.com/9365338db2e0505d6e5f8ea62fa8fe2c45ea8f74
> Cr-Commit-Position: refs/heads/master@{#14145}

TBR=ehmaldonado@webrtc.org,henrik.lundin@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:645069

Review-Url: https://codereview.webrtc.org/2320723007
Cr-Commit-Position: refs/heads/master@{#14149}
2016-09-09 07:27:32 +00:00
9365338db2 Only expose gflags target in non-Chromium and non-fuzzer builds.
Since gflags is not present in Chromium nor the libfuzzer infrastructure,
we have to ensure we don't accidentally depend on it in WebRTC code
that is used in such places.

BUG=chromium:645069
NOTRY=True

Review-Url: https://codereview.webrtc.org/2321963002
Cr-Commit-Position: refs/heads/master@{#14145}
2016-09-09 07:06:12 +00:00
4bba35f735 Switch third_party/gflags to use updated GitHub repo.
This pulls in several fixes and gets Visual Studio 2015 support.
The new repo is located at https://github.com/gflags/gflags
which is mirrored in Chrome infrastructure at
https://chromium.googlesource.com/external/github.com/gflags/gflags

New configuration headers were generated according to README.webrtc
on Windows and Linux. I verified the Linux generated ones are working
on Mac. The generating headers on Mac are identical with only a minor
difference (an __unused attribute) that doesn't effect the build.

BUG=webrtc:5185
NOTRY=True
NOPRESUBMIT=True
TESTED=Successfully ran:
out/Release/video_quality_measurement --input_filename=resources/foreman_cif.yuv  --width=352 --height=288
to verify flags are still being parsed properly.
I also ran the compile trybots and the baremetal bots
(since they run tests that have gflags flags).

Review URL: https://codereview.webrtc.org/1679263002

Cr-Commit-Position: refs/heads/master@{#11539}
2016-02-09 14:47:47 +00:00
60ca31bf5d Roll chromium_revision d66326c..4df108a (367167:367307)
The changes in d66326c..4df108a/build/common.gypi
enables a lot more warnings, which have been disabled/fixed in this CL.
See tracking bugs for remaining work.

Change log: d66326c..4df108a
Full diff: d66326c..4df108a

Changed dependencies:
* src/buildtools: fee7f1e..6d0c448
* src/third_party/libsrtp: b8dd754..8a7662a
DEPS diff: d66326c..4df108a/DEPS

No update to Clang.

BUG=webrtc:5397, webrtc:5398, webrtc:5399
TBR=hta@webrtc.org, perkj@webrtc.org
NOTRY=True

Review URL: https://codereview.webrtc.org/1553033002

Cr-Commit-Position: refs/heads/master@{#11147}
2016-01-04 18:16:01 +00:00
b8caf6a504 GN: Enable libvpx, add link target and convert some test targets
Libvpx now supports GN and this CL turns on compiling it.
I also introduced an executable target 'webrtc_tests'
that depends on all in WeBRTC + tests in order to get a full
linking step executed (since we've seen link problems for GN
when rolling WebRTC into Chromium).

I also converted a few test targets and made a GN file for
third_party/gflags.

BUG=3441
TESTED=Trybots + full Chromium build with a symlinked src/third_party/webrtc
dir to a workspace wit this CL applied.

R=brettw@chromium.org
TBR=niklas.enbom@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/25569004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@7344 4adac7df-926f-26a2-2b94-8c16560cd09d
2014-09-30 18:05:02 +00:00