> Problem:
> 1. On OSX, FLTK (FLTK 1.3 shapshot 8048, and earlier too) includes draw
> in OSX specific Objective-C/C++ 2.0 include files, that can only be
> compiled with Apple supplied GCC variants. Apple-GCC seems to be stuck
> at versions 4.0 and 4.2.
>
> 2. The included OSX headers also cause name collisions with some
> software that has not been designed to include OSX-specific header
> files. For example, there is a name collision with "Cell" as defined by =
> the included OSX headers and "Cell" defined in GNU Octave. (This at
> least when compiling 64-bit, have not tested this with 32-bit.)
>
> 3. It would be great if it was possible to use FLTK also with non-Apple
> GCC versions, especially when compiling portable (non-OSX) code, that
> relies on FLTK for UI portability (which I presume is the whole point
> with FLTK !)
>

Starting from FLTK-1.3.r8113, you can compile client programs
that use the public API of FLTK without including any system header
files (unless your files themselves ask for such inclusion).
Presumably, non-Apple GCC variants will now work because they won't
find any Apple specificity. There won't be any name collision.
Nothing special is needed (in particluar you don't need to define
__CARBON__).
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to