On Wed, Dec 10, 2014 at 2:29 AM, Maarten Hoes <hoes.maarten@gmail.com> wrote:
No, of course not, I guess. But the alternative to using all the internal
libraries, is installing all required libraries in the right versions
required on the system, and then doing --with-system-foo for all of them.
that is a trade-off between a generaly usefull script and a tuned for
a dedicated tb one
my changes (that I have not upstreamed yet.. as I'm still testing -
very long build on that box)
were mostly to simplify the invocation
I added a -f option
that do the build the before, run make check and run the after all in one call
and all the directory have default values:
SRC_DIR = $(pwd)
BUILD=SRC
HTML=BUILD/workdir/lcov/html
TESTDATA=BUILD/workdir/lcov/data
in the end I should be able to just run
lcov-report.sh -f
Context
- Re: Scheduling lcov code coverage script (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.