Re: [BBv2] Patch, review needed - support of Microsoft .idl files for MSVC

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2005-10-23 08:06:43

Alexey Pakhunov wrote:
> Reece Dunn wrote:
>>When building Reader.Core [IDL], it complains about being able to find 
>>ReaderCore.h. This is because the layout is:
>>
>> release/character-set-wide/ReaderCore.h
>> release/character-set-wide/windows-nt/ReaderCore.h
>>
>>This is because Reader.Core has <windows>nt, but ReaderCore doesn't. 
>>This suggests it isn't pulling in the include directory for ReaderCore 
>>like the initial version :(.
> 
> Give me some time to play with it.

This is not a bug with your MIDL code, but rather the way that the 
<implicit-dependency> feature works with a propagated feature. For 
example, given:

mstypelib core : core.idl ;
lib comobj : comobj.cpp : <windows>nt <implicit-dependency>core ;
exe comexe : main.cpp : <windows>xp <implicit-dependency>core ;

having:

feature windows : none nt 2k xp 2k3 vista : propagated composite ;

will cause the build to fail because:

msvc-7.1\release\windows-xp

is included by implicit dependencies and

msvc-7.1\release

is required for it to build properly. By changing this to incidental:

feature windows : none nt 2k xp 2k3 vista : incidental composite ;

the correct directory is added and things build correctly. Fixing this 
would be nice, but is not directly related to the MIDL patch.

>>[5] When rebuiling the project, I am getting:
>>
>>midl : command line error MIDL1020 : cannot open response file 
>>...\..\..\build\tools\speaker\reader\html\msvc-7.1\release\character-set-wide\ReaderHTML.tlb.rsp 
>>Could Not Find 
>>F:\devel\build\tools\speaker\reader\html\msvc-7.1\release\character-set-wide\ReaderHTML.tlb.rsp
> 
> I check this one too.

This is a response file (re)generation issue. Cleaning the build 
directory, using "bjam -a" or using my new response file issue solution 
fix this problem.

=====

These issues aren't directly related to the MIDL patch. Having had a 
chance to play with the new version, I do not have any issues with it 
and thus think that it should be included into BBv2.

- Reece