[vtkusers] compilation fails

[Dominik Szczerba]

I attempted one more try: keep PYTHON_DEBUG_LIBRARY empty and
PYTHON_LIBRARY=python2.7_d.lib.
python27.lib is never referenced, yet declared missing during compilation.

I looked at FindPythonLibs.cmake and vtkWrapPython.cmake, I do not see
anything wrong there.

But there is clearly something broken here. Should I file a bug?

Dominik

On Tue, Jun 21, 2011 at 9:43 PM, Dominik Szczerba <dominik at itis.ethz.ch> wrote:
> I checked one more thing in VC's target linker input:
> For debug configuration there is python27_d.lib, for release python27.lib.
> So why is debug build requiring python27.lib in the wrappings??
>
> Dominik
>
> On Tue, Jun 21, 2011 at 9:39 PM, Dominik Szczerba <dominik at itis.ethz.ch> wrote:
>> I am compiling vtk-5.6.1 on MSVC 2010 64 bit in debug mode with python
>> (I can not use RelWithDebInfo, it fails elsewhere).
>> I set PYTHON_LIBRARY to python2.7.lib and PYTHON_DEBUG_LIBRARY to
>> python2.7_d.lib (both in the same dir, as comes from python build
>> solution) but the compilation fails very early with the first
>> messages:
>>
>> 2>InitializeBuildStatus:
>> 2>  Touching "vtkWrapPython.dir\Debug\vtkWrapPython.unsuccessfulbuild".
>> 2>CustomBuild:
>> 2>  All outputs are up-to-date.
>> 2>ClCompile:
>> 2>  All outputs are up-to-date.
>> 2>ManifestResourceCompile:
>> 2>  All outputs are up-to-date.
>> 2>LINK : fatal error LNK1104: cannot open file 'python27.lib'
>> 2>
>> 2>Build FAILED.
>> 2>
>>
>> Inspecting the vtkWrapPython target's linker input in VC I only see
>> python2.7_d.lib in there. It makes sense then to fail building, but I
>> was expecting both lib versions will be used for both Release/Debug
>> build.
>> Did I miss anything?
>>
>> Dominik
>>
>