![]() You could try the same solution when building winvnc and friends. Additionally, ThinLinc has proprietary parts which orchestrate the interaction between the components. ThinLinc is based on open-source components, which are at the core of the product. ThinLinc is a stable and mature Linux Remote Desktop Server developed by Cendio since 2003. If I explicitly add -ladvapi to my linker flags, then it imports the symbol from ADVAPI32 and Windows 7 stops complaining. TigerVNC is part of ThinLinc - the Linux Remote Desktop Server. It seems that mingw >= 7.0.0 has a CreateProcessAsUser definition in KERNE元2 and so mingw is importing it from that library, but that symbol is not present on Windows 7. I'm not entirely sure what changed, but it seems like a link order problem, because in my project I was never explicitly linking with the ADVAPI32 import library. Long story short, after a bit of effort bisecting mingw releases using Fedora, I found that something changed between 6.0.0 and 7.0.0 that resulted in CreateProcessAsUser getting imported from KERNE元2 rather than ADVAPI32. I had been building using Fedora 27 and mingw64 5.0.2 In my case, the failures started when I upgraded my build environment to Fedora 36, which ships mingw64 9.0.0. ![]() ![]() It shows many live remote desktops together, allowing. I received the same error on Windows 7 for a project that I build using mingw64 that also calls CreateProcessAsUser. Need Monitoring and Managing Many VNC Remote Desktops Try MightyViewer, our Multi VNC Viewer for Windows. The latest release of TigerVNC can be downloaded from our GitHub release page. ![]()
0 Comments
Leave a Reply. |