[CI] Fix the compilation on Windows #92
Merged
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.
@odow @cvanaret
HiGHS
provides some configuration files for CMake, making it easier to detect when compiling it with other libraries likeUno
.The issue is that these configuration files use
libuno.dll.a
on Windows as an entry point for linking.A file
*.dll.a
is an import library (neither static nor shared) — see my explanation here.If we use
-DHIGHS=${libdir}/libhighs.dll
, we create another entry point that leads to duplicate symbols during the linking phase.I modified the files
build_tarballs_*.jl
so that we use the import library of HiGHS on Windows to ensure a single entry point.After merging this PR, Charlie, you can retrigger the CI build by forcing the tag with: