Yes, I used VS 2012 to make the changes.
Ok, it's your repository.
Well, I think that the separated win64 directory makes it obvious to users who
want to build for that platform what to do. I had to do all this searching
around, and if I were not so outgoing I may have just suffered a lack of
fuition and given up. That's not good, and leaving the folder in there is less
work than taking it out, and I think that it's there strictly for helping other
developers like me in the future. I spent probably 2 hours looking around at
the Makefile and other files for building it I thought were pertinent to a
mingw64 route to compile it, and went unsuccessfully down this path needing a
64 bit freetype.
And you're right. Those, and the specification of the compile results
directory, are the only changes that I've made.
Well I don't understand why. The win64 directory builds a correct freetype lib
file for 64 bit platforms. We're helping the users this way. What is the final
outcome? By the way, if you're wanting verification that the win64 does build
successfully by asking me to test it, I had to build freetype as a dependency
of a 64 bit project I was compiling all night last night, so it definitely
works.
On Tuesday, October 22, 2013 3:21 AM, Werner LEMBERG <[email protected]> wrote:
> 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
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
