| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
In cmCTestUpdateHandler, this factors out version control tool detection
from the monolithic cmCTestUpdateHandler::ProcessHandler to separate
methods. This also places priority on detection of the tool managing
the source tree since using any other tool will cause errors.
|
|
|
|
|
|
| |
This moves the initial checkout code from the monolithic
cmCTestUpdateHandler::ProcessHandler to a separate method
cmCTestUpdateHandler::InitialCheckout.
|
| |
|
|
|
|
|
|
| |
Previously we pre-quoted the command line tool path. This avoids it by
quoting the command everywhere it is used, thus preserving access to the
original, unquoted command.
|
|
|
|
| |
generator. Fixes issue #8442. Thanks to Clinton Stimpson for the patch.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This adds documentation of the APPEND option to the configure, build,
test, memcheck, and coverage commands. The docs leave specific
semantics for the dashboard server to define.
|
|
|
|
|
|
| |
This corrects the terse documentation and adds detail to the full
documentation of some commands. It also normalizes the layout of the
documentation string endings to make adding lines easier.
|
|
|
|
| |
This clarifies the terse documentation and lists valid values for PARTS.
|
|
|
|
|
| |
This clarifies the documentation of EXECUTABLE_OUTPUT_PATH and
LIBRARY_OUTPUT_PATH to sound less like deprecation.
|
| |
|
| |
|
| |
|
|
|
|
| |
double clicking on xib files opens them up in Interface Builder. Thanks to baron_roberts for the patch.
|
|
|
|
| |
DragNDropGenerator. See issue #8556. Thanks for Clinton Stimpson for the patch.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This converts uses of 'char' as an array subscript to 'unsigned char' to
heed the warning from gcc. The subscript must be an unsigned type to
avoid indexing before the beginning of the array. This change avoids a
potential crash if input text contains a byte value beyond 0x7f.
|
|
|
|
|
|
|
|
|
|
| |
This removes generation of some Update.xml content that is not used by
any Dart1, Dart2, or CDash servers:
- Revisions elements
- Directory attribute of File elements
- File elements within Author elements
The content was generated only because the original Dart1 Tcl client
generated it, but the content was never used.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The main svn update parsing loop in cmCTestUpdateHandler previously had
a logic error because the variable 'res' was not reset for each
iteration. For a locally modified file it would report the update info
for the previous non-modified file, or nothing if there was no previous
file. This fixes the logic by setting variable 'res' in both control
paths for each iteration. See issue #8168.
|
|
|
|
|
|
|
| |
This renames the variable 'numModiefied' to 'numModified' to fix its
spelling. It also renames 'modifiedOrConflict' to 'notLocallyModified'
to describe its purpose (rather than the opposite of its purpose).
See issue #8168.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This provides an API for parent projects to use to specify values to be
set in the LABELS properties of KWSys libraries, executables, and tests.
|
|
|
|
|
| |
This adds the configured KWSys header files to the library targets that
implement their APIs so that they show up in IDE project files.
|
|
|
|
|
|
| |
This teaches CTest to include source file labels in coverage dashboard
submissions. The labels for each source are the union of the LABELS
property from the source file and all the targets in which it is built.
|
| |
|
|
|
|
|
|
| |
Since CTest does not currently load configuration settings computed at
CMake Configure time while running dashboard scripts, the ctest_build
command must honor the CTEST_USE_LAUNCHERS option directly.
|
|
|
|
|
|
| |
Currently CTest does not load configuration settings computed at CMake
Configure time when running a dashboard script. This adds a comment
describing refactoring that might help resolve the problem.
|
| |
|
|
|
|
|
| |
This fixes a dumb logic error which causes generation of LabelFiles.txt
to try to open the file once for every target with labels.
|
|
|
|
|
| |
This teaches cmCTestLaunch to report source files that lie under the top
source directory relative to the top.
|
| |
|
| |
|
|
|
|
|
|
| |
When we collect Build.xml fragments generated by 'ctest --launch', this
lexicographically orders fragments with the same time stamp on disk
instead of incorrectly dropping duplicates.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This defines a 'UseLaunchers' CTest configuration option. When enabled,
CTest skips log scraping from the Build step output. Instead it defines
the environment variable CTEST_LAUNCH_LOGS to a log directory during the
build. After the build it looks for error-*.xml and warning-*.xml files
containing fragments for inclusion in Build.xml and submission.
This is useful in conjuction with 'ctest --launch' and the RULE_LAUNCH_*
properties to get reliable, highly-granular build failure reports.
|
|
|
|
|
|
| |
cmCTestLaunch first used an empty initializer list to zero-initialize a
buffer, but this is not supported on older compilers. Instead we avoid
the need for initialization altogether.
|