dbus errors

[Jeff Mitchell]

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).


>> I've also PSDK 2003 and MSVC8SP1 Express and it works fine for me.
> 
> Is this the same SDK Jeff uses?

Yes, and it works fine for you because my code isn't in SVN yet.  I
wasn't going to commit non-compiling code, and likewise I can't commit
code that relies on modifications to Qt headers.

> Maybe it it possible to suppress the including of the header defining
> interface by using a macro when building qt.

I rather doubt it, as it's a Microsoft include file.


--Jeff