From: email@example.com [mailto:firstname.lastname@example.org] On
> On Fri, Mar 9, 2012 at 9:50 AM, <email@example.com> wrote:
> > At http://controls.diamond.ac.uk/downloads/python/cothread in the git
> > repository listed there I have pushed updates for
> > both the current version of cothread (to shortly be released as
> > version 2.6) and a Python 3 branch.
> Thanks, 2.6 built and installed on linux x86 and x86_64, but only
> tested that caget() worked. Building with Mingw failed for me on
> Win32. Any build hints for Win32?
Can you give details of your build errors on win32, please?
Actually Windows is a can of worms and doesn't work properly with cothread, and is likely to only work properly if somebody else lends me a hand, as I don't really have the time to give it the effort it needs. I have at least the following problems with this platform:
1. select() in Windows only works on sockets. I had previously fudged my way around this with some WaitForMultipleObjects hacks, but I've not yet figured out how to emulate select() on Windows in a way which works for stdio, pipes *and* sockets, and the latest cothread won't work without support for pipes (though I'm willing to fake this as appropriate). Alas, I've not take the time to figure this out, and it does not seem straightforward.
2. Compiling on Windows is nasty. VC++ doesn't support C99, and its assembler syntax is somewhat different, but it would seem that mingw is very much a moving target. Last time I tried a ming32 build I ended up hacking my Python.h files to get things working and then stopped in disgust.
It is probably better to bite the bullet and create VC compatible versions of the files in the context/ directory, but I am so reluctant...
3. From spring this year it will have been exactly a decade since I was last employed as an engineer to work on Windows. I rejoice. Sorry, but this is my attitude to the platform. I don't want to say much more, as I'm liable to rant at this point!
> And, sorry for the questions, but I've always been a little confused
> by cothread. Perhaps you could clarify some points for me?
I'll answer this in another e-mail, would like to separate the Windows issue from the rest!
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- RE: Invitation to test cothread.catools release candidate Hill, Jeffrey O
- Invitation to test cothread.catools release candidate michael.abbott
- Re: Invitation to test cothread.catools release candidate Matt Newville
- Navigate by Date:
RE: Fwd: michael.abbott
RE: Invitation to test cothread.catools release candidate michael.abbott
- Navigate by Thread:
Re: Invitation to test cothread.catools release candidate Matt Newville
RE: Invitation to test cothread.catools release candidate Hill, Jeffrey O