On Monday, 9 de January de 2012 13.43.52, Stephen Kelly wrote: > On Monday, January 09, 2012 10:36:11 Thiago Macieira wrote: > > And a hint: whenever you get an error from the compiler that doesn't make > > sense at all, check the preprocessed output. > > And if you don't have enough access to do that, start googling for whatever > is on the problem lines together with '#define' :).
Ah, yes.
I doubt many people have access to an HP-UX machine that has the #define
m_volume (or was it IRIX?).
Also note you can't define variables called unix or linux:
$ gcc -E -dM -xc /dev/null | grep -v _
#define unix 1
#define linux 1
I'd also avoid calling one windows.
--
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
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
