This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kristjan.jonsson
Recipients alexis, brian.curtin, eric.araujo, jackjansen, jaraco, kristjan.jonsson, loewis, mark.dickinson, mhammond, python-dev, sable, santoso.wijaya, sbt, tarek, tim.golden
Date 2012-05-17.11:35:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337254530.03.0.393295774531.issue13210@psf.upfronthosting.co.za>
In-reply-to
Content
This is fun.
the reason why linking is failing for some projects in x64 mode is:
the SolutionDir (or maybe current dir) is implicitly part of the library search path.  Therefore, when looking for python33_d.lib, it will find the one in PCbuild, and look into that, and ignore the one in PCbuidl\amd64.

Some projects have "references" to the pythoncore project.  This is a .NET feature and not really useful for normal projects, but it does put an explicit link referrence to the correct .lib file into the linker's input arguments.  This is why _testcapi works, and not _testbuffer (try diffing the two .vcxproj files).

All of this stems from my patch removing explicit link references to the correct .lib file.  Perhaps I can reintroduce that, but in a .props file.
History
Date User Action Args
2012-05-17 11:35:30kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, mhammond, jackjansen, mark.dickinson, jaraco, sable, tim.golden, tarek, eric.araujo, brian.curtin, santoso.wijaya, alexis, python-dev, sbt
2012-05-17 11:35:30kristjan.jonssonsetmessageid: <1337254530.03.0.393295774531.issue13210@psf.upfronthosting.co.za>
2012-05-17 11:35:29kristjan.jonssonlinkissue13210 messages
2012-05-17 11:35:29kristjan.jonssoncreate