<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 8/8/2013 2:00 PM, Doug Warren wrote:<br>
</div>
<blockquote
cite="mid:CAL4fHfzC7fN9jNWCsifdUyd7B5rdQ0ArhxoSr85JR32LyQ0H3g@mail.gmail.com"
type="cite">
<div dir="ltr">You'd have to define your terms a bit better. It's
straight C, if you have berkley sockets and anything even
vaguely resembling POSIX there should be no need for extra
support. I use the same build scripts for
iOS/Android/OSX/Linux. <br>
</div>
</blockquote>
<br>
The platform in question uses <a
href="http://savannah.nongnu.org/projects/lwip/">lwIP</a> (a
lightweight IP stack). Not real close to POSIX, but the basic
functions are there. It's not quite <u>extra</u> support, but it's
<u>different</u> support. I have it essentially working.<br>
<br>
<blockquote
cite="mid:CAL4fHfzC7fN9jNWCsifdUyd7B5rdQ0ArhxoSr85JR32LyQ0H3g@mail.gmail.com"
type="cite">
<div dir="ltr"><a moz-do-not-send="true"
href="https://github.com/lsalzman/enet/blob/master/host.c"
target="_blank">https://github.com/lsalzman/enet/blob/master/host.c</a>
shows a single check for a platform specific check regarding how
to get a uint32 timestamp. <br>
</div>
</blockquote>
<br>
Which is completely unnecessary when the platform abstraction layer
(win32.c and unix.c) provides the enet_time_get() function!?! It
doesn't make sense why that function wouldn't be used?<br>
<br>
Patrick<br>
<br>
</body>
</html>