[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freetype] FreeType 2.0 SNAFU
From: |
Werner LEMBERG |
Subject: |
Re: [Freetype] FreeType 2.0 SNAFU |
Date: |
Fri, 01 Dec 2000 01:02:20 +0100 (CET) |
> Cpp-calculated include paths are not considered portable across all
> compilers. This is even true for C++ compilers.
??? Please explain.
> Take care with file extensions since Windows likes to associate
> programs with extensions. There is no telling what it does with
> extensions on directory names.
As said in another mail, my suggestion is now obsolete.
> It seems unfortunate to require the build environment to pass a -D
> option to allow the headers to work. Other package's headers "just
> plain work". Why can this not be true for FreeType as well?
No need to worry. Wait a bit for the new code.
Werner
- [Freetype] FreeType 2.0 SNAFU, Bob Friesenhahn, 2000/11/29
- Re: [Freetype] FreeType 2.0 SNAFU, Werner LEMBERG, 2000/11/29
- Re: [Freetype] FreeType 2.0 SNAFU, Stefan Seefeld, 2000/11/29
- Re: [Freetype] FreeType 2.0 SNAFU, Werner LEMBERG, 2000/11/29
- Re: [Freetype] FreeType 2.0 SNAFU, Stefan Seefeld, 2000/11/29
- Re: [Freetype] FreeType 2.0 SNAFU, Werner LEMBERG, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU, Stefan Seefeld, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU, Werner LEMBERG, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU, Bob Friesenhahn, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU,
Werner LEMBERG <=
- Re: [Freetype] FreeType 2.0 SNAFU, Bob Friesenhahn, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU, David Turner, 2000/11/30
- Re: [Freetype] FreeType 2.0 SNAFU, Werner LEMBERG, 2000/11/30