Opened 16 years ago
#167 new defect
PCH and <implicit-dependency> with msvc toolset
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | component1 | Version: | |
| Keywords: | Cc: |
Description
[originally reported here (with a test case): http://article.gmane.org/gmane.comp.lib.boost.build/17237/]
It seems that the msvc toolset (trunk version) handles PCH incorrectly in case there is <implicit-dependency> feature in target requirements.
The test case mentioned above demonstrates the problem. It comprises of two projects /proj1 and /proj2, /proj2 has <implicit-dependency> on /proj1 in its requirements.
'bjam /proj2 msvc' fails with the following error:
... fatal error C1010: unexpected end of file while looking for precompiled header. Did you forget to add '#include "precompiled.pch"' to your source?
I think msvc toolset puts "precompiled.pch" instead of "precompiled.h" to cl.exe command line.
'bjam /proj2 gcc' works fine. When <implicit-dependency> is removed, msvc compiles fine as well.
