Hmmm...
well but wouldn't the source for moc be the natural candidate to look at for this task?
I mean, it's guaranteed to know about what's going on, at least from Qt's point of view...

Lukes

Marcus wrote:
My idea is to separate 3 stages:
1 - query the C++ for classes, functions and enums, and all Qt specific
info (not sure if GCCXML can handle this part)
    

Qt's "extensions" to C++ like "signals", "slots", "Q_PROPERTY" end up getting 
#defined away or defined in other C++ things so that they are not 
recognizable to GCC, and GCCXML only sees what GCC would see.

I was looking into whether there is some clever way via macros or something 
that would permit GCCXML to see these extensions. It's see a few months since 
I looked at this.
  

-- 
Luca Fascione
Pipeline Engineer - Weta Digital

+644 380 9170 (x4855) / +64 21 0764 862