On 2018-03-22 07:14 AM, Alexander Kanavin wrote:
On 03/22/2018 08:06 AM, ChenQi wrote:
The test framework meson uses is like:
|e = executable('prog', 'testprog.c') test('name of test', e)|
http://mesonbuild.com/Unit-tests.html
So they could be defined in any valid meson.build file. In systemd's
case, most of them are in top-level meson.build.
I agree with you that it's possible to extract all these test cases
and hold them in a custom script we write. I think this could serve
as a fall-back approach to adding ptest support for systemd.
But I'd like to spend some time to try to find a more general
approach, avoiding headaches when upgrading.
That's right. We probably need to put some kind of 'hook' inside
meson's test() that would copy the test case to a ptest directory,
instead of running it.
Alex
Best if we could pitch this to the meson devs on their list:
The Meson Build System <mesonbu...@googlegroups.com>
The earlier that we describe the problem and our proposed solution with
them the better.
../Randy
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
