On 02Sep2015 0803, Paul Moore wrote:
On 2 September 2015 at 14:07, Steve Dower wrote:
You can also build existing object or static libraries into their own DLL
with the old compiler and dynamically link to them. It's not perfect, but
it's no worse than trying to link them in directly.
Interes
On 2 September 2015 at 14:07, Steve Dower wrote:
> You can also build existing object or static libraries into their own DLL
> with the old compiler and dynamically link to them. It's not perfect, but
> it's no worse than trying to link them in directly.
Interesting approach. "gcc -shared -o xpm.
teve Dower" ; "Python Dev"
Subject: Re: [Python-Dev] Building Extensions for Python 3.5 on Windows
On 2 September 2015 at 13:01, Carl Kleffner wrote:
> that is https://bugs.python.org/msg248716 see also
> http://rt.openssl.org/Ticket/Display.html?id=3390&user=guest&pas
There are more semantic surprises as well. Some Math functions like powf,
acosf and so on are available only with the help of the VS 2015 math.h
include file (32 bit case). With exporting symbols names from the universal
dll's and creating import libraries you are not done yet.
Carl
2015-09-02 14
Hi,
that is https://bugs.python.org/msg248716 see also
http://rt.openssl.org/Ticket/Display.html?id=3390&user=guest&pass=guest
Steve: is there more of that in the new universal runtimes?
Carl
2015-09-02 12:16 GMT+02:00 Paul Moore :
> On 1 September 2015 at 17:15, Steve Dower wrote:
> > On 01S
On 2 September 2015 at 13:01, Carl Kleffner wrote:
> that is https://bugs.python.org/msg248716 see also
> http://rt.openssl.org/Ticket/Display.html?id=3390&user=guest&pass=guest
Interesting. But it does confirm that object files have to be rebuilt,
and there's no way to use existing object files.
On 1 September 2015 at 17:15, Steve Dower wrote:
> On 01Sep2015 0747, Oscar Benjamin wrote:
>>
>> Thanks for the detailed writeup Steve. Do you know how these changes
>> to the python.org Windows binaries would impact on people building
>> extension modules with MinGW?
>
>
> Currently, no version
On 01Sep2015 0747, Oscar Benjamin wrote:
Thanks for the detailed writeup Steve. Do you know how these changes
to the python.org Windows binaries would impact on people building
extension modules with MinGW?
Currently, no version of MinGW AFAIK will link against the UCRT, so
they'll suffer from
On 26 August 2015 at 17:14, Steve Dower wrote:
>> On 8/25/2015 2:17 PM, Steve Dower wrote:
>>>
>>> I've written up a long technical blog post about the compiler and CRT
>>> changes in Python 3.5, which will be of interest to those who build and
>>> distribute native extensions for Windows.
>>>
>>>
On 25Aug2015 2153, Terry Reedy wrote:
On 8/25/2015 2:17 PM, Steve Dower wrote:
I've written up a long technical blog post about the compiler and CRT
changes in Python 3.5, which will be of interest to those who build and
distribute native extensions for Windows.
http://stevedower.id.au/blog/bui
On 8/25/2015 2:17 PM, Steve Dower wrote:
I've written up a long technical blog post about the compiler and CRT
changes in Python 3.5, which will be of interest to those who build and
distribute native extensions for Windows.
http://stevedower.id.au/blog/building-for-python-3-5/
Hopefully it put
I've written up a long technical blog post about the compiler and CRT
changes in Python 3.5, which will be of interest to those who build and
distribute native extensions for Windows.
http://stevedower.id.au/blog/building-for-python-3-5/
Hopefully it puts some of the changes we've made into a
12 matches
Mail list logo