From 2b72e348561bd4696d3e44ca3b855fe565106c64 Mon Sep 17 00:00:00 2001 From: kraibse <33869366+kraibse@users.noreply.github.com> Date: Sat, 31 Oct 2026 12:40:52 +0100 Subject: Update documentation from Eden to Eglantine Updated the clone URL, binary names and some references to Eden itself. --- docs/Build.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) (limited to 'docs') diff --git a/docs/Build.md b/docs/Build.md index 84a3784fc0..edc9789299 100644 --- a/docs/Build.md +++ b/docs/Build.md @@ -1,9 +1,9 @@ -# Building Eden +# Building Eglantine > [!WARNING] > This guide is intended for developers ONLY. If you are not a developer or packager, you are unlikely to receive support. -This is a full-fledged guide to build Eden on all supported platforms. +This is a full-fledged guide to build Eglantine on all supported platforms. If you already have a development environment set up: @@ -20,11 +20,11 @@ First, you must [install some dependencies](Deps.md). ## Clone -Next, you will want to clone Eden via the terminal: +Next, you will want to clone Eglantine via the terminal: ```sh -git clone https://git.eden-emu.dev/eden-emu/eden.git -cd eden +git clone https://github.com/Djihads80/Eglantine.git +cd Eglantine ``` Or use Qt Creator (Create Project -> Import Project -> Git Clone). @@ -47,7 +47,7 @@ This is the recommended GUI method for Linux, macOS, and Windows. > [!WARNING] > On MSYS2, to use Qt Creator you are recommended to *also* install Qt from the online installer, ensuring to select the "MinGW" version. -Open the CMakeLists.txt file in your cloned directory via File -> Open File or Project (Ctrl+O), if you didn't clone Eden via the project import tool. +Open the CMakeLists.txt file in your cloned directory via File -> Open File or Project (Ctrl+O), if you didn't clone Eglantine via the project import tool. Select your desired "kit" (usually, the default is okay). RelWithDebInfo or Release is recommended: @@ -66,7 +66,7 @@ Hit "Configure Project", then wait for CMake to finish configuring (may take a w >For all systems: > >- *CMake* **MUST** be in your PATH (and also *ninja*, if you are using it as ``) ->- You *MUST* be in the cloned *Eden* directory +>- You *MUST* be in the cloned *Eglantine* directory > >On Windows: > @@ -135,12 +135,12 @@ cmake -S . -B build -G "" -DCMAKE_C_COMPILER=clang-cl -DCMAKE_CXX_COM - Click OK; now CLion will build a directory and index your code to allow for IntelliSense. Please be patient. -- Once this process has been completed (No loading bar bottom right), you can now build Eden -- In the top right, click on the drop-down menu, select all configurations, then select Eden +- Once this process has been completed (No loading bar bottom right), you can now build Eglantine +- In the top right, click on the drop-down menu, select all configurations, then select Eglantine -- Now run by clicking the play button or pressing Shift+F10, and Eden will auto-launch once built. +- Now run by clicking the play button or pressing Shift+F10, and Eglantine will auto-launch once built. @@ -186,10 +186,10 @@ cmake --build build Your compiled executable will be in: -- `build/bin/eden.exe` for Windows, -- `build/bin/eden.app/Contents/MacOS/eden` for macOS, -- and `build/bin/eden` for others. +- `build/bin/eglantine.exe` for Windows, +- `build/bin/Eglantine.app/Contents/MacOS/eglantine` for macOS, +- and `build/bin/eglantine` for others. ## Scripts -Take a look at our [CI scripts](https://github.com/Eden-CI/Workflow). You can use `.ci/common/configure.sh` on any POSIX-compliant shell, but you are heavily encouraged to instead write your own based. It's not really that hard, provided you can read CMake. +Take a look at our [CI scripts](https://github.com/Eglantine-CI/Workflow). You can use `.ci/common/configure.sh` on any POSIX-compliant shell, but you are heavily encouraged to instead write your own based. It's not really that hard, provided you can read CMake. -- cgit v1.2.3