Skip to content
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

build failure of dsl-gui on macos monterey with go 1.19.4 #9

Closed
moeller0 opened this issue Jan 5, 2023 · 3 comments
Closed

build failure of dsl-gui on macos monterey with go 1.19.4 #9

moeller0 opened this issue Jan 5, 2023 · 3 comments

Comments

@moeller0
Copy link

moeller0 commented Jan 5, 2023

I seem to run into some issue when building dsl-gui (the CLI version compiles just fine)

bash-3.2$ go build -o dsl ./cmd
bash-3.2$ go build -tags gui -o dsl-gui ./cmd
# github.com/webview/webview
../../../go/pkg/mod/github.com/webview/webview@v0.0.0-20230102133235-36bbd1c79ac6/webview.go:15:10: fatal error: 'stdlib.h' file not found
#include <stdlib.h>
         ^~~~~~~~~~
1 error generated.
bash-3.2$ go version
go version go1.19.4 darwin/amd64

This is probably a pilot's error from my side, but maybe you have an idea how I could fix this?

@moeller0 moeller0 changed the title build failure on macos monteret witg go 1.19.4 build failure of dsl-gui on macos monterey with go 1.19.4 Jan 5, 2023
@janh
Copy link
Owner

janh commented Jan 5, 2023

It looks like this issue usually occurs when using a compiler other than the one from Xcode (as a result of headers no longer being installed to /usr/include for some time now). Maybe the comments on the issues golang/go#39232 and golang/go#27921 are useful to solve it?

@moeller0
Copy link
Author

moeller0 commented Jan 5, 2023

Ah, one other package (FSL) I installed dragged in its own clang and "helpfully" added itself earlier in the path. Sorry for the confusion and thanks for the help.
Now how do I fix this....

@moeller0
Copy link
Author

moeller0 commented Jan 6, 2023

Yepp, I needed to modify my PATH to put /usr/bin before the offending application's path. A solution shown in your links, so I am closing this, as you solved it even though it was my own un-doing.... ;)

@moeller0 moeller0 closed this as completed Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants