RE: [Freetype] Problems linking to freetype lib

[Ian Brown]

I agree with putting it in builds/win32.
Attached is the updated project file that uses the ftdebug.c from
builds/win32.

I made some additional changes to the project file:

There are now targets for both single and multi threaded builds. Plus the
default build is multi-threaded for MFC compatibility.

I also set the release build to create debug symbols. Because the symbols
are created in a separate file (the Program Database file), this does not
impact the size or performance of the release library ... it just makes it a
lot easier to track down errors.

Ian

-----Original Message-----
From: Werner LEMBERG [mailto:address@hidden 
Sent: Friday, January 18, 2002 9:58 AM
To: address@hidden; address@hidden
Cc: address@hidden
Subject: Re: [Freetype] Problems linking to freetype lib

> Here's my project file for reference.

Thanks, I've put it into the CVS.

> I have also included my copy of ftdebug.c. I changed this so that
> when using Win32, the trace output is sent to 'OutputDebugString' so
> that it appears in the debugger output window. The default method of
> sending it to stdout just causes it to get lost when running a MFC
> program.

Where shall I install this file?  IMHO it belongs to builds/win32 --
then the #ifdef WIN32 stuff could be removed.  Is this OK?

> On a slightly different note: Werner, I sent the font lc______.ttf
> to David but haven't heard anything back yet. Do you know if he got
> it? I'll try and investigate the problem some more today.

David seems to be on vacation...


    Werner

freetype.dsp
Description: Binary data