[6/6] oleaut32/tests: Add a bunch of new tests for typelib generation.

Alexandre Julliard julliard at winehq.org
Thu Nov 5 10:09:58 CST 2015


Alexandre Julliard <julliard at winehq.org> writes:

> Dmitry Timoshkov <dmitry at baikal.ru> writes:
>
>> Alexandre Julliard <julliard at winehq.org> wrote:
>>
>>> This is causing build warnings. I understand it may be deliberate in
>>> order to test that path, but a standard build should be warning-free so
>>> this needs to be done differently.
>>> 
>>> ../../../tools/widl/widl -o test_tlb.tlb -m32 -I. -I../../../include -D__WINESRC__ test_tlb.idl
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a753903}
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a753906}
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a75396b}
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a75396d}
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a753970}
>>> warning: duplicate uuid {016fe2ec-b2c8-45f8-b23b-39e53a753972}
>>
>> Frankly, I don't know how to avoid warnings for the things that intentionally
>> test things that cause these warnings. Do you have a suggestion how to avoid
>> warnings? Perhaps a widl flag to silence the warnings, and use it when building
>> the test_tlb.idl?
>
> The right way would probably be to implement midl_pragma warning(disable).

I put the patch in and silenced the warning for now. We can re-enable it
once there's a way to avoid it in the test.

-- 
Alexandre Julliard
julliard at winehq.org



More information about the wine-devel mailing list