[CMake] add_custom_command problem
Eric Noulard
eric.noulard at gmail.com
Mon Jan 17 09:09:00 EST 2011
2011/1/17 Andrea Galeazzi <Galeazzi at korg.it>:
> Eric Noulard ha scritto:
>
> 2011/1/17 Andrea Galeazzi <galeazzi at korg.it>:
>
>
> Il 17/01/2011 12.34, Eric Noulard ha scritto:
>
>
> I just realized something.
> Do you want
> A) to increase the build number EACH time you build
> B) to increase the build number WHEN of of the SOURCES change?
>
>
> The B is definitely my choice.
>
>
> So then what is the precise symptom.
>
> 1) The BuildNumber.h is never generated (and you have a compile error)
> 2) The BuildNumber.h is never regenerated when Config.cpp change?
>
> The symptoms are both:
> 1 - The first time I build the project I have a compile error because
> BuildNumber.h doesn't exist.
So there is an initial dependency issue.
> 2 - If I manually create BuildNumber.h in order to "pass" the compilation,
> any next build doesn't update BuildNumber.h.
>
> I also point out that I wanna update such file every time ANY sources are
> changed.
> I made a simple project that has this problem, where can I upload it?
1) Open bug report:
http://public.kitware.com/Bug/main_page.php
2) and attach your example project to the bug.
3) Send an e-mail into this thread which gives the
url of the bug this way the bug will be linked to the discussion.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
More information about the CMake
mailing list