Re: compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Also, I would recommend uninstalling cygwin before you install
mingw, because if the mingw doesn't behave properly (gcc won't compile
files etc...), you could be sure that there definitely is a conflict
between the cygwin and mingw.

If you don't wish to uninstall cygwin, at least rename the folder
to someting else (cygwin.before.mingw) so that you don't accidentally
use cygwin's binaries.

Regards,
Gurjeet.

On 5/25/06, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> wrote:
> Hi Sibel,
>
> Here's the mail that I posted about 10 days ago about compiling
> and debugging postgres on windows. I have used msys/mingw toolkit and
> it is the recommended (by pg community) toolkit to compile postgres on
> windows.
>
> http://archives.postgresql.org/pgsql-hackers/2006-05/msg00396.php
>
> Hope it helps. Do let me know if you face any problems.
>
> Regards,
> Gurjeet.
>
> On 5/25/06, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
> > On Wed, May 24, 2006 at 01:46:19AM -0700, sibel karaasma wrote:
> > > Hi I'm a new postgresql user. I wrote ACO (ant colony optimazition) and
> > > want to replace it with GEQO in postres/src/backend/optimizer but I don't know how
> > > to compile and run the source code :(
> > >
> > > I installed postgresql-8.1.3 and cygwin but I can not use them to
> > > compile the source code. I want to compare GEQO and ACO optimizers performance using a small database
> >
> > mingw is now the approved build method for windows, and I think there's
> > instructions on how to build PostgreSQL with it somewhere, though I
> > can't seem to find them now. Though to be honest, you'd probably find it
> > easier doing development on any kind of a unix box, including OS X.
> > --
> > Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
> > Pervasive Software http://pervasive.com work: 512-231-6117
> > vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faq
> >
>