[cmake-developers] [CMake 0015368]: ExternalProject's BUILD_ALWAYS flag doesn't clear any existing build stamp file
Mantis Bug Tracker
mantis at public.kitware.com
Fri Jan 23 01:18:51 EST 2015
The following issue has been SUBMITTED.
======================================================================
http://www.cmake.org/Bug/view.php?id=15368
======================================================================
Reported By: peitschie
Assigned To:
======================================================================
Project: CMake
Issue ID: 15368
Category: CMake
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 2015-01-23 01:18 EST
Last Modified: 2015-01-23 01:18 EST
======================================================================
Summary: ExternalProject's BUILD_ALWAYS flag doesn't clear
any existing build stamp file
Description:
Setting the BUILD_ALWAYS flag on an external project should cause the build step
to always trigger. This was new in 3.1 from what I can see. Unfortunately, it
appears to do this by making the *next* stamp file created symbolic (see
https://github.com/Kitware/CMake/blob/master/Modules/ExternalProject.cmake#L1457).
This means that until the existing stamp file is deleted, or something else
causes a rebuild to occur, BUILD_ALWAYS has no effect
Steps to Reproduce:
1. Create a CMake file with an external project, with BUILD_ALWAYS set to 0
2. Build the external project
3. Change the BUILD_ALWAYS flag to 1
4. Attempt to rebuild the external project, and note how the build step is never
executed.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2015-01-23 01:18 peitschie New Issue
======================================================================
More information about the cmake-developers
mailing list