Evaluate binclude.Include based on build tags about binclude HOT 6 CLOSED

Good idea currently it doesn't work, will add support.

from binclude.

PRs which improve the docs are welcome 👍

from binclude.

@audiolion I now added support for implicit filename based build tags like file_linux.go, file_windows.go, file_darwin_arm.go

From the build documentation:

If a file's name, after stripping the extension and a possible _test suffix, matches any of the following patterns:

*_GOOS
*_GOARCH
*_GOOS_GOARCH

(example: source_windows_amd64.go) where GOOS and GOARCH represent any known operating system and architecture values respectively, then the file is considered to have an implicit build constraint requiring those terms (in addition to any explicit constraints in the file).

from binclude.

Thanks for the fast turnaround. I will try it out next week at work. Would you like a PR to document the feature? I don't think other embeds like go.rice, packr/pkger, have this feature.

from binclude.

Actually this isn't finished yet. I could generate different files like binclude_windows.go binclude_linux.go binclude_darwin.go, this would allow embeddding different files for each os and avoid the need to regenerate the file when the platform changes.

from binclude.

Done

from binclude.