Kagami/go-face

macOS build errors

Opened this issue · 4 comments

When i run go get github.com/Kagami/go-face, I get a bunch of errors pertaining to the files in the go-face folder

tpoxa commented

Its normal behavior. go get builds the library after fetching it.
As go-face its a cgo library you need to install additional softwate which described within requirements https://github.com/Kagami/go-face#requirements.

I have installed all the necessary requirements. The errors show, but the go-face folder is copied to my GOPATH. When I run main.go, I get the same errors.

The first couple lines are:
'''
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:134:25: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:134:25: note: insert '_Nullable' if the pointer may be null
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:134:25: note: insert '_Nonnull' if the pointer should never be null
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:135:22: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:135:22: note: insert '_Nullable' if the pointer may be null
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:135:22: note: insert '_Nonnull' if the pointer should never be null
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/us
'''

tpoxa commented

Actually I was not unable to build this library on MacOS either. But I had completely different error list. So I decided to make builds in Docker. I published docker files here #3