08/12/2020 16:37, David Marchand: > On Mon, Dec 7, 2020 at 6:33 PM Thomas Monjalon <tho...@monjalon.net> wrote: > > > > When testing compilation and checking ABI compatibility, > > there is no real need of static binaries eating disks. > > The static linkage of applications are tested with GCC and Clang, > > plus some examples are statically linked. > > The after-installation build test is limited to "helloworld" example. > > Note the meson static build test was already limited to "l3fwd" example. > > > > The ABI compatibility is checked on shared libraries, so no need > > running this test a second time on builds intended for static linking. > > However, limiting ABI check to "shared builds" means all test cases > > must have a "shared build" occurence. > > As a consequence the 32-bit build test is switched to shared linking. > > I see no reason to tie the ABI check to default-library.
The only reason is that ABI check triggers binary installation, which is big when statically linked. > What about the mingw target? ABI check is not required for Windows. BTW there are issues with DLL support. > What you want is to avoid doing duplicate ABI checks. > This happens for the gcc/clang x86 builds, so I'd rather control the > ABI checks out of the build() function (passing a new parameter?). Yes, it would be cleaner to separate ABI check requirement and static linking. In v2, ABI check will be enabled explicitly when calling "build" function for shared builds.
