Opened 10 years ago
Last modified 10 years ago
#7881 new Bugs
ASIO - don't use Winsock when compiling with Cygwin
| Reported by: | Owned by: | chris_kohlhoff | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | asio |
| Version: | Boost 1.48.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
It's not necessarily a bug, but an improvement. I checked why i can compile with the integrated boost library in normal Cygwin distribution and i cannot do the same with some other boost variant. The main difference is the CYGWIN compile switch. In the Cygwin integration, the compile switch is removed and it will use linux sockets. The boost distributions force the usage of Winsock which clearly cause compile problems with Cygwin.
Please remove the compile switch and just let it use the linux sockets.
Attachments (1)
Change History (3)
comment:1 by , 10 years ago
| Component: | None → asio |
|---|---|
| Owner: | set to |
by , 10 years ago
| Attachment: | AsioDifferences.JPG added |
|---|
comment:2 by , 10 years ago
Note:
See TracTickets
for help on using tickets.
Please see attached file to get a glimpse of what i'm talking about. It's a small compare of one Io_Service. The things is, if you try to compile the ASIO example from within Eclipse (windows) with Cygwin as compiler, you'll not be able to get an executable. Looking at the code snippet, all i can think of is, usage of Winsock.
The basic thing is ... there is a difference between BOOST official releases and Cygwin release. As developer, i'll be limited to Cygwin boost which is not necessarily good. Why not synch them?
/Jimmy