[reportlab-users] reportlab fail installing on Windows 7 x64 with Python 2.6 x64 (easy_install)

[Robin Becker]

Sorin Sbarnea wrote:

>> We do NOT plan to adopt setuptools, but we hope to make it so you can

>> 'easy_install reportlab'.

> Thanks for clarifying this - not lets go back to the build issues of

> reportlab because I think anyone would benefit from a reportlab that

> is easy to build.

> 

> Latest release of code does give this errors when you try setup.py

> build (and you have right settings in setup.cfg):

> C:\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.c(1885)

> : warning C4244: '=' : conversion from '__int64' to 'long', possible

> loss of data

> c:\Program Files (x86)\Microsoft Visual Studio

> 9.0\VC\BIN\amd64\link.exe /DLL /nologo /INCREMENTAL:NO

> "/LIBPATH:C:\Program Files (x86)\GnuWin32\lib"

> /LIBPATH:C:\Python26\libs /LIBPATH:C:\Python26\PCbuild\amd64

> /LIBPATH:build\temp.win-amd64-2.6 freetype.lib _renderPM_libart.lib

> _renderPM_gt1.lib /EXPORT:init_renderPM

> build\temp.win-amd64-2.6\Release\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.obj

> /OUT:build\lib.win-amd64-2.6\_renderPM.pyd

> /IMPLIB:build\temp.win-amd64-2.6\Release\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.lib

> /MANIFESTFILE:build\temp.win-amd64-2.6\Release\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.pyd.manifest

>    Creating library

> build\temp.win-amd64-2.6\Release\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.lib

> and object build\temp.win-amd64-2.6\Release\dev\pj\kit\py\ReportLab_2_3\src\rl_addons\renderPM\_renderPM.exp

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_New_Memory_Face referenced in function _get_ft_face

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_Init_FreeType referenced in function _get_ft_face

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_Done_Face referenced in function py_FT_font_dealloc

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_Outline_Decompose referenced in function

> _ft_get_glyph_outline

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_Load_Glyph referenced in function _ft_get_glyph_outline

> _renderPM.obj : error LNK2019: unresolved external symbol

> __imp_FT_Get_Char_Index referenced in function _ft_get_glyph_outline

> build\lib.win-amd64-2.6\_renderPM.pyd : fatal error LNK1120: 6

> unresolved externals

> error: command '"c:\Program Files (x86)\Microsoft Visual Studio

> 9.0\VC\BIN\amd64\link.exe"' failed with exit status 1120


this error just looks as though the build is attempting to include freetype 
support, but the load is failing to see the libraries.


> 

> I checked and the symbols are inside the lib and I found an

> wordaround: you go to .\src\rl_addons\renderPM\ where you run

> "setup.py build" => in this case it does not complain at all.

> 


the setup.py in the renderPM folder is the original (prior to the attempted 
merge of the builds). It may do slightly different things to locate things like 
FT lib etc etc; in particular  don't think it looks at all at cfg files (of 
course distutils may do that anyhow).

I have never built a 64bit version of anything under win32 so won't know 
anything about how that should be done; also I don't think I've yet had to use 
VS 9, which python are you building for?



> Now you copy the library _renderPM.pyd from

> .\src\rl_addons\renderPM\build\lib.win-amd64-2.6 to

> .\build\lib.win-amd64-2.6 and you can run the "setup.py build" again

> and "setup.py install".

> 

> After this reportlab is installed and running very well (at least the tests).

> 

> Now my question would be: why does this happen and how can we repair

> this build issue?

> 

> --

> /sorin

> _______________________________________________

> reportlab-users mailing list

> reportlab-users at lists2.reportlab.com

> http://two.pairlist.net/mailman/listinfo/reportlab-users

> 



-- 
Robin Becker