| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The system tools GetParentDirectory method no longer removes the root
path component. This fixes cmSystemTools::FileExistsInParentDirectories
to not infinitely loop at when GetParentDirectory stops at the root.
|
| |
|
|
|
| |
This removes SystemTools::FileExistsInParentDirectories from KWSys since
it is a special-purpose method that is not generally useful.
|
| | |
|
| |
|
|
|
|
|
|
| |
When SystemTools::GetParentDirectory was fixed to never remove the root
path component from a full path we violated an assumption made by
IsSubDirectory that eventually GetParentDirectory returns an empty
string. This led to an infinite loop if the potential parent directory
is empty, so we explicitly avoid that case.
|
| | |
|
| |
|
|
| |
Alex
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
on the main window. Fixed that.
|
| | |
|
| |
|
|
|
|
|
| |
The previous change to this method broke cases where the input path does
not exist. The SystemTools::GetParentDirectory method is redundant with
the more robust SystemTools::GetFilenamePath. This replaces its
implementation to just call GetFilenamePath.
|
| |
|
|
|
|
| |
The cmSystemTools::RenameFile method returns type bool, but its
implementation on Windows returns the result of an API function that
returns BOOL. This change avoids the compiler warning.
|
| |
|
|
| |
argement. Valid check is added to make sure the input argment exists, and if "/" is passed in, empty string will be returned.
|
| |
|
|
|
|
| |
This extends the "-E" command line mode with a "rename old new"
signature. The new command atomically renames a file or directory
within a single disk volume.
|
| |
|
|
|
| |
This creates command "file(RENAME <oldname> <newname>)" to rename a file
or directory within a single disk volume.
|
| |
|
|
|
|
| |
This moves the cmGeneratedFileStream::RenameFile method implementation
into cmSystemTools. It works only within a single filesystem volume,
but is atomic when the operating system permits.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
All KWSys C symbol names begin with the KWSYS_NAMESPACE defined at
configuration time. For ease of editing we write canonical names with
the prefix 'kwsys' and use macros to map them to the configured prefix
at preprocessing time. In the case of standalone KWSys, the prefix is
'kwsys', so the macros were previously defined to their own names.
We now skip defining the macros in the identity case so that the final
symbol names are never themselves macros. This will allow the symbols
to be further transformed behind the scenes to help linkers in special
cases on some platforms.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Linking to a Windows shared library (.dll) requires only its import
library (.lib). This teaches CMake to recognize SHARED IMPORTED library
targets that set only IMPORTED_IMPLIB and not IMPORTED_LOCATION.
|
| |
|
|
|
|
|
| |
When an IMPORTED target provides no generic configuration and no match
for a desired configuration then we choose any available configuration.
This change corrects the choice when the first listed available
configuration does not really have a location.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Previously KWSys SystemInformation parsed this file assuming a strict
order and set of fields, but the order is not reliable. This
generalizes the implementation to support any order and extra fields.
|
| |
|
|
|
|
|
| |
The transitive link dependencies of a linked target must be followed in
its own scope, not in the scope of the original target that depends on
it. This is necessary since imported targets do not have global scope.
See issue #8843.
|
| |
|
|
| |
platform with no std::*stringstream implementation
|
| | |
|
| |
|
|
| |
sunos
|
| | |
|
| | |
|
| |
|
|
| |
compression type by CPack variables. Also add custom .DS_Store and background image support. Thanks to Mike Arthur for the patches.
|
| |
|
|
| |
Lowman for the gist of the patch.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The previous wording of the VERBATIM option documentation in the
add_custom_command and add_custom_target commands was confusing. It
could be interpreted as the opposite of what the option means (no
escaping instead of escaping). This clarifies the documentation to
explicitly state that it escapes.
|
| | |
|
| | |
|
| | |
|
