-
-
Notifications
You must be signed in to change notification settings - Fork 145
Building
Nodir Temirkhodjaev edited this page Apr 24, 2022
·
17 revisions
- latest Visual Studio Community Edition or just Build Tools for Visual Studio
- Windows Driver Kit (WDK), same version as Visual Studio's SDK
- latest Qt 6 and QtCreator
Qt 6 can be built from sources by <PATH-TO>\fort\deploy\qt-build.bat
script.
- clone the
https://github.com/google/googletest
somewhere - add Environment variable "GOOGLETEST_DIR" (upper case!) with value of cloned path (i.e. it should contain
googlemock
&googletest
folders)
- Open the
<PATH-TO>\fort\src\FortFirewall.pro
in QtCreator - Select "Release" configuration
- Turn on the "Shadow build"
- Change "Build directory" to
<PATH-TO>\fort\build-win10
- Build it
- The
<PATH-TO>\fort\build-win10\ui_bin\FortFirewall.exe
will be created!
- Open Visual Studio 2022 Tools Command Prompt for targeting x64 ("x64 Native Tools Command Prompt for VS 2022" link)
- Change working directory to driver sources by
cd <PATH-TO>\fort\src\driver
- Run
msvcbuild-win10-64.bat
- The
<PATH-TO>\fort\build-driver-win10\x64\fortfw.sys
will be created!
- Driver is already test signed by default
Turn On Test Signing:
BcdEdit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
BcdEdit.exe -set NOINTEGRITYCHECKS ON
BcdEdit.exe -set TESTSIGNING ON
Turn Off Test Signing:
BcdEdit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
BcdEdit.exe -set NOINTEGRITYCHECKS OFF
BcdEdit.exe -set TESTSIGNING OFF
- Run
<PATH-TO>\fort\deploy\setup-deployment-win10.bat
to make the<PATH-TO>\fort\deploy\build
- Run
<PATH-TO>\fort\deploy\create-installer.bat
- The
<PATH-TO>\fort\deploy\out\FortFirewall-*.exe
will be created!