windows build

[Thiago Macieira]

Christian Ehrlicher wrote:
>
>Q_CORE_EXPORT is correct - it must be an export in *every* lib it is
>used (because of this it's KDE_EXPORT and not KIO_EXPORT)

Then no, this isn't the same at all. Q_CORE_EXPORT means export from 
QtCore (which is where QList comes from and, more to the point 
QVariantList comes from).

But, apparently, what you want is Q_DECL_EXPORT.

And, no, I don't think this is correct at all. There has to be another 
solution. In Qt3, QCString inherited from QMemArray<char> and there's no 
such exporting trickery.

In Qt4, we have very, very similar cases:
class Q_GUI_EXPORT QPolygon : public QVector<QPoint>
class Q_GUI_EXPORT QItemSelection : public QList<QItemSelectionRange>

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
  thiago.macieira (AT) trolltech.com     Trolltech ASA
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20060627/ec2397a3/attachment-0001.pgp