--include-imports when dll and lib are in separate locations

[WillAyd]

--include-imports is documented as only including the .lib when it shares the same stem and directory as the corresponding .dll. One of the projects I am working with however decides to put the .dll in the system bin directory and the .lib file in the system lib directory.

Without knowing a ton about Windows packaging, I am under the impression that this pattern is not uncommon. Has there been any discussion as to how an installation like that might still be packaged by delvewheel?

[WillAyd]

FWIW I am under the impression this is the default behavior of CMake build systems, to push .dll files to /bin and .lib files to /lib

Perhaps we can add logic to delvewheel to check the path of the detected .dll, and see if there is an import file in a corresponding /lib location?

[adang1345]

--include-imports is not often used, so the functionality is fairly basic. Visual Studio builds often put the .lib and .dll files in the same location (though this is configurable), so I made a simple design based on that. I would expect that it's not too difficult to configure a CMake build system to do the same or add a step that copies the files into the same location.