1
0
mirror of https://github.com/valinet/ExplorerPatcher.git synced 2024-11-14 19:17:35 +01:00

Updated README with clearer compilation instructions

This commit is contained in:
Valentin Radu 2021-11-02 02:14:29 +02:00
parent 0835675e61
commit e167cfdc91

View File

@ -127,6 +127,8 @@ Hooking is done using the excellent [funchook](https://github.com/kubo/funchook)
## Compiling
If you encounter some issues when following the steps below, or should you want to find out more information and the latest tips from other users/me regarding how to pull this off, consult the relevant thread in Discussions located [here](https://github.com/valinet/ExplorerPatcher/discussions/190).
The following prerequisites are necessary in order to compile this project:
* Microsoft C/C++ Optimizing Compiler - this can be obtained by installing either of these packages:
@ -164,7 +166,7 @@ Steps:
If "cmake" is not found as a command, type its full path, or have its folder added to PATH.
Type "Win32" instead of "x64" above, if compiling for x86. The command above works for x64.
Type "Win32" instead of "x64" above, if compiling for x86 (IA-32). The command above works for x64 (amd64).
Now, in the `libs\funchook\build` folder, open the file `funchook-static.vcxproj` with any text editor, search and replace all occurences of `<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>` with `<RuntimeLibrary>MultiThreaded</RuntimeLibrary>`.
@ -176,23 +178,25 @@ Steps:
3. Compile ExplorerPatcher
* Double click the ExplorerPatcher.sln to open the solution in Visual Studio. Choose Release and your processor architecture in the toolbar. Press F6 to compile.
* Double click the `ExplorerPatcher.sln` file to open the solution in Visual Studio. Choose Release and your processor architecture in the toolbar. Press `[Ctrl]`+`[Shift]`+`[B]` or choose "Build" - "Build solution" to compile.
* Open an "x86 Native Tools Command Prompt for VS 2019" (for x86), or "x64 Native Tools Command Prompt for VS 2019" (for x64) (search that in Start), go to folder containing solution file and type:
* For x86:
```
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=x86
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=IA-32
```
* For x64:
```
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=x64
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=amd64
```
The resulting exe and dll will be in "Release" folder (if you chose x86), or "x64\Release" (if you chose x64) in the folder containing the solution file.
Debug builds mostly work as well, although they may have some quirks or issues. I mostly test the software as release builds.
The resulting libraries will be in the "build\Release" folder in the folder containing the solution file.
That's it. later, if you want to recompile, make sure to update the repository and the submodules first: