I didn't think about the suggestions before I made them, but they turned out to
be very easy fixes. I think that with this new win64 folder, it is very
straight forward for users to build for their platform; they are bound to look
for this just like I did. :)
On , Kenneth Miller <[email protected]> wrote:
Actually, I think this too is also very straight forward; all you need to do is
follow the instructions below. (Trust me, this is better than me providing you
files to copy and manipulate only to get confused :) ).
Copy the original freetype-2.5.0.1\builds\win32\vc2010 to
freetype-2.5.0.1\builds\win64\vc2010
Apply the changes mentioned in the previous email.
Then apply the following:
1. On the menu bar, choose Project, Properties.
2. Expand the Configuration Properties node, and choose General.
3. Change the Output Directory value to the new output directory.
On Monday, October 21, 2013 12:51 AM, Werner LEMBERG <[email protected]> wrote:
> Actually, I found that the freetype library can be quickly built for
> visual studio by doing the following: [...]
Very good.
> So, rather than you showing how to compile for x64, I think it more
> fitting that you assist users in the future; hosting the directions
> on the website as well as placing a win64 folder in there by going
> about the business of naming the target folders for 64 all proper
> and the like would be suitable. Then, for any future zip file
> releases, you can offer users a quick way to include the lib file!
Can you help, this is, provide a patch or a zip file with the
necessary data? No FreeType core developer is a Windows user.
Ideally, I would like to have a directory `builds/win64' which
contains a ready-to-run project file for a fitting compilation
environment so that your described actions are reduced to an absolute
minimum (additional steps should be mentioned in the corresponding
`index.html' file).
Werner_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
