Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post Reply
abdelghani
Posts: 7
Joined: 2013-05-19 18:47

Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post by abdelghani »

Hallo to verybody,
I am trying to build the code source ultravnc-code-813-vncviewer on Win7 + VS2012 Ultimate, after setting my environment, I could build: libjpeg-turbo-win, omnithread, rdr, unz32lib, zip32 and zlibstat but I could not build: vncviewer

I am getting:

1>------ Build started: Project: vncviewer, Configuration: Release x64 ------
1> DSMPlugin.cpp
1>..\DSMPlugin\DSMPlugin.cpp(499): error C2661: 'omni_mutex_lock::omni_mutex_lock' : no overloaded function takes 2 arguments
========== Build: 0 succeeded, 1 failed, 6 up-to-date, 0 skipped ==========

It will be great if someone helps me and shows to me what I am missing.

Many thanks in advance.

Regards
Ghani
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6865
Joined: 2004-04-23 10:21
Contact:

Re: Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post by Rudi De Vos »

Did you used the vncviewerv11.sln prject ( vS 2012) ?

#ifdef _VIEWER
omni_mutex_lock l(m_TransMutex);
#else
omni_mutex_lock l(m_TransMutex,105); <<<<<<<<<<no overloaded function takes 2 arguments
#endif

Looks like _VIEWER is undefined.

Solution
1)
add
#define _VIEWER somewere in the src
2)
Or the proper way
add _VIEWER in the project property ->c++->Preprocessor

Code: Select all

NDEBUG
WIN32
_WINDOWS
__NT__
_WINSTATIC
__WIN32__
_CRT_SECURE_NO_WARNINGS
_X64
_VNCVIEWER
_VIEWER
The extra argument is just used to debug dead locks, as last result you always can replace
omni_mutex_lock l(m_TransMutex,105); by omni_mutex_lock l(m_TransMutex);
It doesn't change any functionality
abdelghani
Posts: 7
Joined: 2013-05-19 18:47

Re: Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post by abdelghani »

Hallo Rudi,
thanks a lot for your quick feedback.

Yes, I am using the vncviewerv11.sln prject ( vS 2012).

With your fix I can build the vncviewer with Configuration: Debug x64 without any issue.

I have two remarks:

1- When I open the project, I see :

F:\UltraVNC\ultravnc-code-813\UltraVNC Project Root\UltraVNC\zlib-1.2.5\contrib\vstudio\vc10\zlibstatv11.vcxproj : warning : Platform 'Itanium' referenced in the project file 'zlibstat' cannot be found.


2- If I set the project with Configuration: Release x64, I got:

2>------ Build started: Project: vncviewer, Configuration: Release x64 ------
2> buildtime.cpp
2>F:\UltraVNC\ultravnc-code-813\UltraVNC Project Root\UltraVNC\vncviewer\buildtime.cpp : fatal error C1083: Cannot open compiler generated file: 'Release\buildtime.obj': No such file or directory
2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(129,5): error MSB3073: The command "cl /nologo /MT /FoRelease\ /FdRelease\ /c buildtime.cpp
2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(129,5): error MSB3073: :VCEnd" exited with code 1.


Many thanks

My regards
Abdelghani
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6865
Joined: 2004-04-23 10:21
Contact:

Re: Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post by Rudi De Vos »

Ignore titanium, we don't have that cpu support

buildtime.h isn't generated with X64 release, could be some path issue.
Try to build x86 first -> buildtime.h is created -> X86 OK
abdelghani
Posts: 7
Joined: 2013-05-19 18:47

Re: Building vncviewer - 1.1.9.3 on Win7 + VS2012 Ultimate

Post by abdelghani »

Hi,
I confirm that:
Debug Win32 -> OK
Release Win32 -> OK

Debug Win64 -> OK
Release Win64 -> OK

Thanks
Ghani
Post Reply