[cmake] No "make install" target
Bug #423556 reported by
Bob Tanner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netrek Server |
Fix Committed
|
Critical
|
Bob Tanner | ||
Bug Description
Taken from James email to netrek-devel.
a. there is no "make install" target, so one can't complete the task of getting a server built and operational, ... this is critical,
Changed in netrek-server: | |
status: | New → Confirmed |
assignee: | nobody → Bob Tanner (tanner) |
Changed in netrek-server: | |
milestone: | none → 2.16.1 |
To post a comment you must log in.
Just adding this for my own reference.
http:// www.cmake. org/cmake/ help/cmake2. 6docs.html
install: Specify rules to run at install time.
This command generates installation rules for a project. Rules specified by calls to this command within a source directory are executed in order during installation. The order across directories is not defined.
There are multiple signatures for this command. Some of them define installation properties for files and targets. Properties common to multiple signatures are covered here but they are valid only for signatures that specify them.
DESTINATION arguments specify the directory on disk to which a file will be installed. If a full path (with a leading slash or drive letter) is given it is used directly. If a relative path is given it is interpreted relative to the value of CMAKE_INSTALL_ PREFIX.
PERMISSIONS arguments specify permissions for installed files. Valid permissions are OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ, GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE, WORLD_EXECUTE, SETUID, and SETGID. Permissions that do not make sense on certain platforms are ignored on those platforms.
The CONFIGURATIONS argument specifies a list of build configurations for which the install rule applies (Debug, Release, etc.).
The COMPONENT argument specifies an installation component name with which the install rule is associated, such as "runtime" or "development". During component-specific installation only install rules associated with the given component name will be executed. During a full installation all components are installed.
The RENAME argument specifies a name for an installed file that may be different from the original file. Renaming is allowed only when a single file is installed by the command.
The OPTIONAL argument specifies that it is not an error if the file to be installed does not exist.
The TARGETS signature:
install(TARGETS targets... [EXPORT <export-name>]
[[ARCHIVE| LIBRARY| RUNTIME| FRAMEWORK| BUNDLE|
PRIVATE_ HEADER| PUBLIC_ HEADER| RESOURCE]
[DESTINATIO N <dir>]
[PERMISSION S permissions...]
[CONFIGURAT IONS [Debug| Release| ...]]
[COMPONENT <component>]
[OPTIONAL] [NAMELINK_ ONLY|NAMELINK_ SKIP]
] [...])
The TARGETS form specifies rules for installing targets from a project. There are five kinds of target files that may be installed: ARCHIVE, LIBRARY, RUNTIME, FRAMEWORK, and BUNDLE. Executables are treated as RUNTIME targets, except that those marked with the MACOSX_BUNDLE property are treated as BUNDLE targets on OS X. Static libraries are always treated as ARCHIVE targets. Module libraries are always treated as LIBRARY targets. For non-DLL platforms shared libraries are treated as LIBRARY targets, except that those marked with the FRAMEWORK property are treated as FRAMEWORK targets on OS X. For DLL platforms the DLL part of a shared library is treated as a RUNTIME target and the corresponding import library is treated as an ARCHIVE target. All Windows-based systems including Cygwin are DLL platforms. The ARCHIVE, LIBRARY, RUNTIME, and FRAMEWORK arguments change the type of target to which...