> For the complete documentation index, see [llms.txt](https://movement.gitbook.io/movement/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://movement.gitbook.io/movement/setup-movement-env.md).
# Setup Movement Env
## Building From Source
Binary releases are available, but if you want to build from source or develop on the Aptos tools, this is how.
### Supported operating systems
Aptos can be built on various operating systems, including Linux, macOS. and Windows. Aptos is tested extensively on Linux and macOS, and less so on Windows. Here are the versions we use:
* Linux - Ubuntu version 20.04 and 22.04
* macOS - macOS Monterey and later
* Microsoft Windows - Windows 10, 11 and Windows Server 2022+
### Clone the movement-subnet repo
1. Install [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). Git is required to clone the aptos-core repo, and will be need to be installed prior to continuing. You can install it with the instructions on the official [Git website](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
2. Clone the Aptos repository. To clone the Aptos repository (repo), you first need to open a command line prompt (Terminal on Mac / Linux, Powershell on Windows). Then run the following command to clone the Git repository from GitHub.
```
git clone https://github.com/movemntdev/movement-subnet
```
3. Now let's go into the newly created directory movement-subnet by *changing directory* or `cd`ing into it:
```
cd movement-subnet/vm/aptos-vm
```
### Set up build dependencies
Prepare your developer environment by installing the dependencies needed to build, test and inspect Aptos Core. No matter your selected mechanism for installing these dependencies, **it is imperative you keep your entire toolchain up-to-date**. If you encounter issues later, update all packages and try again.
macOS
**> Using the automated script**
1. Ensure you have `brew` package manager installed:
2. Run the dev setup script to prepare your environment: `./scripts/dev_setup.sh`
3. Update your current shell environment: `source ~/.cargo/env`.
:::tip You can see the available options for the script by running `./scripts/dev_setup.sh --help` :::
**> Manual installation of dependencies**
If the script above doesn't work for you, you can install these manually, but it's **not recommended**.
1. [Rust](https://www.rust-lang.org/tools/install)
2. [CMake](https://cmake.org/download/)
3. [LLVM](https://releases.llvm.org/)
4. [LLD](https://lld.llvm.org/)
Linux
**> Using the automated script**
1. Run the dev setup script to prepare your environment: `./scripts/dev_setup.sh`
2. Update your current shell environment: `source ~/.cargo/env`
:::tip You can see the available options for the script by running `./scripts/dev_setup.sh --help` :::
**> Manual installation of dependencies**
If the script above does not work for you, you can install these manually, but it is **not recommended**:
1. [Rust](https://www.rust-lang.org/tools/install).
2. [CMake](https://cmake.org/download/).
3. [LLVM](https://releases.llvm.org/).
4. [libssl-dev](https://packages.ubuntu.com/bionic/libssl-dev) and [libclang-dev](https://packages.ubuntu.com/bionic/libclang-dev)
Windows
**> Using the automated script**
1. Open a PowerShell terminal as an administrator.
2. Run the dev setup script to prepare your environment: `PowerShell -ExecutionPolicy Bypass -File ./scripts/windows_dev_setup.ps1`
**> Manual installation of dependencies**
1. Install [Rust](https://www.rust-lang.org/tools/install).
2. Install [LLVM](https://releases.llvm.org/). Visit their GitHub repository for the [latest prebuilt release](https://github.com/llvm/llvm-project/releases/tag/llvmorg-15.0.7).
3. Install [Microsoft Visual Studio Build Tools for Windows](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022). During setup, select "Desktop development with C++" and three additional options: MSVC C++ build tools, Windows 10/11 SDK, and C++ CMake tools for Windows.
4. If on Windows ARM, install [Visual Studio](https://visualstudio.microsoft.com/vs).
5. If not already installed during Visual Studio/Build Tools installation, install [CMake](https://cmake.org/download/).
6. Open a new PowerShell terminal after installing all dependencies
#### Additional Tools
If you used `scripts/dev_setup.sh` for MacOS or Linux setup, additional tools are optionally available.
**TypeScript**
Typically only needed for *developing* the TypeScript SDK. Using the released SDK can be achieved from npm/pnpm/yarn.
```bash
scripts/dev_setup.sh -J
```
**PostgreSQL**
Used in the Indexer.
```bash
scripts/dev_setup.sh -P
```
**Move Prover Tools**
```bash
scripts/dev_setup.sh -y -p
```
Now your basic Aptos development environment is ready. Head over to our Developer Tutorials to get started in Aptos.
####
```bash
cd movement-subnet/vm/aptos-vm/subnet
cargo build --release
# will out put the Binary at movement-subnet/vm/aptos-vm/target/release/subnet
# move this binary to a special directory
cd ~
mkdir move-plugins
cp movement-subnet/vm/aptos-vm/target/release/subnet move-plugins/qCP4kCDiJK6WS5ShMwktmd2zC8gkBkGU1LphErfeSMuHSKLuL
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://movement.gitbook.io/movement/setup-movement-env.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.