proto
proto copied to clipboard
moonrepo
Install Specific Architecture (arm / x64)
Hey, proto seems to be a really good solution for multiple environments developments. I didn't see an option to choose the architecture of the installed version in the documentation. Is this feature planned?
Bye !
@MatteoGauthier It's not planned at all. The arch is derived from the current machine. What's the use case?
@milesj As a MacBook user, new ARM architecture have caused a lot of issue with nodejs for example. Packages that use native bindings might have some issues on non x64 arch, like node-sass, node-gyp, chokidar, next, prisma, etc… For library authors, choosing architecture can be useful too, like for testing in multiple scenarios. I'm currently looking for a good toolchain manager, that could install multiple versions of node, zig, or python with the ability to choose the CPU architecture. I tried nvm, n, fnm, volta But none of these tools allow installing the same version with several archs.
@MatteoGauthier I didn't get the benefit of doing this, I'm using ARM M1 and no problem with the architecture.
Would it be possible to add aarch64-unknown-linux-gnu as compilation target for supporting ARM64 Linux?
I tried adding proto to an image for a dev container.
(no idea really, but would it suffice to add this here?)
We use cargo-dist to build our binaries and it doesn't support arm64 yet. https://github.com/axodotdev/cargo-dist
@oddcelot Related to this issue:
- https://github.com/axodotdev/cargo-dist/issues/324
Targets info: https://opensource.axo.dev/cargo-dist/book/reference/config.html#targets
Thanks for the update @ImBIOS and @milesj for moving things along with https://github.com/axodotdev/cargo-dist/pull/614
Much appreciated 🙌
So this issue would be resolved then with upgrading cargo-dist to 0.6.0 once released, right?
It'll solve the arm64 problem, but the original issue is still something to be figured out.