Independently from the actual question, which is still unanswered, it's
always a pleasure to see how "old" developers - living in a symbiosis with
the code - are worrying about the status quo.
2017-11-12 18:39 GMT+01:00 Zolnai Tamás <zolnaitamas2000@gmail.com>:
As others have pointed out, the targets you are looking for are available.
If
you dont like how they are named, please just create yourself some
function or
alias in your local ~/.bashrc, but do not force this on the rest of the
world[1].
Anyway adding an optional configure option does not mean forcing anybody
to do anything.
It was just the idea of an other quasi hidden option (as there are a lots
of mostly unknown configure options), but as I said I can solve it my local
machine.
I was just interested in what is the reason of running random tests by
plain make.
Best Regards,
Tamás
Context
- Re: Running unit test by make <module> (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.