Update the README #1420
Update the README #1420
Conversation
- Add FAQ about developing outside of linux - Clean up confusing terminology around docker-compose - Remove outdated link to "developing without docker-compose"
|
|
||
| You probably have [CRLF line endings](https://en.wikipedia.org/wiki/CRLF). | ||
| This causes the hashbang in the docker-entrypoint to be `/bin/sh\r` instead of `/bin/sh`. | ||
| This is probably because you have `git.autocrlf` set to true, | ||
| [set it to `input`](https://stackoverflow.com/questions/10418975) instead. | ||
|
|
||
| ##### I see the error `/opt/rustwide/cargo-home/bin/cargo: cannot execute binary file: Exec format error` when running builds. | ||
|
|
||
| You are most likely not on a Linux platform. Currently, running builds is only supported on `x86_64-unknown-linux-gnu`. |
There was a problem hiding this comment.
we could add what running builds is possible through the web container :)
( I'm happy to add it myself after this)
|
@jyn514 just saw this is open, is this ready for review? Or missing something? |
|
@syphar yes, this is ready for review - feel free to merge if it looks good :) |
syphar
added
the
S-waiting-on-review
|
I have some additional ideas regarding running builds on non-linux systems, but will add them separately. |
|
@syphar I don't think it will be possible without docker-compose without first fixing rust-lang/rustwide#41 |
that I know, |
|
@jyn514 yeah I guess it clears it up to the extent that I am forced to use docker-compose - which kinda sucks ;) |
Closes #1395 ("fixes" is probably a stretch).
@nolash does this clear up some confusion?