PCH interface question

Hi,
on gcc, to create a PCH one needs a header. On msvc, one
needs a header and 
a .cpp file. This can be expressed like this:

   pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;

which is a bit verbose. How about allowing the user to
write:

   pch boost : boost.hpp boost.cpp ;

and simply ignore .cpp when it's not needed?

- Volodya

-- 
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Sunday 08 October 2006 00:04, Vladimir Prus wrote:
> Hi,
> on gcc, to create a PCH one needs a header. On msvc,
one needs a header and
> a .cpp file. This can be expressed like this:
>
>    pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;
>
> which is a bit verbose. How about allowing the user to
write:
>
>    pch boost : boost.hpp boost.cpp ;
>
> and simply ignore .cpp when it's not needed?

Getting no comments, I've implement this.

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On 14/10/06, Vladimir Prus <ghostcs.msu.su> wrote:
> On Sunday 08 October 2006 00:04, Vladimir Prus wrote:
> > Hi,
> > on gcc, to create a PCH one needs a header. On
msvc, one needs a header and
> > a .cpp file. This can be expressed like this:
> >
> >    pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;
> >
> > which is a bit verbose. How about allowing the
user to write:
> >
> >    pch boost : boost.hpp boost.cpp ;
> >
> > and simply ignore .cpp when it's not needed?
>
> Getting no comments, I've implement this.
>
The cpp file is just one #include "boost.hpp"
line. Can we generate it
using the mechanism designed for RSP files?

-- 
Andrei
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Monday 16 October 2006 19:19, Andrei Melnikov wrote:
> On 14/10/06, Vladimir Prus <ghostcs.msu.su> wrote:
> > On Sunday 08 October 2006 00:04, Vladimir Prus
wrote:
> > > Hi,
> > > on gcc, to create a PCH one needs a header.
On msvc, one needs a header
> > > and a .cpp file. This can be expressed like
this:
> > >
> > >    pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;
> > >
> > > which is a bit verbose. How about allowing
the user to write:
> > >
> > >    pch boost : boost.hpp boost.cpp ;
> > >
> > > and simply ignore .cpp when it's not needed?
> >
> > Getting no comments, I've implement this.
>
> The cpp file is just one #include "boost.hpp"
line. Can we generate it
> using the mechanism designed for RSP files?

Good idea! Will things work no matter what directory the
.cpp file is 
generated to?

Thanks,
Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On 16/10/06, Vladimir Prus <ghostcs.msu.su> wrote:
> On Monday 16 October 2006 19:19, Andrei Melnikov wrote:
> > On 14/10/06, Vladimir Prus <ghostcs.msu.su> wrote:
> > > On Sunday 08 October 2006 00:04, Vladimir
Prus wrote:
> > > > Hi,
> > > > on gcc, to create a PCH one needs a
header. On msvc, one needs a header
> > > > and a .cpp file. This can be expressed
like this:
> > > >
> > > >    pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;
> > > >
> > > > which is a bit verbose. How about
allowing the user to write:
> > > >
> > > >    pch boost : boost.hpp boost.cpp ;
> > > >
> > > > and simply ignore .cpp when it's not
needed?
> > >
> > > Getting no comments, I've implement this.
> >
> > The cpp file is just one #include
"boost.hpp" line. Can we generate it
> > using the mechanism designed for RSP files?
>
> Good idea! Will things work no matter what directory
the .cpp file is
> generated to?
>
As long as the header is on the include search path. But I
think it's
better to try first. Maybe even explicit header path will
work during
the generation (e.g. /Ycpch.hpp but #include
../../../pch.cpp or
include d:/.../pch.hpp
-- 
Andrei
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Monday 16 October 2006 19:19, Andrei Melnikov wrote:
> On 14/10/06, Vladimir Prus <ghostcs.msu.su> wrote:
> > On Sunday 08 October 2006 00:04, Vladimir Prus
wrote:
> > > Hi,
> > > on gcc, to create a PCH one needs a header.
On msvc, one needs a header
> > > and a .cpp file. This can be expressed like
this:
> > >
> > >    pch boost : boost.hpp :
<toolset>msvc:<source>boost.cpp ;
> > >
> > > which is a bit verbose. How about allowing
the user to write:
> > >
> > >    pch boost : boost.hpp boost.cpp ;
> > >
> > > and simply ignore .cpp when it's not needed?
> >
> > Getting no comments, I've implement this.
>
> The cpp file is just one #include "boost.hpp"
line. Can we generate it
> using the mechanism designed for RSP files?

I think I have it working. One question -- is there any
reason to ever want 
explicitly write the .cpp file? If yes, I'll allow both
specifying file 
explicitly or generating it. If no, I'll disallow explicit
file.

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:
>> The cpp file is just one #include
"boost.hpp" line. Can we generate it
>> using the mechanism designed for RSP files?
> I think I have it working. One question -- is there any
reason to ever want 
> explicitly write the .cpp file? If yes, I'll allow both
specifying file 
> explicitly or generating it. If no, I'll disallow
explicit file.
Code in PCH .cpp files is sometimes used in programs which
use the old 
versions of ATL library or VBA SDK.

-- 
With respect,
             Alex Besogonov (cyberaxelewise.com)

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build