Allow cross-compilation to Linux from Windows #57
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
1. Remove --build parameter to configure 2. Replace backslashes in the path to configure with forward slashes 3. Explicitly set the AR environment variable when calling configure
|
Thanks! I'll touch this up a bit after merging but looks good to me! |
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.
Addresses at least some of the problems with cross-compiling from Windows in #44 (verified that
arm-unknown-linux-gnueabihfworks).--buildparameter toconfigureconfigurewith forward slashesARenvironment variable when callingconfigureThe second item requires a bit of gymnastics to do the replacement without converting to
Stringas the path may not be representable as UTF-8.Tested native and
arm-unknown-linux-gnueabihfbuilds on Windows and Linux.