Synergy-core: Undeclared identifier compile error in VS2017
File src/lib/arch/win32/ArchSystemWindows.cpp at line 144 It contains _ULonglong which I don't really know in which library/sdk it lives, but it's undefined and none of the header files contain its definition.
If replaced with 'long' the solution builds without errors.
Not really sure if that's a bug, so I'm not adding any tags.
EDIT: I don't really remember checking out a branch, so this should be on master.
mohkamfer
All 7 comments
As far as I can tell, the getLibsUsed isn't used. We could just delete that function.
nbolton
on 29 Jul 2018
@mohkamfer Hey, saw a _ULonglong compile error when trying to compile a VS2017 project. Are you also seeing issue #6379?
Severity Code Description Project File Line Suppression State
Error C2065 '_ULonglong': undeclared identifier arch c:\users\nick\projects\synergy-core\src\lib\arch\win32\archsystemwindows.cpp 144
@nbolton Nope didn't encounter that one, just as I fixed the _ULonglong issue all the projects compiled successfully. Maybe this can be related to Windows SDK's version?
On a side note I lost interest in the software as my whole setup is wireless and control stutters and hiccups like there's no tomorrow :angry: so frustrated.
mohkamfer
on 2 Aug 2018
On a side note I lost interest in the software as my whole setup is wireless and control stutters and hiccups like there's no tomorrow 馃槧 so frustrated.
Are you using macOS? https://symless.com/help/s1-troubleshooting/s1-mouse-cursor-lag
nbolton
on 2 Aug 2018
Nope server on Ububtu, client on win tablet
mohkamfer
on 5 Aug 2018
Does the issue go away when using Ethernet? If so, it could be an issue with your WiFi adapter.
nbolton
on 6 Aug 2018
I encountered this error as well (the original issue). I was able to monkey-patch it by replacing "_ULongLong" with "unsigned long long" - it builds just fine. For the context of usage it seems sane: PID's should not be larger than even a regular int. Also this is used for generating message string in whatever context (unlikely to be breaking even in the unlikely event of being faulty).
Didn't yet test this fix in production though.
Built on Win7 x64 with VS2017, cl 19.15.26729
Addendum: uint32 is ok as a substitute. See https://docs.microsoft.com/de-de/windows/desktop/WinProg/windows-data-types and https://msdn.microsoft.com/en-us/library/s3f49ktz.aspx
hmoenck
on 14 Nov 2018
Related issues
Celant
路
4Comments
sangwoo-joh
路
4Comments
bigbear3001
路
4Comments
ColinCreamer
路
5Comments
nbolton
路
5Comments
Most helpful comment
I encountered this error as well (the original issue). I was able to monkey-patch it by replacing "_ULongLong" with "unsigned long long" - it builds just fine. For the context of usage it seems sane: PID's should not be larger than even a regular int. Also this is used for generating message string in whatever context (unlikely to be breaking even in the unlikely event of being faulty).
Didn't yet test this fix in production though.
Built on Win7 x64 with VS2017, cl 19.15.26729
Addendum: uint32 is ok as a substitute. See https://docs.microsoft.com/de-de/windows/desktop/WinProg/windows-data-types and https://msdn.microsoft.com/en-us/library/s3f49ktz.aspx