The process was:
- download the "test app" from cefbuilds.com for CEF 3.1750.1625. This is actually the part most likely to go wrong. On cefbuilds.com there are branches, builds, platforms, and then for each one there is the library, the test app, and the debug/release symbols. You want branch 1750 build 1625, OSX 64-bit, and the Test App. The file you eventually download should be named "cef_binary_3.1750.1625_macosx64_client.7z".
Now uncompress and rename all the "cefclient" things to "cef2go":
$ 7z x cef_binary_3.1750.1625_macosx64_client.7z
$ cd cef_binary_3.1750.1625_macosx64_client/Release
$ mv cefclient.app cef2go.app
$ cd cef2go.app/Contents/Frameworks/
$ mv cefclient\ Helper.app cef2go\ Helper.app
$ cd cef2go\ Helper.app/Contents/MacOS
$ mv cefclient\ Helper cef2go\ Helper
Now clone cef2go master and move cef2go.app into the Release dir
$ git clone g...@github.com:cztomczak/cef2go.git
$ mv cef_binary_3.1750.1625_macosx64_client/Release/cef2go.app cef2go/Release
$ cd cef2go
And finally:
$ make
If all goes according to plan you should get a window with a simple HTML file. If you get build errors complaining about architectures then that probably means that your go binary has an architecture different from that of the CEF framework. Try comparing:
$ go version
$ file "Release/cef2go.app/Contents/Frameworks/Chromium Embeddded Framework.framework"
If the window appears but there is no html rendered inside it then that means you got something wrong with the app renaming. Check your terminal output for dlopen failures.