-
Notifications
You must be signed in to change notification settings - Fork 570
Document supported GOOS values in README (FreeBSD is not supported). #770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This looks very similar to, and there is a lot of useful and relevant information in issue #511. I'm not sure that we did anything to resolve it. Edit: We did have PR #513, but it was closed with the alternative solution of relying on Edit 2: The commit message of perkeep/perkeep@749d512 summarizes the situation nicely. |
Ah! Thank you for digging this up! I tried to search for closed issues but was too tired, I guess. I‘m closing this since it is clearly a duplicate. |
Agree it’s a duplicate, but let’s document FreeBSD as unsupported in the README, so we don’t have to rely on people searching through closed issues and PRs to figure that out. We can use this issue to track that. |
Yes, sure! ps: I also successfully checked the workaround. |
Add instructions for what people should do when building with GopherJS on unsupported platforms. Code generation works completely fine, but syscalls (e.g., for gopherjs run) will only work on supported platforms. Previously, this information was only in issues, people's heads, commit messages, etc. It should be documented in README to provide clarity. Rename "OS X" to "macOS", the current name of that operating system. Rearrange sections to place more relevant information first. Mention Linux before macOS consistently. Linux is placed first because it's open source and more freely available than the proprietary macOS, so it's easier to recommend it as an alternative. Resolves #770. Updates #776. Updates #688.
Add instructions for what people should do when building with GopherJS on unsupported platforms. Code generation works completely fine, but syscalls (e.g., for gopherjs run) will only work on supported platforms. Previously, this information was only in issues, people's heads, commit messages, etc. It should be documented in README to provide clarity. Rename "OS X" to "macOS", the current name of that operating system. Rearrange sections to place more relevant information first. Mention Linux before macOS consistently. Linux is placed first because it's open source and more freely available than the proprietary macOS, so it's easier to recommend it as an alternative. Resolves #770. Updates #776. Updates #688.
I tried to integrate a gopherjs build step into our jenkins CI, which is running on FreeBSD.
The same command runs fine in my dev environment under Linux.
Would like to supply more info but I'm not even sure where these paths come from..
I'm using Go 1.10 and GopherJS 1.10-2.
The text was updated successfully, but these errors were encountered: