protobuf-c/.gitignore

*~
.*swp
*.la
*.gcda
*.gcno
*.lo
*.log
*.o
*.tar.gz
*.trs
.deps/
.dirstamp
.libs/
/Doxyfile
/Makefile
/Makefile.in
/aclocal.m4
/autom4te.cache
/build-aux
/config.*
/configure
/doxygen-doc
/html
/libtool
/protobuf-c-*-coverage.info
/protobuf-c-*-coverage/
/stamp-h1
/stamp-html
/test-suite.log
TAGS
protobuf-c/libprotobuf-c.pc
protoc-c/protoc-c
protoc-c/protoc-gen-c
t/generated-code/test-generated-code
t/generated-code2/cxx-generate-packed-data
t/generated-code2/test-full-cxx-output.inc
t/generated-code2/test-generated-code2
t/generated-code3/test-generated-code3
t/version/version
*.pb-c.c
*.pb-c.h
*.pb.cc
*.pb.h
.gitignore: Ignore temporary files that end with ~ 2013-11-18 21:08:53 -08:00			`*~`
new build system 2013-11-16 18:00:53 -05:00			`.*swp`
			`*.la`
add code coverage option to the build system configure now has a "--enable-code-coverage" option, and if the lcov/gcov tools are available a code coverage report can be built with "make check-code-coverage". this is mostly based on the AX_CODE_COVERAGE / GNOME_CODE_COVERAGE macro: http://savannah.gnu.org/patch/?8451 but i also looked at knot-dns's code coverage implementation: https://github.com/CZNIC-Labs/knot/blob/master/m4/code-coverage.m4 and kevin lyda's pull request: https://github.com/protobuf-c/protobuf-c/pull/131/files 2014-06-02 17:50:57 -04:00			`*.gcda`
			`*.gcno`
new build system 2013-11-16 18:00:53 -05:00			`*.lo`
gitignore: ignore output from the test suite 2013-11-16 18:09:47 -05:00			`*.log`
new build system 2013-11-16 18:00:53 -05:00			`*.o`
			`*.tar.gz`
gitignore: ignore output from the test suite 2013-11-16 18:09:47 -05:00			`*.trs`
new build system 2013-11-16 18:00:53 -05:00			`.deps/`
			`.dirstamp`
			`.libs/`
switch to a more automake-ish method of generating the html doxygen documentation 2014-06-03 17:26:59 -04:00			`/Doxyfile`
.gitignore: anchor Makefile and Makefile.in at the top of the tree 2014-03-26 14:06:17 -04:00			`/Makefile`
			`/Makefile.in`
new build system 2013-11-16 18:00:53 -05:00			`/aclocal.m4`
			`/autom4te.cache`
			`/build-aux`
			`/config.*`
			`/configure`
Autoconf configuration for doxygen. Still need to add the comments in the source code. Currently I've seeded it with the libprotobuf-c files. I've configured it to make man pages and html pages. Might not be ideal, but makes it easy for me to check things (html is nicer, but man pages are handier for remote servers). 2014-02-16 21:45:02 +00:00			`/doxygen-doc`
switch to a more automake-ish method of generating the html doxygen documentation 2014-06-03 17:26:59 -04:00			`/html`
new build system 2013-11-16 18:00:53 -05:00			`/libtool`
add code coverage option to the build system configure now has a "--enable-code-coverage" option, and if the lcov/gcov tools are available a code coverage report can be built with "make check-code-coverage". this is mostly based on the AX_CODE_COVERAGE / GNOME_CODE_COVERAGE macro: http://savannah.gnu.org/patch/?8451 but i also looked at knot-dns's code coverage implementation: https://github.com/CZNIC-Labs/knot/blob/master/m4/code-coverage.m4 and kevin lyda's pull request: https://github.com/protobuf-c/protobuf-c/pull/131/files 2014-06-02 17:50:57 -04:00			`/protobuf-c-*-coverage.info`
			`/protobuf-c-*-coverage/`
new build system 2013-11-16 18:00:53 -05:00			`/stamp-h1`
switch to a more automake-ish method of generating the html doxygen documentation 2014-06-03 17:26:59 -04:00			`/stamp-html`
gitignore: ignore output from the test suite 2013-11-16 18:09:47 -05:00			`/test-suite.log`
new build system 2013-11-16 18:00:53 -05:00			`TAGS`
			`protobuf-c/libprotobuf-c.pc`
			`protoc-c/protoc-c`
.gitignore: protoc-c/protoc-gen-c 2016-04-26 16:35:22 -04:00			`protoc-c/protoc-gen-c`
new build system 2013-11-16 18:00:53 -05:00			`t/generated-code/test-generated-code`
			`t/generated-code2/cxx-generate-packed-data`
			`t/generated-code2/test-full-cxx-output.inc`
			`t/generated-code2/test-generated-code2`
.gitignore: t/generated-code3/test-generated-code3 2017-07-29 19:44:07 -04:00			`t/generated-code3/test-generated-code3`
t/: add new test program 'version' 2014-04-03 17:08:33 -04:00			`t/version/version`
new build system 2013-11-16 18:00:53 -05:00			`*.pb-c.c`
			`*.pb-c.h`
			`*.pb.cc`
			`*.pb.h`