← Back to team overview

drizzle-discuss team mailing list archive

Re: Drizzle on MS windows

 

On 07/14/2010 12:21 PM, Jobin Augustine wrote:
> Thank you Monty, Stewart and Toru,
> 
> regarding Stewart's comment:
>> I'd recommend 1 over 2. Cygwin is problematic in a number of ways.
> Ultimately I too want to achieve that..a perfect MinGW port.
> Cygwin port cannot be really considered as a windows port.
> Monty, you are correct. it appears to be bit of tough job for starting.
> 
> But Cygwin offers a complete set of Linux system calls in a dll
> (cygwin1.dll)
> I am unable to say "No" to such a good offer.
> and as a bonus, complete GNU tool chains. got tempted ;)
> 
> status update:
> First step was to build libdrizzle and it was a grant success.
> after end of the build every libs got compiled and additionally got few
> exes in example directory.

> Next step was to fire a query from windows to Drizzle server running on
> Linux:
> 
> See below.
> 
>  
> 
> C:\TEMP\libdrizzle-0.8\examples>simple.exe -d test -h 10.97.93.243 -q
> 'select * from t1'
> 
> jobin:1
> 
> 
> (using default port)
> 
> so it appears that it worked well... am i right?

Excellent! Looking good.

> 
> 
> 
> 
> On Wed, Jul 14, 2010 at 6:40 PM, Monty Taylor <mordred@xxxxxxxxxxxx
> <mailto:mordred@xxxxxxxxxxxx>> wrote:
> 
>     On 07/14/2010 01:11 AM, Stewart Smith wrote:
>     > On Tue, 13 Jul 2010 21:15:09 +0530, Jobin Augustine
>     <jobinau@xxxxxxxxx <mailto:jobinau@xxxxxxxxx>> wrote:
>     >> Hi All,
>     >> As a hobby project started working on porting Drizzle to windows.
>     >> I don't know anybody already started in this direction.
>     >>
>     >> have few options before me to start.
>     >>
>     >> 1. Use MinGW (http://www.mingw.org/)
>     >>
>     >> 2. Use Cygwin DLL and compile in windows
>     >> (i think, postgres initially followed this path)
>     >>
>     >> 3. Cross compile to windows executable from Linux. (static build)
>     >>
>     >> Just started with option 2. but don't know whether i am in right
>     direction.
>     >> if anybody has any previous experience in any of the above, please
>     >> guide me.
>     >
>     > I'd recommend 1 over 2. Cygwin is problematic in a number of ways.
>     >
> 
>     Depends on how large of a task you want...
> 
>     the MinGW port will be a very large undertaking, because you'll need to
>     fix networking code in libdrizzle, and then you'll need to actually port
>     drizzle to Windows. (1 and 3 are actually essentially the same amount of
>     work - there are like, 3 things you'll need to fix in the build scripts
>     to get 3 to work)
> 
>     Monty
> 
> 
> 




References