-
-
Notifications
You must be signed in to change notification settings - Fork 668
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
go 1.13 compat #2133
Comments
If I do:
Perhaps it's linked to the |
I can repro with stock go:
Removing
|
Adding |
On go 1.12:
|
Thanks for analyzing this. This looks like a bug in rules_go. I'll fix it before go1.13 is officially released, but probably not before rules_go 0.19.0 is released. |
Thank you ! |
@jayconrod how would you go about fixing it? have gazelle generate |
I won't be able to look at it today, but I think |
Go 1.13 is stricter on the package path passed to go tool compile -p. This means that go_library passed in go_binary.embed fails to declare a main.main function, as they now retain their original import path. Fix that by adding a is_main boolean to the GoLibrary provider, which will tell wether a library is supposed to be a main package; that is, compiled from within a go_binary. Fixes #2133
) Go 1.13 is stricter on the package path passed to go tool compile -p. This means that go_library passed in go_binary.embed fails to declare a main.main function, as they now retain their original import path. Fix that by adding a is_main boolean to the GoLibrary provider, which will tell wether a library is supposed to be a main package; that is, compiled from within a go_binary. Fixes bazel-contrib#2133
What version of rules_go are you using?
master
as of todayWhat version of gazelle are you using?
master
as of todayWhat version of Bazel are you using?
0.25.3
What operating system and processor architecture are you using?
darwin_amd64
What did you do?
When using Go 1.13b1:
What did you see instead?
The text was updated successfully, but these errors were encountered: