I know nothing at all about VxWorks so please excuse my ignorance. Does VxWorks have a POSIX programming interface or is it based on Win32? The socket_select_interrupter class is only intended for Win32. POSIX implementations are supposed to use pipe_select_interrupter instead.
Cheers, Chris
VxWorks is POSIX based. I had forced it to use socket_select_interrupter because the pipe_select_interrupter wasn't compiling due to (what I thought was) a lack of a pipe implementation on VxWorks. I have since got this configured correctly, so pipe_select_interrupter seems to work ok. socket_select_interrupter also works with the bzero() call I had in my original post. -- /************************************** * Scott Finley * Research Software Engineer * TomoTherapy Inc. * Email: sfinley@tomotherapy.com * Phone: 608.824.3381 ***/
Scott Finley writes:
VxWorks is POSIX based. I had forced it to use socket_select_interrupter because the pipe_select_interrupter wasn't compiling due to (what I thought was) a lack of a pipe implementation on VxWorks. I have since got this configured correctly, so pipe_select_interrupter seems to work ok. socket_select_interrupter also works with the bzero() call I had in my original post.
Excellent. Do let me know if any other changes are required for VxWorks and I'll check them into CVS. Thanks! Cheers, Chris
All, The formal 0.3.7 release of asio doesn't work on cygwin against 1.34.0 It compiles.... But 'make check' fails most things. Any ideas where to start? Andy
Andy Stevenson writes:
The formal 0.3.7 release of asio doesn't work on cygwin against 1.34.0 It compiles.... But 'make check' fails most things. Any ideas where to start?
As I mentioned in another reply, this is due to a change in the unit test framework in 1.34 such that it now treats having no test cases as a failure. It has already been addressed in the asio version in CVS. Cheers, Chris
participants (3)
-
Andy Stevenson -
Christopher Kohlhoff -
Scott Finley