On Wed, Jun 15, 2011 at 9:19 AM, Ed Day wrote:
> This works for Windows? I did not know that. Would I need to run it
> through Cygwin or something similar?
Cygwin or mingw, if you're using them. I wasn't clear at the time
which build system you were using.
--
Nick
***
Thanks for the git info. I have embedded responses to the other items below.
Regards,
Ed
On Tue, Jun 14, 2011 at 3:16 PM, Nick Mathewson wrote:
> On Tue, Jun 14, 2011 at 10:36 AM, Ed Day wrote:
> [...]
>> I did a clone from the main repository and tried to build it on
>> Windows and found t
On Tue, Jun 14, 2011 at 10:36 AM, Ed Day wrote:
[...]
> Sounds interesting. I am a newbie to git, so I'm wondering how I
> would access this branch?
So here's what I'd suggest. It's no substitute for reading a proper
git tutorial, so please don't use this as a long-lived reference card
or anyt
On Mon, Jun 13, 2011 at 5:25 PM, Nick Mathewson wrote:
> On Sat, Jun 11, 2011 at 6:19 AM, Ed Day wrote:
>> I see in the event-test.c sample program the disclaimer that it does
>> not work on non-UNIX platforms (which to me means Windows, maybe
>> others?).
>
> Just Windows as far as I know.
>
>>
On Sat, Jun 11, 2011 at 6:19 AM, Ed Day wrote:
> I see in the event-test.c sample program the disclaimer that it does
> not work on non-UNIX platforms (which to me means Windows, maybe
> others?).
Just Windows as far as I know.
> It looks like this is an implementation of a named pipe.
> This h
I see in the event-test.c sample program the disclaimer that it does
not work on non-UNIX platforms (which to me means Windows, maybe
others?). It looks like this is an implementation of a named pipe.
This has been a problem I have been trying to solve on Windows for
awhile now, how to asynchronou
