From 2cab039a5f0b2565c99f4c08329617e0a2561b55 Mon Sep 17 00:00:00 2001 From: Florian Kaiser Date: Wed, 7 May 2025 21:43:54 +0200 Subject: [PATCH] Add info about long file path issue to README.md (#1442) * Add info about long file path issue to README.md * Update README.md --------- Co-authored-by: Christian Semmler --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index c24dc4ef..9a12cbff 100644 --- a/README.md +++ b/README.md @@ -37,6 +37,7 @@ You will need the following software installed: 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. + - Be aware that long file paths (e.g., `C:\Users\LongUserName\LongerFolderName\isle`) may be truncated by `make`, resulting in “File not found” errors. - 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. While `Debug` builds can be compiled and used, they are not recommended as the primary goal is to match the code to the original binary. This is because the retail binaries were compiled as `Release` builds. - `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`).