dbus errors

[Christian Ehrlicher]

Jeff Mitchell schrieb:
> Christian Ehrlicher wrote:
>> Jeff Mitchell schrieb:
>>> Jeff Mitchell wrote:
>>>> Peter Kümmel wrote:
>>>>> Christian Ehrlicher wrote:
>>>>>>> Unfortunately, it doesn't produce anything.  It just shifts the errors 
>>>>>>> down by one line...no warnings about previous definitions of interface 
>>>>>>> are given.
>>>>>>>
>>>>>>> However, doing:
>>>>>>> #undef interface
>>>>>>>
>>>>>>> Makes compile work again.
>>>>>>>
>>>>>>> How do I solve this?  It's probably a result of including some of the 
>>>>>>> various Microsoft files I needed to include in order to get WMI 
>>>>>>> methods written.  But I don't really want to #undef things that are 
>>>>>>> supposed to be defined willy-nilly, nor can I expect that "patch Qt" 
>>>>>>> is a reasonable answer  :-)
>>>>> You could also remove "interface" in the Qt header or rename it, the
>>>>> name isn't important in the header:
>>>>>
>>>>> static QDBusMessage createSignal(const QString &path, const QString
>>>>> &interface_this_name_is_totally_arbitrary, const QString &name);
>>>>>
>>>>> Then we could try to post a patch to Trolltech not to use "interface"
>>>>> as name for variables in declaration.
>>>> Thiago, is there a snowball's chance in hell of this happening?
>>>> (especially in 4.4?)  I'm including some standard include headers in my
>>>> files on Windows to query WMI for hardware information.  I'm still 
>>>> trying to pinpoint the exact MS include file that is causing 
>>>> this...there are several that #define interface, but so far none that 
>>>> appear in my includes list...but I haven't been able to check the normal 
>>>> VC includes yet (i.e. I don't *think* that any of the Win2K3 SDK ones 
>>>> are defining it).
>>> Testing this, I forgot that there's a method named interface()...it 
>>> doesn't only appear in unimportant places.  Which means that to change 
>>> it would be to break API...not going to happen.  Not sure if an "#undef 
>>> interface" might be possible...
>>>
>> Are you really sure it's the 'interface' which screws up your build? 
>> e.g. did renaming the variable name to something other work?
> 
> "#undef interface" put in before line 75 fixes build.
> 
fine. then a

#define interface whatever

should emit a warning because of a redeclaration.


Christian