>> Have you by chance tried to add ptest coverage for poppler?
>> If not, Matthew may do that.
>>
>>
> Have not done any ptest on this - just some runtime tests on target with
> evince
>
> Andreas
```
$ make test
Running tests...
Test project /home/mzeng/code/poppler/build
Start 1: check_qt5_attachments
1/21 Test #1: check_qt5_attachments ............***Failed 2.47 sec
Start 2: check_qt5_dateConversion
2/21 Test #2: check_qt5_dateConversion ......... Passed 0.58 sec
...
```
Poppler's `make test` runs tests from the `/build/qt5/tests` directory, which
apparently are relying on qt5.
```
/****************************************************************************
** Meta object code from reading C++ file 'check_attachments.cpp'
**
** Created by: The Qt Meta Object Compiler version 67 (Qt 5.14.0)
**
** WARNING! All changes made in this file will be lost!
*****************************************************************************/
#include <memory>
#include <QtCore/qbytearray.h>
#include <QtCore/qmetatype.h>
...
```
Is it worth it to write a ptest and sort out the meta-qt5 layer?
Matthew
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
