Build Git version of Hamlib ourselves for Win32 #261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@hobbes1069, I think it would still be good to have v4.4 mingw{32,64}-hamlib packages as this makes the build take significantly longer. In any case, I'll post up a test build using this PR to make sure there are no major issues with the Hamlib that got built. CC @drowe67 in case he has feedback too. |
|
Merging as I haven't heard any objections. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Builds latest Hamlib whenever Docker container is used. This is so that the Windows builds use the same version of Hamlib as macOS. Resolves #260.