|
![](/i/fill.gif) |
JRG wrote:
> As far as Qt is concerned... are you running moc by yourself?
> You known, qmake uses the HEADERS variable to look for Q_OBJECT classes.
I see. No, I'm a Qt newbie. I just worked out this weekend how to compile
something outside of the Qt subdirectories. :-) {To be fair, it's
cross-compiled from a VM to a piece of hardware that doesn't have any
keyboard or mouse, so it's not like it's trivial.}
> If your private class contains that macro, just try and include the
> generated .moc directly.
Cool. It's easy enough to put it in a separate .h file. It just surprised
me. Looking at it, I thought Q_OBJECT was a #define, not some tag for a
separate preprocessor.
You know something else that surprises me? That I can screw up the
compilation enough to get G++ outputting assembler that the assembler
doesn't understand. I can't imagine why I can invoke G++ with arguments
that, in one execution, would compile C++ to assembly, then pass that
assembly to the assembler for the wrong architecture. Weird.
--
Darren New, San Diego CA, USA (PST)
Insanity is a small city on the western
border of the State of Mind.
Post a reply to this message
|
![](/i/fill.gif) |