Closed ghost closed 2 years ago
VS 2019 (latest updates 16.11.0 ), WDK - Win10 (10.0.19041.685), please use the SbieRelease/Win32 or SibeRelease/x64, no error .
VS 2019 (latest updates 16.11.0 ), WDK - Win10 (10.0.19041.685), please use the SbieRelease/Win32 or SibeRelease/x64, no error .
VS2019,WDK-Win10 (10.0.19041.685), use SbieDebug,build SboxDrv error LNK2001、LNK2019 error. Please help me and tell me how to deal with this issue
Driver never successfully built in debug already since sophos times, build the driver always as release
Driver never successfully built in debug already since sophos times, build the driver always as release
Thanks David!
modify the SbieDrv source / project SbieDebug/x64, please add the ntstrsafe.lib (Link input lib) SbieDebug/Win32, add the ntstrsafe.lib (Link input lib), and disable the memcmp (mem.c) , then you can build success . //#ifndef _WIN64 //int __cdecl memcmp( // _In_readsbytes(_Size) void const _Buf1, // _In_readsbytes(_Size) void const _Buf2, // In size_t _Size //) //{ // return (RtlCompareMemory(_Buf1, _Buf2, _Size) == _Size) ? 0 : 1; //} //#endif
sbierelease , you can modify the configuration. a . C++ /od b. Link /Debug then ,you can debug the sbiedrv (sbierelease ) .
There was a reason for this memcpy function, i think on win 7 32 bit the driver failed to load without it wheb built with a modern WDK version. So for the debug build in 32 bit just disable intrinsic funtions in the optimisation settings than you can leave this funcrion in
Describe the bug I'm a visual studio newbie trying to compile classic sandboxie from source.
To Reproduce Steps to reproduce the behavior:
Sandboxie.sln
in visual studioWhen I do that, an error dialog appears saying
Common.lib
is not a valid win32 executable. Can you please describe how to get the build pipeline up and running?System details and installed software (please provide the following information):
Additional context My sdk configuration: