Shared library builds fails, if header file is missing, #6209
Closed
jkroepke
started this conversation in
Ideas, Issue Triage, and General discussions
Replies: 2 comments 5 replies
-
|
I'm also having this issue that prevents me from using goreleaser in my project—in my case, it doesn't make sense to publish a header with the shared library because it's irrelevant to end users. I couldn't figure out a way to skip adding the header or skip uploading it to release. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Problem seems to be here: goreleaser/internal/builders/golang/build.go Lines 285 to 292 in 9e21891 When is it correct to actually also add the header? 🤔 Or maybe we should simply check if such file exists before adding it? 🤔 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In my case I'm building a c-shared artifact which does not generate a .h file. I can reproduce that with a simple go build -buildmode=c-shared. No header files are present.
However, in go releaser they seems mandatory.
Config: https://github.com/jkroepke/openvpn-auth-oauth2/blob/f4922018c377c64bb4989ca90131b7e681b3b323/.goreleaser.yaml
Beta Was this translation helpful? Give feedback.
All reactions