Re: How to build freetype .dll using bcc++

> How to build freetype .dll using the makefile for BCC free command
> line compiler?  If any makefile sample, please send me or tell me
> how to build. Thanks

[I assume that you are talking about FreeType 2.1.7.]

What does

  make
  make

produce?  AFAIK, BCC should be recognized (see file
builds/compiler/bcc.mk).

You need GNU make!

    Werner

Compiling on the Texas DSP

Hello,

   I am using the freetype engine on a Texas DSP - 55xx.

   After changing enumerations FT_IMAGE_TAG and FT_ENC_TAG to their 16 
bit equivalents the project does compile.
   Some warnings were issued regarding shift counts being too large (e.g 
<long variable> = <char variable> << 24).Fixed by casting.

   I try to run the sample (copied from the tutorial), and I get a error 
returned "bad format" when trying to open arial.ttf
The function that returns the error is

" error = FT_New_Face( library,"c:\\winnt\\fonts\\arial.ttf",0,&face);
 if ( error == FT_Err_Unknown_File_Format )"

   The same code project compiled on Borland Builder, compiles and runs 
fine no errors.

   Tracing through the code I believe I have found where the problem lies,

   The smallest types on this Texas unit are 16 bits in size. Chars are 
16 bits in size.
   Sizeof a char is returned as 1, size of a long is returned as 2.
   In the function FT_Stream_ReadFields in FTStream.c the following code 
does not work as intended.

  /* finally, store the value in the object */
     p = (FT_Byte*)structure + fields->offset;
     switch ( fields->size )

Re: Compiling on the Texas DSP

[FreeType 2.1.7]

> Some warnings were issued regarding shift counts being too large
> (e.g <long variable> = <char variable> << 24).Fixed by casting.

Please send a log of the compiler warnings for further inspection.

> The smallest types on this Texas unit are 16 bits in size. Chars are
> 16 bits in size.  Sizeof a char is returned as 1, size of a long is
> returned as 2.

How did you configure FreeType?  In ftconfig.h there is a test using
FT_ULONG_MAX to find out the size of a long.  Theoretically your
compilation process should abort because `long' has to be >= 4.

What actually is a 4-byte wide type on your platform?  `long long'?

> case 4: here is used to store UInt32 values into the structure.  On
> a DSP the sizeof a long is returned as 2 and hence long values are
> stored using case 2: .  Data is lost and the font header is assumed
> corrupt.

Thanks for investigating.

> I can fix this problem but would like to know if anyone has tried to
> compile to the Texas DSP compilers before.  I would like to know how
> many problems I am likely to encounter because of this Sizeof
> peculiarity.

If you can provide a 4-byte entity no problems should happen.

Re: [Devel] Re: Compiling 2.1.7 on Mac OS X

Yes, this patch works.  You should also remove the XX_ANSICFLAGS in configure 
(which tried to remove -ansi, is misspelled so it doesn't work, and is not 
needed with this patch.)

On Wednesday 31 March 2004 01:54 pm, Werner LEMBERG wrote:
> > This seems to work.  I'm not sure how this is supposed to be quoted.
> > CFLAGS="$CFLAGS -DOS_INLINE='static __inline'" produces
> > "-DOS_INLINE=static __inline" on the command line so I guess it's
> > okay.
> >
> > The system headers say:
> > #ifndef OS_INLINE
> > #define OS_INLINE static inline
> > #endif
> >
> > so this seems to be valid.
>
> I suggest a different patch, see below.  Please test.
>
>
>     Werner
>
>
> ======================================================================
>
> --- ftmac.c	Sat Mar 20 15:19:59 2004
> +++ ftmac.c.new	Wed Mar 31 23:51:56 2004
>  <at>  <at>  -66,6 +66,8  <at>  <at> 
>  #ifdef __GNUC__
>  #include "../truetype/ttobjs.h"

visual c project

Re: visual c project

Zivan,

> I have downloaded the latest freetype release 2.1.7.  If I open the
> visualc project file *.dsw and *.dsp, nothing shows up.
> Is there anything wrong in my download or I am missing some step.  Please
> advice.  I am using Visual Studio 6.

When you say "nothing shows up," do you mean there are no source files in
the editor window, or that even the "File View" tab on the left side is
empty?

    Thanks,
    PeterM

Re: visual c project

Re: visual c project

Re: visual c project

(no subject)

To : David Turner

Hi David,

we have customer who is using freetype and he would be interested in using
stroke fonts with the FT rasterizer.
Does FT support stroke fonts in any way, or could it be implemented easily as a
kind of PlugIn provided we would supply a stroke font with an open format ?

Thanks for your help.

Juergen Willrodt