From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-11-20 10:26:45
Reece Dunn wrote:
>> I have attached a patch to add PCH support to the msvc toolset. This
>> is most likely the most complex toolset to get PCH support on, so
>> extending this for other toolsets should be trivial.
>
There is one more problem. If a target that uses PCH depends on another
target using PCH the top most one gets two <pch-header> and two
<pch-file> properties - one from each target. For example:
---- core/jamfile.v2 ----
pch stdafx
:
stdafx.h stdafx.cpp
;
lib core
:
stdafx
...
:
<link>shared
;
----
---- client/jamfile.v2 ----
pch stdafx
:
stdafx.h stdafx.cpp
;
lib client
:
stdafx
...
../core//core
:
<link>shared
;
----
I'm trying to find a way to remove <pch-xxx> properties from usage
requirements of LIB, SHARED_LIB, EXE and such targets. Maybe there is a
better way of doing it.
Best regards/Venlig hilsen,
Alexey Pakhunov.