Re: [OE-core][PATCH v8] expat: Added ptest

["Oleksandr" <oleksandr.s.popovych@globallogic.com>]

Hello Richard, Joshua,

On Mon, May 11, 2020 at 3:45 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> ...
>
> Thanks, this is definitely getting there. There was only one test
> failure this time, with meta-mingw:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/1884
>
> I've cc'd Joshua in case he has any insights on this.

I`ve tested my patch with meta-mingw layer on my host and it seems I
have fixed the current compilation error, with making some changes to
meta-mingw (by changing "CMAKE_SYSTEM_NAME" variable to "Windows"
value during toolchain file generation in
"recipes-core/expat/expat_%.bbappend" file using a
"recipes-devtools/cmake/cmake_%.bbappend" file as template). However
this is only part of a solution, because another error appears next to
it: gdb-cross-canadian that depends on expat now fails to build,
because it can not find a proper expat library. It seems that expat
recipe, which was switched to build with CMake in my patch, does not
generate output library in proper format (it compiles only
"libexpat.dll.a", when the current version of expat recipe from
upstream, that uses Autotools, generates both "libexpat.a" and
"libexpat.dll.a"). This is such an error that I can not figure out how
to solve it by myself, so I ask for help.

Additionally I would like to ask you: How should I send patches now
when at least two separate patches with similar purposes should be
sent to different layers (one for [OE-core] and other for
[meta-mingw])? Should they be connected with some kind of cover-letter
or is there another option?

Thanks for your attention.