mirror of
https://chromium.googlesource.com/libyuv/libyuv
synced 2025-12-06 16:56:55 +08:00
b6bfacc2e7
* Update gflags to newer repository location (plain copy from the files in WebRTC). * Add workarounds for mojo dependency (see http://bugs.webrtc.org/5629 for more details). * Update libyuv_unittest to generate user friendly run-scripts for Android in out/{Debug,Release}/bin * Fix Android test execution by adding explicit dependency on Chromium's base/base.gyp:base_build_config_gen This roll also solves the compile problem for Mac ASan bots. Change log: |
||
|---|---|---|
| .. | ||
| gen | ||
| BUILD.gn | ||
| gflags.gyp | ||
| LICENSE | ||
| README.libyuv | ||
URL: https://github.com/gflags/gflags Version: 2.1.2 License: New BSD License File: LICENSE Description: The gflags package contains a library that implements commandline flags processing. As such it's a replacement for getopt(). It has increased flexibility, including built-in support for C++ types like string, and the ability to define flags in the source file in which they're used. Local Modifications: None How to update platform configuration files: The gen/ directory contains pre-generated configuration header files. Historically, all operating systems and architectures have generated similar configurations except for Windows. This is why there's only posix and win directories below gen/. When rolling gflags to a newer version, it's a good idea to check if new configuration files needs to be generated as well. Do this by running ./configure in the newly checked out version of gflags. Then diff the generated files with the ones below gen/. If you notice a diff, update the files with the updated ones. If you suspect platform dependend changes other than Windows, you'll have to checkout gflags on the other platforms as well and run ./configure there too.