Merge lp://staging/~allanlesage/coverage-builder/autotools-test-deux into lp://staging/coverage-builder
Proposed by
Allan LeSage
| Status: | Merged |
|---|---|
| Approved by: | Martin Pitt |
| Approved revision: | 283 |
| Merged at revision: | 280 |
| Proposed branch: | lp://staging/~allanlesage/coverage-builder/autotools-test-deux |
| Merge into: | lp://staging/coverage-builder |
| Diff against target: |
550 lines (+441/-0) 19 files modified
debian/control (+1/-0) test/autotools-project/Makefile.am (+13/-0) test/autotools-project/Makefile.am.coverage (+50/-0) test/autotools-project/README (+1/-0) test/autotools-project/autogen.sh (+5/-0) test/autotools-project/configure.ac (+60/-0) test/autotools-project/debian/changelog (+5/-0) test/autotools-project/debian/control (+12/-0) test/autotools-project/debian/rules (+6/-0) test/autotools-project/m4/gcov.m4 (+86/-0) test/autotools-project/m4/gtest.m4 (+63/-0) test/autotools-project/src/Makefile.am (+17/-0) test/autotools-project/src/fibonacci.cpp (+11/-0) test/autotools-project/src/fibonacci.h (+7/-0) test/autotools-project/src/main.cpp (+7/-0) test/autotools-project/test/Makefile.am (+32/-0) test/autotools-project/test/test-fibonacci.cpp (+22/-0) test/autotools-project/test/test-main.cpp (+8/-0) test/test_autotools.py (+35/-0) |
| To merge this branch: | bzr merge lp://staging/~allanlesage/coverage-builder/autotools-test-deux |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Martin Pitt (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
Minimal test for autotools packages--the trick was to call dh_autoreconf :) .
Again we're doing more thorough testing of further steps in the CMake tests, just need to validate that we get .gcnos for autotools projects here.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
Looks good now! Please merge.
I suppose in the near future you want to expand this with building a library, so that you can check operations with that too.
I consider these test cases as prototypes how projects that want to support coverage should look like. As such I have a few questions below.
Thanks!