Re: [jamboost] Building the dependency graph

From: David Abrahams (dave_at_[hidden])
Date: 2002-07-24 07:22:09

Hi Vladimir,

I just want to say: you have my admiration and gratitude for pressing
forward with this. Thanks, you rule!

-Dave

----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
To: <jamboost_at_[hidden]>; "Markus Sch?pflin"
<markus.schoepflin_at_[hidden]>
Sent: Wednesday, July 24, 2002 6:01 AM
Subject: Re: [jamboost] Building the dependency graph

>
> Hi Markus,
>
> Markus Schöpflin wrote (long ago):
> > Ok, here we go...
> >
> > Use case for various compiler tools from microsoft.
> > [snip]
>
> Ok, now I'm looking at your diagram, which is now part of
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/tools/build/new/
m2-transformations.txt?rev=HEAD&content-type=text/vnd.viewcvs-markup
> to see what problems it presents for us.
>
> I've some initial questions, and would appreciate if you could clarify
them
>
> 1. Is *.bsc file created for each executable file, or for the whole
project?
> 2. Is creation of precompiled headers an explicit operation? I.e. would
it be
> reasonable to require something like:
>
> precompiled_headers my_project_pch : stdafx.cpp ;
>
> 3. How files compiled with and without precompiled headers are separated?
Can
> we assume that sources for each main target all either use PCH or don't
use
> them. That would allow to write
>
> lib a : a.cpp ;
> lib b : b.cpp my_project_pch ;
>
> Or is finer granularity required?
>
> TIA,
> Volodya
>
>
> To unsubscribe from this group, send an email to:
> jamboost-unsubscribe_at_[hidden]
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>