- Sep 15, 2016
-
-
Kitware Robot authored
-
- Sep 14, 2016
-
-
6a9ed3d4 cmGeneratorTarget: factor out a space
-
e952f1bd cmcmd: Fix sort order in help output
-
-
-
-
1ca2d5d1 cmake-gui: Add button to open the generated project
-
Brad King authored
-
Kitware Robot authored
-
- Sep 13, 2016
-
-
Look for VS or Xcode project files at the top of the build tree. If present, enable an "Open Project" button to open them through the OS desktop services.
-
Encode the subdirectory names properly for CMake syntax. Closes: #16299
-
-
Ruslan Baratov authored
-
Add options to the `install()` and `export()` commands to export the targets we build into Android.mk files that reference them as prebuilt libraries with associated usage requirements (compile definitions, include directories, link libraries). This will allow CMake-built projects to be imported into projects using the Android NDK build system. Closes: #15562
-
-
-
b35311ca CTestSVN: Fix segfault when CTEST_UPDATE_VERSION_ONLY is enabled
-
4f349a86 Help: Fix formatting in separate_arguments documentation
-
9370b697 Re-order link line to place RPATH entries before libraries
-
4dd997da file(DOWNLOAD|UPLOAD): Warn on unexpected arguments
-
Ben Boeckel authored -
Tobias Hunger authored
sort "sleep" before "tar", not after
-
Kitware Robot authored
-
- Sep 12, 2016
-
-
Tobias Hunger authored
-
Brad King authored
-
Nils Gladitz authored
Before the change the list of externals was queried only before the svn update. With the change the list is queried both before and after. This should also be more accurate since the list of externals might change during the update.
-
Ruslan Baratov authored
%b: Abbreviated month name (e.g. Oct). %a: Abbreviated weekday name (e.g. Fri).
-
-
-
Tobias Hunger authored
Introduce cmake::ReportCapabilitiesJson which returns a the Json object that is serialized in cmake::ReportCapabilities. This allows to re-use the information in cmake-server.
-
Tobias Hunger authored
Ignore *.user* files from QtCreator and *.pyc files.
-
Since we support adding arbitrary flags to the link line via `target_link_libraries` the project/user may add their own RPATH flags (typically for system library locations). Re-order the link line to place our generated RPATH entries before the libraries so that they also come before flag-specified entries. Otherwise our in-build-tree RPATH entries may not be preferred by the dynamic loader and we could collide with libraries in the system directories. Closes: #16293
-
Refactor the library code used in the GenerateExportHeader test to use an improved naming convention that more directly identifies what it being tested, making use of namespaces to avoid possible symbol collisions. This also eliminates duplicate cases such as `libshared()` and `libshared_not_exported()` which had the same decoration, and adds consistent pairings of <name>_EXPORT and <name>_DEPRECATED_EXPORT which were missing previously. The data tests from the previous commit are also added to `libstatic` and `libshared_and_static` for consistency. Note that there are no exported members of exported classes, as these are not allowed on Windows.
-
Add static data members and global variables to the GenerateExportHeader shared library, testing that export decoration for these works in addition to decoration of classes and free functions.
-
Modify notation of statements in the GenerateExportHeader test expected to result in link errors. Modify script used to build the test to also generate a suite of modified sources, each having exactly one of the failing lines enabled, and to generate EXCLUDE_FROM_ALL executables for the same. Modify RunCMake script used to drive the test to read the list of such executables and try to build each of them, verifying that they do in fact fail to build. This will verify that the _NO_EXPORT macros are working as expected, and will also catch errors like the one that commit 0cbaaf2d (GenerateExportHeader: Fix add_compiler_export_flags regression, 2016-09-01) fixed. When setting up the failure tests for GenerateExportHeader, check if the compiler actually hides non-exported stuff. If not, the failure tests won't fail, and will cause the overall test to fail. Since this typically is only the case for very old compilers, simply skipping them as opposed to trying to do something more fine grained seems reasonably safe.
-
-
-
db915a37 Utilities/Release: Drop Cygwin binary
-
c0bccc51 CPackWIX: Enabled patching of WIX <Feature> tags
-
861f1b3d VS: Do not default to missing v100 64-bit toolset on VS 2010 Express
-
