From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2007-09-05 03:31:25
Vladimir Prus wrote:
> This is something I've tried to do before, but found it again in
> my todo list. Now, we call 'exe', 'lib' and other things
> you define in Jamfiles a 'main target'. Inside code, we have 'virtual
> targets', that are more like files. This 'main target' term seems
> confusing. How about calling it 'metatarget'? In user documentation,
> we'll define it as 'metatarget', but since user cannot define
> anything else, we'll use 'target' is synonym for 'metatarget'.
>
> In code, we'll have 'metatarget' and 'virtual-target'.
"meta-target" for better consistency?
> Of course,
> the rename
> in code probably won't happen until Python port is done,
Whoa! Is it really accepted that the main Boost.Build development path will
lead to a Python port? One of the main reasons for me using BB is the lack
of other dependencies than BJam (requiring only a C compiler) and the
Boost.Build sources/scripts.
[snip rest]
/ Johan