From 465a86efabd49aeebd34a4cbfb348e80247837e7 Mon Sep 17 00:00:00 2001 From: LuisYeah1234-hub <64372171+LuisYeah1234-hub@users.noreply.github.com> Date: Wed, 25 Dec 2024 18:20:33 +0100 Subject: [PATCH] Update README (again) [skip ci] --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 81043ad1c8..2a5bb0cef6 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ cmake -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=RelWithDebInfo ``` - **Visual C++ 4.2 has issues with paths containing spaces**. If you get configure or build errors, make sure neither CMake, the repository, nor Visual C++ 4.2 is in a path that contains spaces. - Replace `` with the source repository. This can be `..` if your build folder is inside the source repository. - - `RelWithDebInfo` is recommended because it will produce debug symbols useful for further decompilation work. However, you can change this to `Release` if you don't need them. `Debug` builds may now work with the decompiled version of `LEGO1.DLL`. + - `RelWithDebInfo` is recommended because it will produce debug symbols useful for further decompilation work. However, you can change this to `Release` if you don't need them. `Debug` builds may now work with the decompiled version of `LEGO1.DLL`, However they might still have some bugs or issues. - `NMake Makefiles` is most recommended because it will be immediately compatible with Visual C++ 4.2. For faster builds, you can use `Ninja` (if you have it installed), however due to limitations in Visual C++ 4.2, you can only build `Release` builds this way (debug symbols cannot be generated with `Ninja`). 1. Build the project by running `nmake` or `cmake --build ` 1. When this is done, there should be a recompiled `ISLE.EXE` and `LEGO1.DLL` in the build folder.