[Windows] Leftover assertlibs in XML-Parser build dir after upgrade to 2.47

[mtsanovv]

I have a custom perl distribution build that in the end creates an archive, containing several static libraries, one of them being the result from the build of XML-Parser. My build pipeline scans for obj files on Windows and uses the LINK.EXE tool to stick the libraries together:

/LIB /verbose /wx /out:my_archive.lib c:\j\701\w\64uld4c72r\gen\out\build-ff2dd19f\XML-Parser-2.46\Expat\Expat.obj

However, after the update to 2.47, my pipeline finds assertlib obj files and tries doing the following:

/LIB /verbose /wx /out:my_archive.lib c:\j\701\w\64uld4c72r\gen\out\build-ff2dd19f\XML-Parser-2.47\assertlibDjV4eMSu.obj c:\j\701\w\64uld4c72r\gen\out\build-ff2dd19f\XML-Parser-2.47\assertlibRF8qOTKX.obj c:\j\701\w\64uld4c72r\gen\out\build-ff2dd19f\XML-Parser-2.47\Expat\Expat.obj

I can see that the newly introduced CheckLib logic (https://github.com/cpan-authors/XML-Parser/blob/master/inc/Devel/CheckLib.pm) is supposed to run _cleanup_exe after creating those files (and if it fails, it should throw a warning). Unfortunately, I don't observe any warnings like this on my STDOUT/STDERR. Running the same XML-Parser build on Linux & macOS does not produce such assertlibs in the end result (I suppose they get deleted).

I'm modifying my pipeline to ignore assertlib files but I thought that it'd be a good idea to give you a heads up.