--- Peter Donald <[EMAIL PROTECTED]> wrote:
> > <td align="center" valign="top">No. No target will be run if
> > omitted.</td>
>
> -1
>
> Don't like it one bit but I guess you knew that. Other build tools do
> not work this way, they have a default build process if none is
> specified.
I thought that's what this amounted to -- the default process being to
execute all those things outside of any target. What do you mean by
"default build process"?
> If you were to allow the default attribute to default to something
> meaningful (ie "main") then fine but dont think it should dfefault
> to no process.
But then wouldn't it just do "main" and stop there? I thought this idea
was to do everything outside of any target, then do whatever target(s) was
specified, or a default, if there is one, and no target was specified.
Personally, I like the idea of having the option to put all the
really-do-always-want-these-things-done-before outside of any target, and
limit an "init" ("prepare", "main", whatever) to only those things that
should be done only for specific targets that 'depends' on it.
I don't think it's completely unique, either -- Jam does something
similar. You can have a Jamfile that defines vars/rules/actions "outside
of any target" (not really Jam-speak, but basically the same idea), have a
bunch of Echo's, and a zillion targets. If none of the targets are
associated with a rule that depends (directly or eventually) on one of the
pseudo-targets that depends on the "all" pseudo-target (think of it as
'default'), then just saying 'jam' (without a target) will set all those
vars/rules/actions and it'll run the Echo's, but that's all it'll do.
Diane
=====
([EMAIL PROTECTED])
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
