We may as well define the dll output for mingw alongside the darwin dylib definitions. There are some recipes which output .so files even on mingw but those can be handled specifically in mingw.
Signed-off-by: Richard Purdie <[email protected]> --- meta/conf/bitbake.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index ab4c6a2d9c9..3f583668f66 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -307,12 +307,14 @@ BB_MULTI_PROVIDER_ALLOWED = "virtual/libintl virtual/libintl-native virtual/nati SOLIBS = ".so.*" SOLIBS:darwin = ".dylib" +SOLIBS:mingw32 = ".dll" SOLIBSDEV = ".so" # Due to the ordering of PACKAGES and the naming of the dev symlinks on darwin, # we can't make the symlinks end up in the -dev packages easily at this point. This hack # at least means builds aren't completely broken and symlinks don't take up much space. SOLIBSDEV:darwin = ".dylibbroken" +SOLIBSDEV:mingw32 = ".dll" PACKAGE_DEBUG_SPLIT_STYLE ?= "debug-with-srcpkg"
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#204714): https://lists.openembedded.org/g/openembedded-core/message/204714 Mute This Topic: https://lists.openembedded.org/mt/108547797/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
