-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
compile error #31
Comments
me too !!! |
Closed
You need to install mingw 32 bit and go 32bit for that to work (maybe go 64bit works too, didn't test) Easiest way to install correct mingw32 is to install tdm-gcc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GOROOT=E:/win10soft/go
GOPATH=E:/test/GoProjects/test
E:/win10soft/go\bin\go.exe build -o "C:\Users\jay\AppData\Local\Temp\Build main_win.go and run1go" -gcflags "-N -l" E:/test/cef2go-0.10/src/main_win.go
/E/test/cef2go-0.10/src/cef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible ./../../Release/libcef.lib when searching for -llibcef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible ./../../Release/libcef.dll when searching for -llibcef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible ./../../Release/libcef.lib when searching for -llibcef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible ./../../Release/libcef.dll when searching for -llibcef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible ./../../Release\libcef.lib when searching for -llibcef
e:/win10soft/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.2/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -llibcef
collect2.exe: error: ld returned 1 exit status
The text was updated successfully, but these errors were encountered: