Strip .dll
extension from raw-dylib link names
#2431
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As noted in the comment, currently
windows-bindgen
emits the full name of the dll including the extension, which will cause runtime failures since somewhere (linker? dynamic loader?) the extension is automatically added, causing the dll not to be found and abort.I think the confusion may come from the RFC containing example code which does include the extension.
Note this doesn't impact
bthprops.cpl
which is the 1? case I could find of a dynamic lib having an extension other than .dll.I was opening an issue and realized it was easier to just fix it.