Thanks for sharing...

Anyway, the armcc4.1 is still used for our project... and now theQtCore can be 
successfully build out, but I still have one C++ template related error in 
qtnetwork module as bellow:

    "access/qnetworkrequest_p.h", line 94: Error:  #2574: explicit 
specialization of class "QTypeInfo<QPair<QByteArray, QByteArray>>" must precede 
its first use (at line 105 of 
"../../include/QtCore/../../src/corelib/tools/qlist.h")
      Q_DECLARE_TYPEINFO(QNetworkHeadersPrivate::RawHeaderPair, Q_MOVABLE_TYPE);

Code of qnetworkrequest_p.h:
L1:  class QNetworkHeadersPrivate
L2:  {
L3:  public:
L4:      typedef QPair<QByteArray, QByteArray> RawHeaderPair;
L5:      typedef QList<RawHeaderPair> RawHeadersList;
L6:  ...
  };

L94:  Q_DECLARE_TYPEINFO(QNetworkHeadersPrivate::RawHeaderPair, Q_MOVABLE_TYPE);

And the above code indicates that QList<RawHeaderPair> (L4) will firstly use 
the QTypeInfo<RawHeaderPair>, which is declared in last code L94.
So it seems an error, but does anyone know how to fix it ? or how to ignore 
such error ?

Thanks,
Song

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
ext Thiago Macieira
Sent: Monday, June 04, 2012 7:20 PM
To: [email protected]
Subject: Re: [Development] mkspec "linux-arm-armcc " for qt5

On segunda-feira, 4 de junho de 2012 08.32.03, [email protected] wrote:
> Hi,
> 
> We are trying to use armcc to build qt5, and meet many compiling issues...
> Here, I just want to confirm that is there some assumption / 
> limitation in our qt5 code base about use armcc or gcc ???

I don't think anyone has compiler using that compiler for months or even years.

It's completely untested. Here there be dragons.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to