|From:||Pavlo Golub <pavlo(dot)golub(at)cybertec(dot)at>|
|To:||"insaf(dot)k" <insaf(dot)k(at)zohocorp(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Porting PG Extension from UNIX to Windows|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
You wrote 25.04.2018, 11:45:
> I have developed a postgres extension in Linux. I want to compile it in MS Windows as well.
You should try MSYS2. It's far better than VS and MSYS right now.
I may try to build your extension if you want.
> The extension extensively make use of POSIX threads and mutexes.
> I've done some research regarding compiling in Windows. I am not
> sure in what way I should compile the extension. AFAIK, Visual
> Studio is not POSIX compliant and so I'll have to rewrite all those
> POSIX calls using Windows API. So it's better to compile the extension in Cygwin.
> I have some questions regarding compiling the extension in Cygwin.
> Do I have to build PG in Cygwin, if I want to compile the extension in Cygwin?
> Our deployment pattern is like this, build everything in one
> machine and copy the DLLs into the production machine. So, if I
> compile in Cygwin, will the generated DLLs work in other Windows
> machines? Would the target machine be required to install any
> dependencies related to Cygwin in order to use the DLLs?
> Also, one more question, not related to PG. Cygwin vs native
> Windows API calls, will there be much difference in the
> performance?(We are not using fork() calls, btw).
|Next Message||Craig Ringer||2018-05-07 13:52:24||Re: Porting PG Extension from UNIX to Windows|
|Previous Message||Alexander Kuzmenkov||2018-05-07 13:34:07||Re: Reopen logfile on SIGHUP|