| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Add a `CMAKE_DEPENDS_IN_PROJECT_ONLY` variable to activate the behavior.
|
|\
| |
| |
| |
| | |
5c1f4da8 Tests: Rename RunCMake.{SolutionGlobalSections => VSSolution}
|
| |
| |
| |
| | |
The test will be suitable for covering other `.sln` content too.
|
|\ \
| | |
| | |
| | |
| | | |
bf3e76d2 GHS: Fix try_compile (#15975)
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
9ead71df Help: Add notes for topic 'ninja-directory-targets'
e9bf8ec8 Ninja: Add test for `$subdir/all` targets
ca575fe9 Ninja: Add `$subdir/all` targets
|
| | | | |
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With the Makefile generator one can use `cd $subdir; make all` to build
all targets associated with a given subdirectory. This is not possible
to do with the Ninja generator since there is only one `build.ninja`
file at the top of the build tree. However, we can approximate it by
allowing one to run `ninja $subdir/all` at the top of the tree to build
the targets in the corresponding subdirectory.
Port logic from cmGlobalUnixMakefileGenerator3::WriteDirectoryRule2 to
cmGlobalNinjaGenerator in order to produce equivalent directory-level
targets.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
8e2aa6ca TestBigEndian: Log success to CMakeOutput.log, not CMakeError.log
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
6f4f9054 FindPkgConfig: set correctly named variables in cache (#15903)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The fix in commit v3.5.0-rc1~27^2 (FindPkgConfig: set standard variables
in the cache, 2016-01-20) added the wrong variable name to the cache.
The test was only testing that the cache variable existed, not that it
also had the correct value. Update the test to ensure that the cache
value matches the local variable value.
Reported-by: Bernd Lörwald
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
53c0dc2d Add support for Bruce C Compiler (BCC)
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
Revise C compiler detection code to be K&R compatible.
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
d84ba668 CPack: Avoid using OS X CoreServices if compiler fails on header (#16021)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some compilers on OS X report errors in the CoreServices framework headers.
Check for support of the header ahead of time and compile the relevant code
only when the header is available.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
5f6b4f69 Find{BLAS,LAPACK}: Add support for OpenBLAS (#16024)
|
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
OpenBLAS (www.openblas.net) is the successor to GotoBLAS.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
52777366 Drop unnecessary LSRequiresCarbon reference from Info.plist files
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
LSRequiresCarbon is long since unnecessary. It refers to requiring
Carbon as opposed to Classic (OS 9 emulation).
|
| | | | | |
|
| |_|/ /
|/| | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
c089485d Utilities/Release: Skip spurious Qt5Autogen test for nightly binary
e903a9fc Utilities/Release: Create a Windows 64-bit binary
dd630075 Utilities/Release: Rename scripts to match target platform
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This test fails spuriously too often and prevents the nightly binary
from finishing. Simply skip it for the nightly binary to allow it
to complete more regularly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Compile with `-D_WIN32_WINNT=0x502` to use a WinXP-compatible API.
Compile with `-D_USING_V110_SDK71_` to tell the VS standard library
headers that we are building with a WinXP-compatible Windows SDK. Link
executables with `-subsystem:console,5.02` to make them runnable on
Windows XP 64-bit. Ideally `cmake-gui` should instead be linked with
`-subsystem:windows,5.02` but with the Ninja and Makefile generators
CMake adds `-subsystem:windows` after our `-subsystem:console,5.02` flag
and the linker seems to interpret this combination as we need.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The machine name we happen to use for the build is less informative than
its platform.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
6a6e5d89 GenerateExportHeader: Allow common NO_DEPRECATED_MACRO_NAME for multiple libs
be5a8973 GenerateExportHeader: Do not define DEFINE_NO_DEPRECATED (#16022)
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously we allowed this definition to persist outside our header.
This would cause conflicts across multiple such headers because the name
was always the same. Fix this by avoiding the definition altogether.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
7b990e82 cmake-gui: Populate CFBundleIdentifier in our Info.plist file (#16023)
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
c718070c CPack: Avoid requiring Carbon framework on OS X (#16021)
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In commit v3.5.0-rc1~232^2 (CPackDMG: Add support for multilingual SLAs,
2015-10-19) we added use of the Carbon framework in order to get access
to its APIs to convert Script Manager RegionCode values. This is not
necessary. Instead we can use CoreServices.
While at it, replace individual CoreFoundation includes with including
the entire framework, which is the correct way.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
a3bcf2aa VS: Fix WinCE remote debugger tool per-config target name
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix the DebuggerTool RemoteExecutable value added by commit a22f9967
(VS: Optionally generate remote directory for WinCE projects,
2016-02-15) to account for the configuration when computing the target
name.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
e3fc2899 Fix iOS combined feature for single architecture targets
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
If list of valid target architectures is empty for given SDK then there will
be no VALID_ARCHS build setting returned by Xcode. Return "" (empty string)
explicitly in this case. This may happens if CMAKE_IOS_INSTALL_COMBINED is ON
but only one architecture used in target.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
9dc384f6 cmake-mode.el: Fix help completion item lists with CMake >= 3.0 (#16019)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We run `cmake --help-*-list` to get a list of items for completion.
Since CMake < 3.0 always printed "cmake version ..." on the first line
of the output we have previously ignored the first line. However, CMake
3.0 and above do not print the version line so we should not ignore the
first line or we miss one item.
Ideally we should filter the first line out if it is "cmake version ..."
in order to support CMake < 3.0 cleanly, but at worst the version line
will show up as a completion option so simply including the first line
is good enough for now.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
3144857e Avoid depending on CMAKE_ROOT cache entry internally (#16015)
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use cmSystemTools::GetCMakeRoot() which always knows the location of our
resources. Do not depend on CMAKE_ROOT because the user could unset it
from the cache.
|
| |_|_|/
|/| | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
e2f387fa FindBoost: Tolerate missing indirect dependencies (#16013)
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Depending upon the configuration, certain components may or may not
be installed, for example Boost.Regex, but other components may
still have header dependencies upon these components which will
obviously fail to work. Since we can't make a sensible
determination with the hardcoded dependency information, we
choose to interpret these dependencies less strictly.
|