Re: [Boost-build] "metatargets"

From: Peter Foley (peter_at_[hidden])
Date: 2007-09-05 02:19:36

Hi Volodya,

> 
> Message: 1
> Date: Tue, 4 Sep 2007 21:41:57 +0400
> From: Vladimir Prus <ghost_at_[hidden]>
> Subject: [Boost-build] "metatargets"
> To: boost-build_at_[hidden]
> Message-ID: <200709042141.58143.ghost_at_[hidden]>
> Content-Type: text/plain;  charset="utf-8"
> 
> 
> This is something I've tried to do before, but found it again in

Yep you have tried to do this before.  Gmane appears to be down but I
have found my response to your original email (20 Jan 2007).  Not sure
if you have slightly changed the focus of your question as you were
originally talking about the documentation.

Here is a link to my original reply:
http://lists.boost.org/boost-build/2007/01/16075.php

I will copy my original reply text across as I feel that it is still
applicable for this discussion.  Admittedly I am not sure if this helps
as you never replied to the original email so maybe it wasn't a good
suggestion?

-------------- Old email -------------------
Hi Volodya,

I have been finding the re-use of particular words for different
meanings
within the documentation to be confusing as well.

Although I know I am still green around the ears when it comes to
Boost.Build here is how I would currently define (Main) "Target" from
reading the documentation:

"Target -

A target has two meanings:

Firstly - this is what you expect to be generated when you execute
Boost.Build. Examples of this include Executables (exe), Portable
Document
Format (pdf) and Hypertext Markup Language (html). For information on
all
the possible target types refer to the Boost.Build manual.

Secondly - a target can be made up of many other targets that ultimately
contribute to the output of the main target."

I know this is an over-simplification but it helps me when I start to
get
lost within the documentation.

>From my still new to Boost.Build perspective what I believe this boils
down
to is that the Main Target is the expected result(s).

So from this simplistic view I suggest you rename "Main Target" to
"Result".
For what it is worth here is how I would define it:

"Result - This is used by a user to specify the expected output(s) after
the
completion of processing your jamfile by Boost.Build.

You can define one or more Results within your Jamfile (eg executables
via
the "exe" result, user documentation via the "pdf" result and even have
Boost.Build initiate the running of your Unit-Tests!! After building the
executable(s)).

Some of the currently supported results within Boost.Build include
Executables (exe), Portable Document Format (pdf) and Hypertext Markup
Language (html). For information on all the possible target types please
refer to the Boost.Build manual."

To put it simply when you run Boost.Build you initiate a process (one or
more targets) that will ultimately output a result (Main Target(s)).

Not sure if this was what you were looking for but I hope it helps.

Peter.
-------------- Old email -------------------