> Also, the failure to compile threads.cxx looks like it might
> be "interesting" too... I wonder if this is a mingw issue, or
> general win32 issue?
> Looks to be some sort of typedef clash, but I can't
> immediately see exactly what...
>
> Note that explicitly including <windows.h> before we include
> the fltk3 headers "fixes" this problem, so something in the
> fltk3 headers is causing the windows headers to expand some
> macro or other that causes a problem, I guess...
>
> Compiling threads.cxx...
> In file included from
> d:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/objb
> ase.h:71,
> from
> d:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/ole2.h:9,
> from
> d:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/wind
> ows.h:114,
> from threads.h:61,
> from threads.cxx:36:
> d:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/wtyp
> es.h:141: error: `typedef double fltk3::DOUBLE' redeclared as
> different kind of symbol
> ../fltk3/enumerations.h:843: error: previous declaration of
> `fltk3::Mode fltk3::DOUBLE'
Looking in my copy of wtypes.h, at line 141 I actually have:
typedef double DOUBLE;
This appears to be getting expanded at compile time as:
typedef double fltk3::DOUBLE;
Which then clashes with the definition "fltk3::Mode fltk3::DOUBLE" in
our enumerations.h.
So - I wonder if this is a mingw issue or a gcc issue, or maybe we
genuinely have a problem...
I wonder if we are having some sort of namespace issue here, i.e. have
we done a "using namespace fltk3" or whatever, and then somehow made it
look to the compiler as if all the windows.h stuff is inside the fltk3
namespace, or...? Just guessing...
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
