Re: Build v1 custom targets (autogen source)

From: jfmeinel (boost_at_[hidden])
Date: 2004-08-28 17:48:10

--- In jamboost_at_[hidden], "Victor A. Wagner Jr." <vawjr_at_r...>
wrote:
> At Friday 2004-08-27 07:28, you wrote:
> 
> why do you want it rebuilt every time. One would hope that you'd
really 
> only want it built if version or gen_version.py had changed
> 
> 

Well, rebuilding each time isn't a requirement. I was thinking about
keeping a "build number" but that doesn't really matter. I guess with
a build number, what you would want is for it to be dependant on *all*
the source code, so that if anything changes, you get a new number.

But really that's more than I need.

What I really want, and what I haven't been able to figure out, is how
to use boost to recognize a dependency and be able to build something
that is considered source somewhere else.

I know how to create a "lib" or a "dll", etc, and then refer to it
later. It puts it in "bin/path/.../compiler/release/.../something",
but I would even be okay with that, so long as the compiler tool can
find it and compile it into an object file.

Sort of like a <src> tag. What I would really want is something as
simple as "when you need version.cpp, run generate_version.py"

Is this not possible under V1?

John
=:->