-
Notifications
You must be signed in to change notification settings - Fork 275
Build only on windows. #106
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
Conversation
|
Hi @erikh, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
|
signed |
lowenna
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you not need an 'unsupported.go' file that is !windows?
|
seems to build fine without it (the relevant portions are gated by
something else I assume)
…On Sun, Jan 22, 2017 at 10:04 PM, John Howard ***@***.***> wrote:
***@***.**** commented on this pull request.
Do you not need an 'unsupported.go' file that is !windows?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#106 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABJ64YJJbyzznPkuB85UyzV7ed2DDQSks5rVELggaJpZM4Lqr24>
.
|
|
Hi, I am closing and re-opening this PR to bump the CLA bot. Sorry for the inconvenience! |
|
Hi @erikh, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
| @@ -1,3 +1,5 @@ | |||
| // +build windows | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this file should be updated as it's autogenerated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this contain windows only code? If so, we should keep it from compiling.
go generate should not affect the build tag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see. I'll fix it.
Signed-off-by: Erik Hollensbe <github@hollensbe.org>
|
Added it to the generator to get the best of both worlds. I have manually edited the generated source still, but it should reflect the generated version. Can you test for me? I don't have a windows development environment atm (but fwiw, I do all my hacking on linux on windows 10 :) |
|
@erikh - Can I ask why you're even pulling a Windows-only library into Linux code though? Questioning whether making this change is really the right thing to do, and it just simply shouldn't be used on non-Windows platforms. |
|
I believe the requirement comes from docker, but I'll double check. |
|
Is there a practical disadvantage to doing this? |
|
@erikh FYI it builds on Windows, haven't verified if it works. |
|
I'm closing this for now. I can't think why a Windows-specific library would need to be included in Linux, and haven't seen anything convincing to warrant updating this. |
Expanded runC tests
Over at github.com/containers/ I'm trying to incorporate various parts of docker which leverage this library. I am building on linux.
The references to go-winio do not build on linux because they have a build tag which demands windows. This library leverages go-winio, but does not have the appropriate build tags itself, which causes it to build with undefined symbols. This is unfortunately halting our test suite as a result.
Please let me know if this is unacceptable, how I can make it acceptable.
Thanks!
cc @runcom @mtrmac