Re: Porting PG Extension from UNIX to Windows - Mailing list pgsql-hackers

From Pavlo Golub
Subject Re: Porting PG Extension from UNIX to Windows
Date
Msg-id 1968900664.20180507163713@cybertec.at
Whole thread Raw
In response to Porting PG Extension from UNIX to Windows  ("insaf.k" <insaf.k@zohocorp.com>)
List pgsql-hackers
Greetings, insaf.k.

You wrote 25.04.2018, 11:45:

> Hello,



> 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).





> Thanks,

> Insaf



-- 
Kind regards,
 Pavlo                          mailto:pavlo.golub@cybertec.at



pgsql-hackers by date:

Previous
From: Alexander Kuzmenkov
Date:
Subject: Re: Reopen logfile on SIGHUP
Next
From: Craig Ringer
Date:
Subject: Re: Porting PG Extension from UNIX to Windows