-
Notifications
You must be signed in to change notification settings - Fork 5
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
Test win build #65
Test win build #65
Conversation
3bc6a93
to
a77ddee
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
a77ddee
to
c944ad4
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@jdblischak I think we are going to need the |
8b2a1c5
to
2dec66e
Compare
Closing since our strategy has since changed. As I understand, the plan is to build htslib for Windows in its own dedicated feedstock. It will compile htslib with msys2. The main motivation for this is that the htslib maintainers regularly test on Windows using the msys2 environment, and past efforts to build and maintain a Visual Studio/CMake environment have been unsuccessful. Then in this feedstock, libtiledbvcf will be built for Windows with Visual Studio/CMake, and will access htslib using the compatible API from the mys2 build. This avoids us having to build libtiledbvcf with msys2 as I had begun attempting in this PR. |
Trying out a build on Windows