macOS: Explicit Makefile.osx using static linking #18
Conversation
This file contains hidden or 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
Instead of using pkg-config and assuming Homebrew or similar package management is present, use explicit manually built static libraries for libusb and libftdi. This makefile was used to generate portable ujprog in: emard/ulx3s-bin@0f782d92267fa4faa3ee
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Instead of using pkg-config and assuming Homebrew or similar package management
is present, use explicit manually built static libraries for libusb and libftdi.
This makefile was used to generate portable ujprog in:
emard/ulx3s-bin@0f782d92267fa4faa3ee
I don't know if this is better or more straightforward for average user though, but at least can be done with vanilla system 😉