Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #96634 > unrolled thread
| Started by | Robin Becker <robin@reportlab.com> |
|---|---|
| First post | 2015-09-15 14:32 +0100 |
| Last post | 2015-09-15 14:32 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: how to build windows extensions for python 3.5 Robin Becker <robin@reportlab.com> - 2015-09-15 14:32 +0100
| From | Robin Becker <robin@reportlab.com> |
|---|---|
| Date | 2015-09-15 14:32 +0100 |
| Subject | Re: how to build windows extensions for python 3.5 |
| Message-ID | <mailman.595.1442323948.8327.python-list@python.org> |
On 15/09/2015 12:38, Robin Becker wrote: > On 14/09/2015 17:26, Mark Lawrence wrote: >> On 14/09/2015 16:52, Robin Becker wrote: > ....... >> >> http://stevedower.id.au/blog/building-for-python-3-5-part-two/ >> >> The most important thing is to have something to do while the Visual >> Studio installation takes up 8G of your disk space and several hours of elapsed >> time. At least the installation went smoothly. >> > > thanks Mark's reference seems more directed at designers of the compilation steps for the extension. From Zachary's comment it seems I should be able to build with distutils without too much trouble. However, I try to link bits of various libraries statically into the reportlab extensions eg freetype.lib. Does anyone know if I will need separate versions of those for VS2015? Currently I build with distutils for Python 27, 33 & 34. Currently the .libs seem OK with both 2.7 & >=3.3 builds, but I notice from the reference that all the code for VS2015 needs to be built with specific options set, so will I need separate versions of the relocatable libs? -- Robin Becker
Back to top | Article view | comp.lang.python
csiph-web