-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hack needed for building on Linux/Unix #1
Comments
Good point. I didn't notice that myself, as I have SDK in internal git repository where the line endings are already fixed by git (ie. I have core.autocrlf = input). |
Alternative way to solve this with git would be cd WICED-SDK-3.3.1 git init git config core.autocrlf input git add . warning: CRLF will be replaced by LF in .... The file will have its original line endings in your working directory. git commit -a -m "fix line endings." git rm --cached -r . git reset --hard |
This is now documented in README. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The wiced.patch operation described in the README.md instructions fails on Linux because some of the files have CRLF line endings (and so they don't match what patch is expecting). Here's a quick hack that was tested on Linux to run in the directory prior to patch to switch the text file lines so they match. This script can take a long time to traverse the SDK tree with possibly long pauses: be careful not to interrupt it.
The text was updated successfully, but these errors were encountered: