From f95272de303373b3d2d55e001a0dac9a8d800407 Mon Sep 17 00:00:00 2001 From: Pierre Ossman Date: Fri, 17 Oct 2014 13:59:35 +0200 Subject: Extend "static" build option Try to link as much as possible statically in an effort to produce binaries that can be run everywhere. --- BUILDING.txt | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'BUILDING.txt') diff --git a/BUILDING.txt b/BUILDING.txt index 71d26b65..8f686cc3 100644 --- a/BUILDING.txt +++ b/BUILDING.txt @@ -252,16 +252,21 @@ Debug Build Add "-DCMAKE_BUILD_TYPE=Debug" to the CMake command line. -Self-Contained GCC Build ------------------------- +Portable (semi-static) Build +---------------------------- -If TigerVNC is built using GCC (including MinGW), then it may depend on the -libgcc or libstdc++ dynamic libraries. To eliminate this dependency, add +TigerVNC can under favourble circumstances be built in a way that allows +the resulting binaries to run on any system without having to also install +all the dynamic libraries it depends on. Enable this mode by adding: -DBUILD_STATIC=1 to the CMake command line. +Note that the method used to achieve this is very fragile and it may be +necessary to tweak cmake/StaticBuild.cmake to make things work on your +specific system. + ===================== Building Java Support -- cgit v1.2.3