Hi,
add_custom_target(update_version COMMAND echo updating)
add_library(mylib version.c)
add_dependencies(mylib update_version)
We had exactly this configuration for months and the lib was rebuilt
always... but now that you affirm that it /should/ work better, I
had a deeper look again.
Hi,
I know that similar questions have been posted before, but as far as I
have been able to follow, no real solution was ever given.
The goal is to embed revision information in a C++ library mylib.
I already managed to use create_custom_target so that an external
program is executed to
the list of sources. But another problem came up: Only the first single
list item seems to be scanned for implicit dependencies. And I failed to
come up with a list or command syntax that would allow me to have the
other 99+ sources scanned as well.
I think I came up with a usable workaround
On 11. Dec, 2009, at 15:53 , Kolja Waschk wrote:
Hi,
I know that similar questions have been posted before, but as far as I
have been able to follow, no real solution was ever given.
The goal is to embed revision information in a C++ library mylib.
I already managed to use
Hi, thanks,
One question: Why do you need a add_custom_command with all those
dependencies? Why does version.cc depend on all the source and header
files? What do you write in your version.cc file? Is it something like
Beside the SVN revision number of the working base, our embedded
revision
On 11. Dec, 2009, at 16:58 , Kolja Waschk wrote:
Hi, thanks,
One question: Why do you need a add_custom_command with all those
dependencies? Why does version.cc depend on all the source and header
files? What do you write in your version.cc file? Is it something like
Beside the SVN
