Several mingw32|64 packages provide static libraries in the associated
development package.

When building for Tumbleweed, there are rpmlint issues, for example with the
mingw64-openssl_1.1 package: 

[ 1418s] mingw64-libopenssl-1_1-devel.noarch: E:
arch-independent-package-contains-binary-or-object (Badness: 499)
/usr/x86_64-w64-mingw32/sys-root/mingw/lib/libcrypto.a
[ 1418s] mingw64-libopenssl-1_1-devel.noarch: E:
arch-independent-package-contains-binary-or-object (Badness: 499)
/usr/x86_64-w64-mingw32/sys-root/mingw/lib/libssl.a

(see
https://build.opensuse.org/package/live_build_log/windows:mingw:win64/mingw64-openssl-1_1/openSUSE_Tumbleweed/x86_64
for details) 

To fix this problem, the following line must be added to xxx-rpmlintrc

addFilter('arch-independent-package-contains-binary-or-object')

for each affected package:

$ ~/osc/windows:mingw:win32> find -maxdepth 2 -name '*-rpmlintrc' -exec grep
-Hn arch-independent-package-contains-binary-or-object {} \; | wc -l
60

$ ~/osc/windows:mingw:win64> find -maxdepth 2 -name '*-rpmlintrc' -exec grep
-Hn arch-independent-package-contains-binary-or-object {} \; | wc -l
57

Since it is a common pattern to build mingwxx packages as "noarch" architecture
and it is obvious that many of these packages install static libraries, the
question arises whether this exception can be defined centrally and thus is not
required in every package.