Cool_Tools/ExplorerPatcher
1
0
Fork 0
mirror of https://github.com/valinet/ExplorerPatcher.git synced 2025-02-17 11:08:41 +01:00
Code Releases Wiki Activity

Updated for changes to the build process involving ARM64

Amr Satrio 2024-11-16 23:37:45 +07:00
parent 17b373ae81
commit 65c028408e
1 changed files with 12 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
Compiling.md

@ -13,7 +13,7 @@ The following prerequisites are necessary in order to compile this project:
Download either of those [here](http://go.microsoft.com/fwlink/p/?LinkId=840931). The guide assumes you have installed either Visual Studio 2022 or Build Tools for Visual Studio 2022.
* A recent version of the [Windows SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/) - for development, version 10.0.19041.0 is used, available [here](https://go.microsoft.com/fwlink/p/?linkid=2120843) (this may also be offered as an option when installing Visual Studio). The automated infrastructure usually uses the latest SDK available, currently 10.0.22000, available [here](https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/)
* A recent version of the [Windows SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/) - for development, version 10.0.22621 is used (this may also be offered as an option when installing Visual Studio). The automated infrastructure usually uses the latest SDK available, currently 10.0.22621.
* [CMake](https://cmake.org/) - for easier usage, make sure to have it added to PATH during installation
@ -38,37 +38,29 @@ Steps:
nuget restore ExplorerPatcher.sln
```
3. Compile funchook (type this in a PowerShell window):
```
cd libs
cd funchook
md build
cd build
cmake -G "Visual Studio 17 2022" -A x64 -DFUNCHOOK_CPU=x86 ..
(gc .\funchook-static.vcxproj) -replace '<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>', '<RuntimeLibrary>MultiThreaded</RuntimeLibrary>' | Out-File .\funchook-static.vcxproj
cmake --build . --config Release
```
3. Compile dependencies by running `BuildDependenciesRelease.bat` or `BuildDependenciesDebug.bat` located in the root folder of the repository.
4. Compile ExplorerPatcher
* 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:
* Open "x64 Native Tools Command Prompt for VS 2022" or "ARM64 Native Tools Command Prompt for VS 2022" (search that in Start), go to folder containing solution file and type:
* For x86:
* For x64 (Intel, AMD):
```
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=IA-32
```
* For x64:
```
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=amd64
```
Debug builds mostly work as well, although they may have some quirks or issues. I mostly test the software as release builds.
* For ARM64 (Snapdragon):
```
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=IA-32
msbuild ExplorerPatcher.sln /property:Configuration=Release /property:Platform=arm64
```
Debug builds mostly work as well, although they may have some quirks or issues. We mostly test the software as release builds.
The resulting libraries will be in the "build\Release" or "build\Debug" folder in the directory containing the solution file.