how to support android with go-mobile about blst

[dot-asm]

Given the form of the question, you make either of two assumptions, both of which are wrong. You either assume that the community is so large and diverse that somebody would know and have the opportunity to address it. Or that literally anybody would recognize exactly what is the problem and be able to answer the question off the top of their heads:-) Again, both assumptions are unfortunately wrong. While from our side assumption is that you would know what to do, quoting README.md: "respective [Go] users would go about as they would with any other external module." Which appears also wrong in the context?

To summarize, you have to be more specific. What was tried, what was the error message. Best would be if you could provide a minimalist code snippet and compiler command line that fails...

Cheers:-)

[sean-sn]

Any more details on this @mostcute?

[dot-asm]

One can wonder if it's a more general matter of cross-compiling with go. I mean it might be not specific to gomobile. Trouble is that if you try to simply cross-compile blst by setting GOARCH environment variable, you get totally non-descriptive error messages about missing classes defined in blst.go. The keyword for cross-compilation seems to be CGO_ENABLED environment variable set to 1. But then you become liable for setting CC environment variable to appoint cross-compiler for the job. But there is a catch here. Android NDK and Xcode use same compiler command for cross-compilation and specify alternative processor target with -target command line option(*). Which falls beyond CC environment variable. It might happen that gomobile already makes arrangements for passing suitable -target, in which case it might be sufficient to set CGO_ENABLED variable.

(*) Both are simply using clang.