-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
switch extensions of static libs on windows #131
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Thanks a lot @h-vetinari ! Just a curiosity, I guess that you considered renaming the static libraries to |
That would just create the same problem for any user of the Together with:
I don't see how else to fix this TBH... |
In which way? If I understood correctly, after #128 |
Fair enough, thanks for walking me through that... |
dea6e3b
to
9cc2d65
Compare
leave the standard one (".lib") for detection of the import library
Another fallout from #128, which changed the static libs to depend on the shared ones according to conda-forge/conda-forge.github.io#1809.
This needed an adaptation of the import library names (since they share the
.lib
suffix with the static ones); so far so good, all that is saved in the CMake metadata. However, CMake prefers its own customFindProtobuf
despite having package metadata created by itself, and then ends up not finding the adapted import libs. 🤦Undo this to stop the bleeding.Switch the extension of the import library to use the default ".lib", see this comment