Erik Hofman wrote:
>
> Christian Mayer wrote:
>
>
> > Anyway, could all
> >
> > #include
> >
> > lines be changed back to
> >
> > #ifdef HAVE_ZLIB
> > # include
> > #else
> > # include
> > #endif
> >
> > w/o causing any trouble? This would help me. I wouldn't need any other
> > chang
Christian Mayer wrote:
> Anyway, could all
>
> #include
>
> lines be changed back to
>
> #ifdef HAVE_ZLIB
> # include
> #else
> # include
> #endif
>
> w/o causing any trouble? This would help me. I wouldn't need any other
> change as the directories are still there.
You have t
"Curtis L. Olson" wrote:
>
> Christian Mayer writes:
> > Hi,
> >
> > is there a reason why SimGear/misc/zfstram.hxx was changed from
> >
> > #ifdef HAVE_ZLIB
> > # include
> > #else
> > # include
> > #endif
> >
> > to
> >
> > #include
> >
> It was a slight phylisophical shift. Although zlib
Christian Mayer writes:
> Hi,
>
> is there a reason why SimGear/misc/zfstram.hxx was changed from
>
> #ifdef HAVE_ZLIB
> # include
> #else
> # include
> #endif
>
> to
>
> #include
>
> ? As ZLIB isn't standard (perhaps except on Linux) it's great to have
> the fallback to the supplied ver
Christian Mayer wrote:
>
> Hi,
>
> is there a reason why SimGear/misc/zfstram.hxx was changed from
>
> #ifdef HAVE_ZLIB
> # include
> #else
> # include
> #endif
>
> to
>
> #include
Apart from fixing all occurances of the single #include FGFS
complied staight away under MSVC!! (If I'd h
Hi,
is there a reason why SimGear/misc/zfstram.hxx was changed from
#ifdef HAVE_ZLIB
# include
#else
# include
#endif
to
#include
? As ZLIB isn't standard (perhaps except on Linux) it's great to have
the fallback to the supplied version. And adding the additional include
directories to Z
