| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
non-cygwin builds that are using cygwin cvs.exe.
|
|
|
|
| |
(rather than 1.4) so that it works (hopefully) with more svn clients in the wild. Change time stamps of test projects in CMakeLists.txt to reflect times available in newly created repository. Add UPDATE_COMMAND "" for checkouts that are tag-based or date-stamp-based to avoid unnecessary update steps.
|
|
|
|
| |
available. Add 'configure' step to the repository extraction 'projects' to print the version number of CVS and SVN in the dashboard test/build output.
|
|
|
|
| |
to avoid network activity. Also: stop building KWStyle and kwsys as part of this test to reduce the amount of time spent running the test. Instead, build TutorialStep1 as retrieved from the new local repositories with various tags, date stamps and revision numbers.
|
|
|
|
|
|
|
|
|
|
| |
This creates new module ExternalProject.cmake to replace the prototype
AddExternalProject.cmake module. The interface is more refined, more
flexible, and better documented than the prototype.
This also converts the ExternalProject test to use the new module. The
old module will be removed (it was never in a CMake release) after
projects using it have been converted to the new module.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The add_external_project function separates its arguments with ';'
separators, so previously no command line argument could contain one.
When specifying CMAKE_ARGS, some -D argument values may need to contain
a semicolon to form lists in the external project cache.
This adds add_external_project argument LIST_SEPARATOR to specify a list
separator string. The separator is replaced by ';' in arguments to any
command created to drive the external project. For example:
add_external_project(...
LIST_SEPARATOR ::
CMAKE_ARGS -DSOME_LIST:STRING=A::B::C
...)
passes "-DSOME_LIST:STRING=A;B;C" to CMake for the external project.
|
|
|
|
|
|
| |
This creates function 'add_external_project_step' to centralize creation
of external project steps. Users may call it to add custom steps to
external project builds.
|
|
|
|
|
|
| |
The patch step runs parallel to the update step since it does not make
sense to have both. Configuration of the step requires specification of
a PATCH_COMMAND argument to add_external_project.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This rewrites the keyword/argument parsing and handling in the
AddExternalProject module to use arguments more literally:
- The strict keyword-value pairing is gone in favor of keywords with
arbitrary non-keyword values. This avoids requiring users to escape
spaces and quotes in command lines.
- Customized step command lines are now specified with a single
keyword <step>_COMMAND instead of putting the arguments in a
separate entry (previously called <step>_ARGS).
- Build step custom commands now use VERBATIM mode so that arguments
are correctly escaped on the command line during builds.
|
|
|
|
|
|
|
| |
This teaches AddExternalProject to run "$(MAKE)" for build and install
steps of CMake-based external projects when using a Makefile generator.
It allows the external project to participate in a parallel make invoked
on the superproject.
|
|
|
|
| |
it properly by using the SYMBOLIC source file property to indicate to WMake when the sentinel file is not actually written by the update step.
|
|
|
|
| |
commands to fix the failing ExternalProject test on the CMake nightly dashboard.
|
|
|
|
| |
errors of Tutorial Step5 on Win98 using Visual Studio 6 when the path length of its build tree exceeds 72 characters. Crazy, perhaps. But this fixes the last real dashboard failure of the ExternalProject test.
|
|
|
|
| |
building, installing and testing on WATCOM dashboards. WATCOM STL support is still under development.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
for an external project. Add capability of customizing the download step. Add tests of empty projects. Better comments and error checking in AddExternalProject.cmake. In tests, use KWStyle from CVSHEAD to see if QNX continuous can build the latest KWStyle. Make KWStyle test depend on all previous test external projects so it builds last to catch other issues before any KWStyle compile errors.
|
|
|
|
| |
building the projects that depend on a cvs or svn download method.
|
|
fixing, more tests and documentation certain to follow as it gets used by others...
|