On 18/02/12 01:26 PM, Christoph Gohlke wrote:
On 2/16/2012 8:12 PM, Lenard Lindstrom wrote:Hi everyone, Some more Windows installers and prebuilt libraries: md5sums ca388c44dbb51f46dff53b93558f1abc *prebuilt-pygame1.9.2-msvcr90-win32.zip e5cfda898096e66ea5e1bf75c5f7424b *pygame-1.9.2a0.win32-py2.7.msi 0578a2514b73e0bf7e22d6d0f2d56b39 *pygame-1.9.2a0.win32-py3.2.msi Please help test the new pygame.freetype module. Just set the PYGAME_FREETYPE environment to some value, then use Pygame as normal. If you don't notice anything different then freetype is working fine. Thanks, Lenard LindstromHi Lenard,I didn't try those builds. But, FWIW, my own win32 and win-amd64 msvc9 builds pass all tests with and without PYGAME_FREETYPE. The examples work well too.Christoph
Hi Christoph,The prebuilt binaries are not important in testing freetype. When the PYGAME_FREETYPE environment variable is defined, the SDL_ttf based pygame.font extension module is replaced with the pygame.freetype based pygame.ftfont Python module. That freetype keeps passing its unit tests is good news. But I am also interested in seeing it used in actual games.
By the way, how did you deal with smpeg? I finally gave up with MinGW and built smpeg with Visual Studio 9.0. I mean to provide instructions on building the libraries with msys_build_deps,py, where smpeg is assumed to be already compiled. But I am still working out a systematic approach: Build SDL first, create a LIB for SDL, build smpeg with the SDL library added to the library search path, then build everything else.
Lenard Lindstrom