Re: [ft-devel] Windows x64 Build Re: Freetype-devel Digest, Vol 105, Issue 12

[Hin-Tak Leung]

Just wish to point out that a copy of the whole of freetype is bundled with
ghostscript, and ghostscript has been routinely built for win64 for quite a few 
years.
For as long as it was, the preferred compiler for building ghostscript for 
windows
has always been MS VC.

If you ask nicely, the Artifex folks might be happy to try things out for you,
afterall, since ghostscript depends heavily on freetype. Much of the Artifex's
commercial interests in ghostscript is windows-based, and most
of the ghostscript developers have a windows-based development set-up.
In fact AFAIK, Ken Sharp is almost exclusively windows-based; they should be
able to advise on windows-based development practices.

visual studio indeed generates a few large temporary files for tracking 
dependencies,
and/or contains various not-useful local machine/user-specific information,
which should not be committed.

Also, visual studio 2008+(?) express is freely downloadable and runs quite well 
with
wine, and wine's 64-bit windows emulation is sufficient for 64-bit ghostscript 
to run
as far as I remember. (and since freetype is bundled and built with ghostscript,
by extension "it should all just work".)

I build ghostscript with MS VC once in a while under wine that way. Mostly 
whenever
I need to make extensive changes which may affect things outside my usual 
unix-based usage.

<snipped>
 ------------------------------
 
 Message: 2
 Date: Tue, 22 Oct 2013 10:21:09 +0200 (CEST)
 From: Werner LEMBERG <address@hidden>
 To: address@hidden
 Cc: address@hidden,
 address@hidden
 Subject: Re: [ft-devel] Windows x64 Build
 Message-ID: <address@hidden>
 Content-Type: Text/Plain; charset=us-ascii
 
 
 > Ok, it's done. File is attached as 7zip file.
 
 Thanks.  Since this is a 15MByte archive, you won't see
 it on the
 list.
 
 Some observations while doing a diff between the archive and
 the git:
 
   o It seems that the vc2010 files can be used out of
 the box for
     Visual Studio 2012 and 2013 also, which would
 be good.
 
   o I will neither put the (extremely large) .sdf nor
 the .suo files
     into the git repository.  According to
 info in the net, those
     files are regenerated as soon as you open the
 project files.
 
   o Do I need a special `win64' directory at all? 
 It seems to me that
     your new project files simply add a 64bit
 option; there isn't any
     other change I can recognize.  This would
 greatly simplify the
     whole issue.
 
     To test that, I ask you to start with a
 freshly unpacked FreeType
     archive, then overwrite the three files in
 `builds/win32' with the
     files from your `builds/win64'. 
 Theoretically, this should be
     sufficient to see a 64bit build option.
 
 Please comment.
 
 
     Werner
<snipped>