[Feature Request] Add Movement CLI to Homebrew

[shayansanjideh]

Currently the only way to install the Movement binaries is to install from source, which can fail sometimes as the team is making changes. Adding the Movement binaries to Homebrew would help solve this

[0xmovses]

This was something @andygolay had started on many moons ago. Agreed, we defo want this. Did you face any blockers on this Andy?

[andygolay]

Yes Movement CLI was generally deprioritized a month or two ago. It can be prioritized, not sure whether it falls under DevX now or what category of development it would fall under.

[andygolay]

For more context, @Rahat-ch and I met in December and figured out how to create our own tap; it's fairly straightfoward, but we decided it was a "nice to have" given the mainnet push, and given that devs can build the CLI without brew.

Is there much Movement dev community demand for brew installation for Movement CLI @shayansanjideh ?

I've been hearing about devs demanding Move 2 compatibility. I've started looking into it and it seems like it could be a decent lift / quite non-trivial.

At that point, once we've achieved parity with Aptos framework features and bytecode version, then I think it would make sense to go forward with brew installation, unless there's strong community demand for it now.

From what I understand, Movement CLI is able to be installed from source now. I'll look into it to confirm. I know there was an issue with the diesel dependency a month or so ago but I thought that was resolved.

[Rahat-ch]

Based on feedback we've been now getting we do want to get this pushed from the Product side.

There are two things to consider for devex when looking at Move 2 as well as CLI.

Move 2 is mostly requested from builders who are already in the Aptos ecosystem and want to have feature parity for their dapps across both chains. This was discussed at the offiste as being a high priority.

We do additionally see the Movement CLI needing to be more accessible as a high priority as well.

Rationale:

• it seems as changes to the codebase sometimes occur it is not always a simple task to install the movement cli - dependency issue you mentioned being an issue for folks for some time
• It is unfortunately not as simple as running brew install aptos @3.5 installing the aptos cli at specific versions requires building from source similar to how we build the movement cli today
• Maintaining two versions locally of the same cli for different versions of the same codebase isn't an ideal UX
• Several builders who are doing Move education workshops have cited this as a friction point and a large time consumption for newcomers into the movement ecosystem

[Rahat-ch]

Some additional items that would be good to ensure we have for smooth devex:

Choosing Mainnet/Testnet should configure endpoints properly for both Bardock and Mainnet - in the case of bardock ensure it also configures the faucet endoint. Currently we have to choose custom and manually enter endpoints.

Next would be ensuring the depencies on Move.Toml are properly set to our fork of aptos core when running movement init. So Move.toml should have:

[dependencies.AptosFramework]
git = "https://github.com/movementlabsxyz/aptos-core.git"
rev = "movement"
subdir = "aptos-move/framework/aptos-framework"

[andygolay]

On it, thanks @Rahat-ch.

[startswithaj]

For more context, @Rahat-ch and I met in December and figured out how to create our own tap; it's fairly straightfoward, but we decided it was a "nice to have" given the mainnet push, and given that devs can build the CLI without brew.

Is there much Movement dev community demand for brew installation for Movement CLI @shayansanjideh ?

I've been hearing about devs demanding Move 2 compatibility. I've started looking into it and it seems like it could be a decent lift / quite non-trivial.

At that point, once we've achieved parity with Aptos framework features and bytecode version, then I think it would make sense to go forward with brew installation, unless there's strong community demand for it now.

Until we're compatible with Move 2, imo devs might as well run brew install aptos@3.5 if they'd like to install a compatible CLI with brew. From what I understand, Movement CLI is able to be installed from source now. I'll look into it to confirm. I know there was an issue with the diesel dependency a month or so ago but I thought that was resolved.

Hi Guys,

I'm trying to install the Movement CLI and hitting this diesel dependency issue. I'm on a Macbook M4.

Is there any resolution to this? Is there any movement on the brew install.

There is no such thing as brew install aptos@3.5 unfortunately.

Cheers and apologies for highjacking this thread for support. @andygolay @Rahat-ch

[andygolay]

For more context, @Rahat-ch and I met in December and figured out how to create our own tap; it's fairly straightfoward, but we decided it was a "nice to have" given the mainnet push, and given that devs can build the CLI without brew.
Is there much Movement dev community demand for brew installation for Movement CLI @shayansanjideh ?
I've been hearing about devs demanding Move 2 compatibility. I've started looking into it and it seems like it could be a decent lift / quite non-trivial.
At that point, once we've achieved parity with Aptos framework features and bytecode version, then I think it would make sense to go forward with brew installation, unless there's strong community demand for it now.
Until we're compatible with Move 2, imo devs might as well run brew install aptos@3.5 if they'd like to install a compatible CLI with brew. From what I understand, Movement CLI is able to be installed from source now. I'll look into it to confirm. I know there was an issue with the diesel dependency a month or so ago but I thought that was resolved.

Hi Guys,

I'm trying to install the Movement CLI and hitting this diesel dependency issue. I'm on a Macbook M4.

Is there any resolution to this? Is there any movement on the brew install.

There is no such thing as brew install aptos@3.5 unfortunately.

Cheers and apologies for highjacking this thread for support. @andygolay @Rahat-ch

Ah sorry @startswithaj my mistake about the Aptos 3.5 brew install.

