'Re: [Kde-bindings] Common work for Qt4 bindings'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    Re: [Kde-bindings] Common work for Qt4 bindings
From:       Luca Fascione <lukes () wetafx ! co ! nz>
Date:       2005-09-10 4:56:56
Message-ID: 43226798.7010101 () wetafx ! co ! nz
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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

[Attachment #5 (text/html)]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hmmm...<br>
well but wouldn't the source for moc be the natural candidate to look
at for this task?<br>
I mean, it's guaranteed to know about what's going on, at least from
Qt's point of view...<br>
<br>
Lukes<br>
<br>
Marcus wrote:
<blockquote cite="mid200509092346.19790.mathpup@mylinuxisp.com"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">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)
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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.
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Luca Fascione
Pipeline Engineer - Weta Digital

+644 380 9170 (x4855) / +64 21 0764 862
</pre>
</body>
</html>

_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings

[prev in list] [next in list] [prev in thread] [next in thread] 