ARTICLE AD BOX
I am trying to build Kismet Debugger for the UE4SS tool as described in the Kismet Debugger's readme.md file, but I am running into difficulties.
I have tried using x64 Native Build Tools Command Prompt for Visual Studio 2022 (my platform is Windows 10, btw), but due to the numerous errors I have encountered, I am beginning to believe that I might have set something up incorrectly.
Cloning the repository goes well. No issues here. The problems begin when I try to generate the project.
Each time I attempt to generate the project for ninja using the exact command described in the readme.md file, I get the following error:
CMake Error at build/_deps/corrosion-src/cmake/FindRust.cmake:23 (message): Could not find toolchain '' Available toolchains: `stable-x86_64-pc-windows-gnu` `stable-x86_64-pc-windows-msvc` `1.46-x86_64-pc-windows-msvc` Call Stack (most recent call first): build/_deps/corrosion-src/cmake/FindRust.cmake:461 (_findrust_failed) build/_deps/corrosion-src/cmake/Corrosion.cmake:34 (find_package) build/_deps/corrosion-src/CMakeLists.txt:33 (include)This is already seemingly unexpected behavior for the project to be producing. But if I choose to try and push through this error by setting the default rust toolchain to nightly and installing the latest stable release, and finally, using the following command:
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DRust_COMPILER="C:\Users\John\.cargo\bin\rustc.exe" -DRust_CARGO="C:\Users\John\.cargo\bin\cargo.exe" -DRust_TOOLCHAIN="stable-x86_64-pc-windows-msvc" -DRust_CARGO_TARGET_LINK_NATIVE_LIBS="kernel32;ntdll;userenv;ws2_32;dbghelp;msvcrt"(This also fixes another error I get where Ninja doesn't know how to find the library "/default:msvcrt")
Trying to build with the aforementioned "fixes" will then generate a ton more errors. Here is an example of one of the errors it generates:
This seems to suggest that the project needs to be compiled via Visual Studio, or some other compiler that is capable of easily providing preprocessor options that the kismet-debugger project doesn't seem to mention.
Of course, testing this and copying the source code only for the kismet-debugger project (dllmain.cpp, KismetDebugger.cpp, and KismetDebugger.hpp), then setting up a new mod project following the guideline described here successfully compiles the project. But if this is the case, then why does the github project mention using command line arguments to assemble the project if it requires Visual Studio and an entirely different file structure?
I believe that I am doing something wrong or have not set something up correctly, but I am unsure of what to do in order to build the project as mentioned in the readme. How do I set up the project in order to build it on my Windows 10 machine as mentioned in the readme?
Just in case this info is needed, this is the dev document, and this is the normal document for creating a c++ mod like the Kismet Debugger is.
