Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #96639 > unrolled thread
| Started by | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| First post | 2015-09-15 10:54 -0500 |
| Last post | 2015-09-15 10:54 -0500 |
| 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 Zachary Ware <zachary.ware+pylist@gmail.com> - 2015-09-15 10:54 -0500
| From | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| Date | 2015-09-15 10:54 -0500 |
| Subject | Re: how to build windows extensions for python 3.5 |
| Message-ID | <mailman.599.1442332481.8327.python-list@python.org> |
On Tue, Sep 15, 2015 at 8:32 AM, Robin Becker <robin@reportlab.com> wrote: > 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? I'm a bit surprised that you can successfully use the same .libs for 2.7 and 3.3/3.4. But since that seems to work, I'd say go ahead and try it with 3.5, and if the build succeeds test the crap out of it :) -- Zach
Back to top | Article view | comp.lang.python
csiph-web