|
|
@@ -211,8 +211,8 @@ will clean both the Xvnc and vncviewer builds without destroying any of the |
|
|
|
build configuration or module dependencies. |
|
|
|
|
|
|
|
|
|
|
|
Building the TigerVNC Viewer/Server with Visual C++ (Command Line) |
|
|
|
------------------------------------------------------------------ |
|
|
|
Building the Windows TigerVNC Viewer/Server with Visual C++ (Command Line) |
|
|
|
-------------------------------------------------------------------------- |
|
|
|
|
|
|
|
cd {build_directory} |
|
|
|
cmake -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory} |
|
|
@@ -222,8 +222,8 @@ This will build either a 32-bit or a 64-bit version of TigerVNC, depending |
|
|
|
on which version of cl.exe is in the PATH. |
|
|
|
|
|
|
|
|
|
|
|
Building the TigerVNC Viewer/Server with Visual C++ (IDE) |
|
|
|
--------------------------------------------------------- |
|
|
|
Building the Windows TigerVNC Viewer/Server with Visual C++ (IDE) |
|
|
|
----------------------------------------------------------------- |
|
|
|
|
|
|
|
Choose the appropriate CMake generator option for your version of Visual Studio |
|
|
|
(run "cmake" with no arguments for a list of available generators.) For |
|
|
@@ -237,8 +237,8 @@ configurations in that project ("Debug", "Release", etc.) to generate a full |
|
|
|
build of TigerVNC. |
|
|
|
|
|
|
|
|
|
|
|
Building the TigerVNC Viewer with MinGW |
|
|
|
--------------------------------------- |
|
|
|
Building the Windows TigerVNC Viewer with MinGW |
|
|
|
----------------------------------------------- |
|
|
|
|
|
|
|
cd {build_directory} |
|
|
|
cmake -G "MSYS Makefiles" [additional CMake flags] {source_directory} |
|
|
@@ -256,13 +256,13 @@ NMake, remove "-DCMAKE_BUILD_TYPE=Release" (Debug builds are the default with |
|
|
|
NMake.) |
|
|
|
|
|
|
|
|
|
|
|
Self-Contained MinGW Build |
|
|
|
-------------------------- |
|
|
|
Self-Contained GCC Build |
|
|
|
------------------------ |
|
|
|
|
|
|
|
If TigerVNC is built using MinGW, then it may depend on the MinGW libgcc DLL. |
|
|
|
To eliminate this dependency, add |
|
|
|
If TigerVNC is built using GCC (including MinGW), then it may depend on the |
|
|
|
libgcc or libstdc++ dynamic libraries. To eliminate this dependency, add |
|
|
|
|
|
|
|
-DCMAKE_C_FLAGS=-static-libgcc -DCMAKE_CXX_FLAGS=-static-libgcc |
|
|
|
-DBUILD_STATIC=1 |
|
|
|
|
|
|
|
to the CMake command line. |
|
|
|
|