[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Steve Dower added the comment: This was fixed with #22919. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Steve Dower added the comment: AFAICT, cabinet.lib has been around since at least VS 2008, so 3.4 will be fine. But since it builds currently there's no point changing it. I'll just let my changes handle it for 3.5 and leave the older versions alone. -- ___

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Zachary Ware added the comment: Definitely not 2.7, since it's still on VS2008 and would require so many changes for this to matter that it's just not an issue; I'm not sure on 3.4. Is cabinet.lib available (and have everything we need) for MSVC10 and SDK 7.1 (which are the important targets

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Steve Dower added the comment: I've inadvertently picked this up with my changes for #22919, so it'll get into 3.5 that way. Do we need to apply this to 3.4 as well? What about 2.7? -- assignee: -> steve.dower nosy: +steve.dower ___ Python tracker

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Changes by Ned Deily : -- components: +Build nosy: +loewis, zach.ware type: compile error -> ___ Python tracker ___ ___ Python-bugs-l

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

New submission from Michael Stahl: building with MSVC2012 and the Windows SDK 8.0 fails according to this page, the fci.lib is no longer available and cabinet.lib should be used instead: http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/3b85f36e-dffe-4589-adc3-13673b349812/ "For W