• Richard Geary's avatar
    Add support for outputting dependency manifest files, used by ninja and make · 532c9414
    Richard Geary authored
    Use --manifest-file=somefile.d to output the dependency manifest.
    This file will contain a list of files which were read by protoc as part
    of creating the output files.  It doesn't include the plugin inputs if
    plugins are used, that could be a later extension.
    The manifest file is in the format <output file>: <input files>.  The
    manifest file format only allows you to specify one output file, which
    isn't a problem as it's used to detect input changes in order to detect
    when to rerun the protoc command.  The output file used in the manifest
    is the manifest filename itself; to use this in ninja you should declare
    the manifest file as the first output as well as the depfile input.
    532c9414
Name
Last commit
Last update
benchmarks Loading commit data...
editors Loading commit data...
examples Loading commit data...
java Loading commit data...
javanano Loading commit data...
m4 Loading commit data...
more_tests Loading commit data...
python Loading commit data...
ruby Loading commit data...
src Loading commit data...
vsprojects Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
Android.mk Loading commit data...
CHANGES.txt Loading commit data...
CONTRIBUTORS.txt Loading commit data...
INSTALL.txt Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.md Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
generate_descriptor_proto.sh Loading commit data...
post_process_dist.sh Loading commit data...
protobuf-lite.pc.in Loading commit data...
protobuf.pc.in Loading commit data...
test-driver Loading commit data...