Linux websever 5.15.0-153-generic #163-Ubuntu SMP Thu Aug 7 16:37:18 UTC 2025 x86_64
Apache/2.4.52 (Ubuntu)
: 192.168.3.70 | : 192.168.1.99
Cant Read [ /etc/named.conf ]
8.1.2-1ubuntu2.23
urlab
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
cmake-3.22 /
Help /
envvar /
[ HOME SHELL ]
Name
Size
Permission
Action
ASM_DIALECT.rst
843
B
-rw-r--r--
ASM_DIALECTFLAGS.rst
746
B
-rw-r--r--
CC.rst
648
B
-rw-r--r--
CCMAKE_COLORS.rst
1.46
KB
-rw-r--r--
CFLAGS.rst
551
B
-rw-r--r--
CMAKE_APPLE_SILICON_PROCESSOR....
424
B
-rw-r--r--
CMAKE_BUILD_PARALLEL_LEVEL.rst
345
B
-rw-r--r--
CMAKE_BUILD_TYPE.rst
299
B
-rw-r--r--
CMAKE_CONFIGURATION_TYPES.rst
335
B
-rw-r--r--
CMAKE_CONFIG_TYPE.rst
197
B
-rw-r--r--
CMAKE_EXPORT_COMPILE_COMMANDS....
390
B
-rw-r--r--
CMAKE_GENERATOR.rst
557
B
-rw-r--r--
CMAKE_GENERATOR_INSTANCE.rst
250
B
-rw-r--r--
CMAKE_GENERATOR_PLATFORM.rst
312
B
-rw-r--r--
CMAKE_GENERATOR_TOOLSET.rst
309
B
-rw-r--r--
CMAKE_INSTALL_MODE.rst
4.44
KB
-rw-r--r--
CMAKE_LANG_COMPILER_LAUNCHER.r...
505
B
-rw-r--r--
CMAKE_LANG_LINKER_LAUNCHER.rst
511
B
-rw-r--r--
CMAKE_MSVCIDE_RUN_PATH.rst
341
B
-rw-r--r--
CMAKE_NO_VERBOSE.rst
257
B
-rw-r--r--
CMAKE_OSX_ARCHITECTURES.rst
303
B
-rw-r--r--
CMAKE_PREFIX_PATH.rst
712
B
-rw-r--r--
CMAKE_TOOLCHAIN_FILE.rst
424
B
-rw-r--r--
CSFLAGS.rst
603
B
-rw-r--r--
CTEST_INTERACTIVE_DEBUG_MODE.r...
213
B
-rw-r--r--
CTEST_OUTPUT_ON_FAILURE.rst
323
B
-rw-r--r--
CTEST_PARALLEL_LEVEL.rst
199
B
-rw-r--r--
CTEST_PROGRESS_OUTPUT.rst
757
B
-rw-r--r--
CTEST_USE_LAUNCHERS_DEFAULT.rs...
164
B
-rw-r--r--
CUDAARCHS.rst
346
B
-rw-r--r--
CUDACXX.rst
700
B
-rw-r--r--
CUDAFLAGS.rst
597
B
-rw-r--r--
CUDAHOSTCXX.rst
824
B
-rw-r--r--
CXX.rst
660
B
-rw-r--r--
CXXFLAGS.rst
573
B
-rw-r--r--
DASHBOARD_TEST_FROM_CTEST.rst
246
B
-rw-r--r--
DESTDIR.rst
707
B
-rw-r--r--
ENV_VAR.txt
149
B
-rw-r--r--
FC.rst
677
B
-rw-r--r--
FFLAGS.rst
580
B
-rw-r--r--
HIPCXX.rst
498
B
-rw-r--r--
HIPFLAGS.rst
590
B
-rw-r--r--
ISPC.rst
502
B
-rw-r--r--
ISPCFLAGS.rst
598
B
-rw-r--r--
LDFLAGS.rst
498
B
-rw-r--r--
MACOSX_DEPLOYMENT_TARGET.rst
299
B
-rw-r--r--
OBJC.rst
593
B
-rw-r--r--
OBJCXX.rst
610
B
-rw-r--r--
PackageName_ROOT.rst
724
B
-rw-r--r--
RC.rst
655
B
-rw-r--r--
RCFLAGS.rst
570
B
-rw-r--r--
SWIFTC.rst
704
B
-rw-r--r--
VERBOSE.rst
330
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : CMAKE_INSTALL_MODE.rst
CMAKE_INSTALL_MODE ------------------ .. versionadded:: 3.22 .. include:: ENV_VAR.txt The ``CMAKE_INSTALL_MODE`` environment variable allows users to operate CMake in an alternate mode of :command:`file(INSTALL)` and :command:`install()`. The default behavior for an installation is to copy a source file from a source directory into a destination directory. This environment variable however allows the user to override this behavior, causing CMake to create symbolic links instead. Usage Scenarios ^^^^^^^^^^^^^^^ Installing symbolic links rather than copying files can help in the following ways: * Conserving storage space because files do not have to be duplicated on disk. * Changes to the source of the symbolic link are seen at the install destination without having to re-run the install step. * Editing through the link at the install destination will modify the source of the link. This may be useful when dealing with CMake project hierarchies, i.e. using :module:`ExternalProject` and consistent source navigation and refactoring is desired across projects. Allowed Values ^^^^^^^^^^^^^^ The following values are allowed for ``CMAKE_INSTALL_MODE``: ``COPY``, empty or unset Duplicate the file at its destination. This is the default behavior. ``ABS_SYMLINK`` Create an *absolute* symbolic link to the source file at the destination. Halt with an error if the link cannot be created. ``ABS_SYMLINK_OR_COPY`` Like ``ABS_SYMLINK`` but fall back to silently copying if the symlink couldn't be created. ``REL_SYMLINK`` Create a *relative* symbolic link to the source file at the destination. Halt with an error if the link cannot be created. ``REL_SYMLINK_OR_COPY`` Like ``REL_SYMLINK`` but fall back to silently copying if the symlink couldn't be created. ``SYMLINK`` Try as if through ``REL_SYMLINK`` and fall back to ``ABS_SYMLINK`` if the referenced file cannot be expressed using a relative path. Halt with an error if the link cannot be created. ``SYMLINK_OR_COPY`` Like ``SYMLINK`` but fall back to silently copying if the symlink couldn't be created. .. note:: A symbolic link consists of a reference file path rather than contents of its own, hence there are two ways to express the relation, either by a *relative* or an *absolute* path. When To Set The Environment Variable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For the environment variable to take effect, it must be set during the correct build phase(s). * If the project calls :command:`file(INSTALL)` directly, the environment variable must be set during the configuration phase. * In order to apply to :command:`install()`, the environment variable must be set during installation. This could be during a build if using the ``install`` or ``package`` build targets, or separate from the build when invoking an install or running :manual:`cpack <cpack(1)>` from the command line. * When using :module:`ExternalProject`, it might be required during the build phase, since the external project's own configure, build and install steps will execute during the main project's build phase. Given the above, it is recommended to set the environment variable consistently across all phases (configure, build and install). Caveats ^^^^^^^ Use this environment variable with caution. The following highlights some points to be considered: * ``CMAKE_INSTALL_MODE`` only affects files, not directories. * Symbolic links are not available on all platforms. * The way this environment variable interacts with the install step of :module:`ExternalProject` is more complex. For further details, see that module's documentation. * A symbolic link ties the destination to the source in a persistent way. Writing to either of the two affects both file system objects. This is in contrast to normal install behavior which only copies files as they were at the time the install was performed, with no enduring relationship between the source and destination of the install. * Combining ``CMAKE_INSTALL_MODE`` with :prop_tgt:`IOS_INSTALL_COMBINED` is not supported. * Changing ``CMAKE_INSTALL_MODE`` from what it was on a previous run can lead to unexpected results. Moving from a non-symlinking mode to a symlinking mode will discard any previous file at the destination, but the reverse is not true. Once a symlink exists at the destination, even if you switch to a non-symlink mode, the symlink will continue to exist at the destination and will not be replaced by an actual file.
Close
