On 2017 M09 21, Thu 07:18:46 CEST David Cole via CMake wrote:
> By manually deleting (or touching) the stamp file associated with the
> earliest step you need to re-run.
>
> ExternalProject is not for auto-detecting changes to stuff and
> minimally re-running build steps. It's for static stuff tha
On Thu, Sep 21, 2017 at 4:21 AM, Craig Scott
wrote:
> You probably want the BUILD_ALWAYS option. Have a look at the overhauled
> docs for ExternalProject (only available on master at the moment) for a
> more informative description of the option and the module in general:
>
> Excellent that fixes
On Thu, Sep 21, 2017 at 1:09 PM, J Decker wrote:
> how do I make sure that externalprojects get built if I change a source in
> one?
>
"BUILD_ALWAYS 1" should always trigger the build of the external project.
This would be required since only the external project's build system will
know if some
You probably want the BUILD_ALWAYS option. Have a look at the overhauled
docs for ExternalProject (only available on master at the moment) for a
more informative description of the option and the module in general:
https://cmake.org/cmake/help/git-master/module/ExternalProject.html
On Thu, Sep 2
By manually deleting (or touching) the stamp file associated with the
earliest step you need to re-run.
ExternalProject is not for auto-detecting changes to stuff and
minimally re-running build steps. It's for static stuff that doesn't
change much.
Find the "-build" stamp file that's associated w
how do I make sure that externalprojects get built if I change a source in
one?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on e