I just tried building and got this as well:

   Compiling aptos-indexer-grpc-server-framework v1.0.0 (/Users/andygmove/Downloads/repos/aptos-core/ecosystem/indexer-grpc/indexer-grpc-server-framework)
   Compiling self_update v0.39.0 (https://github.com/banool/self_update.git?rev=8306158ad0fd5b9d4766a3c6bf967e7ef0ea5c4b#8306158a)
For more information about this error, try `rustc --explain E0308`.
error: could not compile `diesel` (lib) due to 5 previous errors
warning: build failed, waiting for other jobs to finish...
warning: `aptos-indexer-grpc-utils` (lib) generated 1 warning

I'll look into it and see if we can come up with a patch this week.

[andygolay]

For more context, @Rahat-ch and I met in December and figured out how to create our own tap; it's fairly straightfoward, but we decided it was a "nice to have" given the mainnet push, and given that devs can build the CLI without brew.
Is there much Movement dev community demand for brew installation for Movement CLI @shayansanjideh ?
I've been hearing about devs demanding Move 2 compatibility. I've started looking into it and it seems like it could be a decent lift / quite non-trivial.
At that point, once we've achieved parity with Aptos framework features and bytecode version, then I think it would make sense to go forward with brew installation, unless there's strong community demand for it now.
Until we're compatible with Move 2, imo devs might as well run brew install aptos@3.5 if they'd like to install a compatible CLI with brew. From what I understand, Movement CLI is able to be installed from source now. I'll look into it to confirm. I know there was an issue with the diesel dependency a month or so ago but I thought that was resolved.

Hi Guys,

I'm trying to install the Movement CLI and hitting this diesel dependency issue. I'm on a Macbook M4.

Is there any resolution to this? Is there any movement on the brew install.

There is no such thing as brew install aptos@3.5 unfortunately.

Cheers and apologies for highjacking this thread for support. @andygolay @Rahat-ch

I downgraded the bigdecimal package version and got movement to build. You can try this branch: #154

If you test it, please me know how it goes?

[andygolay]

I think Homebrew itself isn't going to be the answer here given that this is a bit of of a stopgap measure for the current version of aptos-core we're working with and the main goal is just to give users a fast prebuilt movement binary installation. (Solution I worked out is below the issues I'll list.)

If I override the aptos-core rust-toolchain so it uses the latest stable version, cargo install --path crates/aptos --bin movement builds successfully, but brew install --build-bottle ./movement.rb fails based on some dep incompatibility involving the time crate.

When I try to build bottles I keep getting this error

Error: Failed to load cask: ./movement.rb
Cask 'movement' is unreadable: wrong constant name #<Class:0x00000001484f96a8>
Warning: Treating ./movement.rb as a formula.
==> Fetching movement
==> Downloading file:///Users/andygmove/Downloads/repos/aptos-core/movement-cli-v3.5.tar.gz
Already downloaded: /Users/andygmove/Library/Caches/Homebrew/downloads/84206f793d293c46fc769a8d79c358bffda3e8a55c1122e97cb01b49fbeccf75--movement-cli-v3.5.tar.gz
==> cargo install --path=crates/aptos --bin movement
Last 15 lines from /Users/andygmove/Library/Logs/Homebrew/movement/01.cargo:

   Compiling uncased v0.9.9
   Compiling typed-arena v2.0.2
   Compiling base64ct v1.6.0
   Compiling pasta_curves v0.5.1
   Compiling libsecp256k1-gen-ecmult v0.3.0
   Compiling libsecp256k1-gen-genmult v0.3.0
   Compiling fail v0.5.1
   Compiling tiny-keccak v2.0.2
For more information about this error, try `rustc --explain E0282`.
error: could not compile `time` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
warning: `move-core-types` (lib) generated 7 warnings
error: failed to compile `movement v3.5.0 (/private/tmp/movement-20250422-11701-6mlias/crates/aptos)`, intermediate artifacts can be found at `/private/tmp/movement-20250422-11701-6mlias/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

basically there's some incompatibility with the "time" dependency when installing with homebrew.

However, cargo install --path crates/aptos --bin movement is working correctly.

Because homebrew should simply work out of the box after we upgrade to full compatibility with aptos-labs/aptos-core, and so this is really just a once-off convenience for devs, and we're not planning to continue hacking brew installations like this (because they should just work out of the box once we're up to date with aptos-core main), I'm thinking what we can do for the sake of giving Mac devs a quick binary install, is test this release I just put up: https://github.com/movementlabsxyz/homebrew-movement-cli/releases/tag/bypass-homebrew

It installs in under 10 seconds with

curl -LO https://github.com/movementlabsxyz/homebrew-movement-cli/releases/download/bypass-homebrew/movement-macos-arm64.tar.gz
tar -xzf movement-macos-arm64.tar.gz
chmod +x movement-macos-arm64                       
sudo mv movement-macos-arm64 /usr/local/bin/movement

You can copy and paste all four of those lines into your terminal and it just does it's thing, similar to Homebrew.

If you guys test that and it works, I'll make the other customizations @Rahat-ch requested above and re-release.

[andygolay]

Some additional items that would be good to ensure we have for smooth devex:

Choosing Mainnet/Testnet should configure endpoints properly for both Bardock and Mainnet - in the case of bardock ensure it also configures the faucet endoint. Currently we have to choose custom and manually enter endpoints.

Next would be ensuring the depencies on Move.Toml are properly set to our fork of aptos core when running movement init. So Move.toml should have:

[dependencies.AptosFramework]
git = "https://github.com/movementlabsxyz/aptos-core.git"
rev = "movement"
subdir = "aptos-move/framework/aptos-framework"

I've implemented these changes and created releases for Mac (both for machines running newer ARM / M-series processors and also the older x86_64 / Intel processors)

Check it out here:

https://github.com/movementlabsxyz/homebrew-movement-cli/releases/tag/bypass-homebrew