From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | <merlin(dot)moncure(at)rcsonline(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: information Windows - PostgreSQL |
Date: | 2003-06-18 14:42:04 |
Message-ID: | 35171.199.90.235.43.1055961724.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Not sure if this is useful - I just found it on MSDN. It talks about porting
issues, including specifically signal handling techniques (it seems to
recommend using windows messaging instead of signals for some scenarios).. I
am not sure how easy it would be to abstract this away by providing a
signalling library that contained it all.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnucmg/html/UCMGch09.asp
cheers
andrew
Bruce wrote:
> Merlin Moncure wrote:
>> Bruce,
>>
>> I assume then that the MinGW environment is missing signal emulation
>> that is present in the Microsoft C runtime distribution? Microsoft's
>> is copyrighted, of course in winsig.c (it is actually quite small,
>> just a couple hundred lines of code). Are you proposing to rewrite
>> that part of the CRT? I checked the redistribution license and
>> winsig,etc.c are most certainly not suitable for incorporation into an
>> open source project.
>
> I actuallly don't even know the answer. I don't know what is possible
> with MinGW vs Visual C. I need help.
>
> I would have dug into it, but I got pretty far with MinGW, then had to
> stop to catch up on email, and still not caught up enough to return to
> MinGW.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-06-18 15:16:50 | Re: lots of configure failures on freebsd/alpha |
Previous Message | Alvaro Herrera | 2003-06-18 14:35:37 | Re: pg_get_triggerdef in pg_dump |