|
1 |
| ---- |
2 |
| -layout: default |
3 |
| -title: Installing Geode CLI |
4 |
| -nav_exclude: true |
5 |
| -description: "How to set up Geode CLI" |
6 |
| ---- |
7 |
| - |
8 |
| -# Installing Geode CLI |
9 |
| - |
10 |
| -Geode CLI is the command-line interface for working with Geode, intended mainly for developers. It comes with many important tools such as packaging mods into `.geode` files, creating spritesheets, creating bitmap fonts, etc.. The CLI, if installed, will be automatically invoked by Geode CMake files, so you likely won't need to use it a lot manually; however, for Geode mod development, it is very much recommended to have it installed as you will have to manually create resources and `.geode` files otherwise. |
11 |
| - |
12 |
| -## Downloading CLI |
13 |
| - |
14 |
| -### Latest Release |
15 |
| - |
16 |
| -You can find the latest release of CLI on the [Release page on its repo](https://github.com/geode-sdk/cli). Do note that this release may be a little outdated; please [let us know](/docs/contributing) if it seems to be missing features, and we'll be sure to create a new release. |
17 |
| - |
18 |
| -### Building from source |
19 |
| - |
20 |
| -You can build the CLI yourself using [Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Clone the git repo using `git clone https://github.com/geode-sdk/cli` and then run `cargo build` to build it. Do note that before you can run CLI on Windows, you need to manually move `libgeode.dll` from the `target/debug/deps` directory to `target/debug` (we don't know why Rust doesn't move it for us). You can do this with the command `copy target/debug/deps/libgeode.dll target/debug`. |
21 |
| - |
22 |
| -## Adding CLI to PATH |
23 |
| - |
24 |
| -> :warning: Note: this section is for Windows. |
25 |
| -
|
26 |
| -In order for the CLI to be accessible from anywhere on your computer, it needs to be added to your `PATH` environment variable. If you know what that means, you know how to do it; otherwise, follow these steps: |
27 |
| - |
28 |
| -1. Select the CLI executable in File Explorer, Shift + Right-Click it and select `Copy as Path` |
29 |
| - |
30 |
| -2. Search `Edit the system environment variables` on Windows search. Alternatively, you can open up Control Panel and search for it, then select `Edit the system environment variables` or **to skip straight to step 3 select `Edit environment variables for your account`**. |
31 |
| - |
32 |
| -3. Click `Environment Variables...` |
33 |
| - |
34 |
| -4. In the top `User variables` section, select the `Path` variable and click `Edit` |
35 |
| - |
36 |
| -5. Now click `New` and paste the path of the CLI executable you copied at Step 1. Remove the `\geode.exe` from the end. |
37 |
| - |
38 |
| -6. Click OK to close the environment variable windows. |
39 |
| - |
40 |
| -## Making sure it works |
41 |
| - |
42 |
| -1. Open up Windows search and open `cmd` or `powershell` |
43 |
| - |
44 |
| -2. Type `geode` and hit Enter. If CLI was installed correctly, you should see the CLI help displaying its version and commands. |
45 |
| - |
| 1 | +# Installing Geode CLI |
| 2 | + |
| 3 | +Geode CLI is the command-line interface for working with Geode, intended mainly for developers. It comes with many important tools such as packaging mods into `.geode` files, creating spritesheets, creating bitmap fonts, etc.. The CLI, if installed, will be automatically invoked by Geode CMake files, so you likely won't need to use it a lot manually; however, for Geode mod development, it is very much recommended to have it installed as you will have to manually create resources and `.geode` files otherwise. |
| 4 | + |
| 5 | +## Downloading CLI |
| 6 | + |
| 7 | +### Latest Release |
| 8 | + |
| 9 | +You can find the latest release of CLI on the [Release page on its repo](https://github.com/geode-sdk/cli). Do note that this release may be a little outdated; please [let us know](/docs/contributing) if it seems to be missing features, and we'll be sure to create a new release. |
| 10 | + |
| 11 | +### Building from source |
| 12 | + |
| 13 | +You can build the CLI yourself using [Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Clone the git repo using `git clone https://github.com/geode-sdk/cli` and then run `cargo build` to build it. Do note that before you can run CLI on Windows, you need to manually move `libgeode.dll` from the `target/debug/deps` directory to `target/debug` (we don't know why Rust doesn't move it for us). You can do this with the command `copy target/debug/deps/libgeode.dll target/debug`. |
| 14 | + |
| 15 | +## Adding CLI to PATH |
| 16 | + |
| 17 | +> :warning: Note: this section is for Windows. |
| 18 | +
|
| 19 | +In order for the CLI to be accessible from anywhere on your computer, it needs to be added to your `PATH` environment variable. If you know what that means, you know how to do it; otherwise, follow these steps: |
| 20 | + |
| 21 | +1. Select the CLI executable in File Explorer, Shift + Right-Click it and select `Copy as Path` |
| 22 | + |
| 23 | +2. Search `Edit the system environment variables` on Windows search. Alternatively, you can open up Control Panel and search for it, then select `Edit the system environment variables` or **to skip straight to step 3 select `Edit environment variables for your account`**. |
| 24 | + |
| 25 | +3. Click `Environment Variables...` |
| 26 | + |
| 27 | +4. In the top `User variables` section, select the `Path` variable and click `Edit` |
| 28 | + |
| 29 | +5. Now click `New` and paste the path of the CLI executable you copied at Step 1. Remove the `\geode.exe` from the end. |
| 30 | + |
| 31 | +6. Click OK to close the environment variable windows. |
| 32 | + |
| 33 | +## Making sure it works |
| 34 | + |
| 35 | +1. Open up Windows search and open `cmd` or `powershell` |
| 36 | + |
| 37 | +2. Type `geode` and hit Enter. If CLI was installed correctly, you should see the CLI help displaying its version and commands. |
| 38 | + |
0 commit comments