2009/2/28 Aaron Turner synfina...@gmail.com:
So is there a clean way to pass the current Cmake config variables to
a new cmake process via execute_process()? Or do I need to create a
template file and use configure_file() to do that? Basically, your
above example doesn't work for me because
2009/2/27 Aaron Turner synfina...@gmail.com:
When I was using autotools, I'd hook up a target version to
dist-gzip so that my version.c (which was auto-generated and had my
svn repo revision in it) was always up to date when I built my source
tarball. Is there a way to do that with cpack's
On Fri, Feb 27, 2009 at 7:36 AM, Eric Noulard eric.noul...@gmail.com wrote:
2009/2/27 Aaron Turner synfina...@gmail.com:
When I was using autotools, I'd hook up a target version to
dist-gzip so that my version.c (which was auto-generated and had my
svn repo revision in it) was always up to
When I was using autotools, I'd hook up a target version to
dist-gzip so that my version.c (which was auto-generated and had my
svn repo revision in it) was always up to date when I built my source
tarball. Is there a way to do that with cpack's package_source
target?
Doing the obvious:
