virgil: depend on x86_64

[iMichka]

See VirgilSecurity/virgil-cli#58

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[Wink35]

R

[cho-m]

Looks like they compile their C library and package it for various OS/hardware: https://github.com/VirgilSecurity/virgil-sdk-go/tree/master/crypto/wrapper/pkg

They did add support for M1 in C library (https://github.com/VirgilSecurity/virgil-crypto-c/releases/tag/v0.16.0) but still need to update their wrappers/Go code & cut a new release.

Not sure if we can build the C library and link to it ourselves (and hard to tell if there are any other possible issues that need to be addressed to make code ARM-compatible).

---

EDIT: It is possible to build virgil-crypto-c on M1 and then link libraries to virgil via CGO_LDFLAGS. Whether this will cause issues though is hard to tell without testing since upstream builds specific versions of static libraries.

[SMillerDev]

Let's go with this, and we can always fix it later

[BrewTestBot]

🤖 A scheduled task has triggered a merge.