Re: Finding out where output files are and changing it + precompiled headers

From: David Abrahams (dave_at_[hidden])
Date: 2005-07-07 14:46:52

Andrey Melnikov <melnikov_at_[hidden]> writes:

> David Abrahams wrote:
>> Andrey Melnikov <melnikov_at_[hidden]> writes:
>> 
>>>>This PCH thing becomes a common request. Recall that msvc has both "automatic" 
>>>>pch mode, that requires, IIRC, a single switch, and "manual" mode, that 
>>>>requires creating PCH once, and then using it from other targets. 
>>>
>>>I named "automatic" mode "hdrstop", because it requires #pragma hdrstop. 
>>> Borland compilers support #pragma hdrstop too, and Jamfile with 
>>><pch>hdrstop would be portable at least between intel-win, msvc and borland.
>> 
>> 
>> I don't like it; one of the things we're trying to do with Boost.Build
>> is to abstract away niggling little compiler dependencies like the
>> syntax used to implement automatic precompiled headers. I betcha
>> there are some linux compilers that have a similar functionality with
>> a different syntax.
>> 
> I didn't mean that Boost.Build's support for portable precompiled 
> headers must be portable across all compilers supporting precompilation.

I didn't think you did. I only object to the use of the name
"hdrstop" in the public interface of Boost.Build.

> I understand that there are compilers with completely incompatible 
> precompiled headers syntax. Trying to support precompiled headers in 
> portable projects like Boost is almost impossible.

I doubt it. I would like to have a non-implementation-specific
abstract name in the build system's public interface. That's why we
use <define> and not <-D> and <find-library> instead of <-l>

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com