Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
gen/ | 22-Nov-2023 | - | 2,106 | 690 | ||
BUILD.gn | D | 22-Nov-2023 | 2.1 KiB | 74 | 62 | |
LICENSE | D | 22-Nov-2023 | 1.4 KiB | 29 | 25 | |
README.libyuv | D | 22-Nov-2023 | 1.2 KiB | 29 | 24 | |
gflags.gyp | D | 22-Nov-2023 | 2.7 KiB | 93 | 90 |
README.libyuv
1URL: https://github.com/gflags/gflags 2Version: 2.1.2 3License: New BSD 4License File: LICENSE 5 6Description: 7The gflags package contains a library that implements commandline 8flags processing. As such it's a replacement for getopt(). It has 9increased flexibility, including built-in support for C++ types like 10string, and the ability to define flags in the source file in which 11they're used. 12 13Local Modifications: None 14 15 16How to update platform configuration files: 17The gen/ directory contains pre-generated configuration header files. 18Historically, all operating systems and architectures have generated 19similar configurations except for Windows. This is why there's only 20posix and win directories below gen/. 21When rolling gflags to a newer version, it's a good idea to check if 22new configuration files needs to be generated as well. 23Do this by running ./configure in the newly checked out version of 24gflags. Then diff the generated files with the ones below gen/. 25If you notice a diff, update the files with the updated ones. 26If you suspect platform dependend changes other than Windows, you'll 27have to checkout gflags on the other platforms as well and run 28./configure there too. 29