Alex authored 3 weeks ago and Brad King committed 3 weeks ago

Use `FormatMessageW` and convert to our internal narrow encoding.

This was once supported in CMake 2.x and in current 3.x versions is
ignored.

CMake used this to preserve symlinks through realpath operations, but
its presence caused some undesired side effects.  Those realpath
operations are being replaced with a hand-written alternative that
explicitly preserves symlinks when possible and does not have the side
effects.  Therefore we no longer need the path translation map.

Issue: cmake/cmake#16228

Use the CTest module directly.

Modern C++ mangling produces short symbol names for templates
instantiated with `std::string`, so `kwsys::String` has no purpose.

Pass our own definition using `$<CONFIG>` instead.

Ben Boeckel authored 2 years ago and Brad King committed 2 years ago

ParaView no longer uses it and nothing else does either. This also
removes much of the `CMAKE_INTDIR` usage in the project.

In the policy's NEW behavior, the compiler id is `XLClang`.

Đoàn Trần Công Danh authored 3 years ago and Brad King committed 3 years ago

backtrace(3) from libexecinfo in musl will run into crash [1].

Provide an option to disable it explicitly even if libexecinfo is present.

1: https://www.openwall.com/lists/musl/2021/07/17/1

If the target is changed since the last configure, some checks need to
be looked up again. Clear their cache entries when these checks need to
be redone.

The versions of these compilers previously supported do not
support C++11 that we now require.

Now that KWSys requires C++11, we can assume `long long` and `std:atoll`
are available.

It was already turned off when building inside CMake.
Other consuming projects have been migrated to C++11 and
can now use `std::unordered_{set,map}` instead.

The `IOStream` component was meant to provide compatibility with old C++
stream implementations that did not support `long long` and/or
`__int64`.  Now that KWSys requires C++11 that is not a problem.

This test fails very frequently on CI because it relies on the
timing of process scheduling by the OS, which is not deterministic.
Disable it.

Ancient CMake versions required upper-case commands.  Later command names
became case-insensitive.  Now the preferred style is lower-case.

EXECUTABLE_OUTPUT_PATH is the old executable location variable.

The target property RUNTIME_OUTPUT_DIRECTORY supercedes this variable
for a target if it is set. Executable targets are otherwise placed in
this directory.

Julien Schueller authored 5 years ago and Brad King committed 5 years ago

Fix another place missed by commit c3acc96d (CMake: Fix psapi lib name
on case-sensitive fs, 2020-02-13).

Fixes detection of GetProcessMemoryInfo on MinGW

* Clang with the MSVC STL requires C++14
* Deprecatoion warning suppressions were specific to MSVC and Intel
* An assignment inside a condition resulted in a warning
* kwsysProcessSetExitException was declared, but never defined or used

Ken Martin authored 5 years ago and Brad King committed 5 years ago

The prior code had no implementation on windows. This code relies on
dbghelp.dll which is a standard part of the operating system. It is
implemented for OS from Vista forward when compiled with MSVC version
1800 or later (VS2013).

Ben Boeckel authored 9 years ago and Brad King committed 5 years ago

When determining full paths, CMake would treat the as-called path for
the source and build directories as real paths even if they were
symlinks. This causes problems when determining the relative path
between the source and build directories when they are symlinks.

Take the following setup as an example:

    /mnt/src/project/
        src/
        build/ -> /mnt/builds/project/build

With the translation map and /mnt/src/project/build/ as the build
directory, CMake would use ../src as the relative path to the source
tree from the build tree rather than ../../../src/project/src and
lookups using ../src would fail. If the build directory were instead
used *as* /mnt/builds/project/build, everything would work just
fine.

This patch makes the core logic which does this logic optional so that
it can be experimented with in CMake itself.

This converts the path to a format suitable for passing to Windows APIs.

Historically we have defined macros like

* `_LARGEFILE_SOURCE`
* `_LARGEFILE64_SOURCE`
* `_LARGE_FILES`
* `_FILE_OFFSET_BITS`

in `Configure.h` to activate large file support in system headers.  This
requires consuming projects to include the header at the beginning of
every translation unit in order to get the macros defined consistently.

Instead these macros should be defined by the build system on the
compiler command line.  Drop them from KWSys in favor of that approach.
The macros are not needed as often as they once were anyway.

In standalone builds, default to C++11.  Provide options for
host projects to control the standard level.