Skip to content

Conversation

@michaelkirk
Copy link
Member

@michaelkirk michaelkirk commented Apr 19, 2021

This is just a dupe of #79, but trying to work around whatever bug is breaking CI.

(my theory is that we won't encounter the bug when bors is running off a branch local to this repo... we'll see)

@michaelkirk
Copy link
Member Author

bors try

bors bot added a commit that referenced this pull request Apr 19, 2021
@bors
Copy link
Contributor

bors bot commented Apr 19, 2021

try

Build succeeded:

@michaelkirk
Copy link
Member Author

This is really old, but just to leave a trail of breadcrumbs...

This PR doesn't represent work that I was bottom lining, I was just trying to take the work from #79 and get CI to pass.

#79 stalled out with this comment: #79 (comment)

@urschrei
Copy link
Member

If there really is no way of getting the version from vcpkg, the version is available at runtime. This is obviously not ideal, but it would be feasible to have a Windows-only runtime version compatibility check to guard against instances in which the compile step is successful using an unsupported library version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants