Re: pg_config --pgxs on Win32

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Thomas Hallgren" <thhal(at)mailblocks(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_config --pgxs on Win32
Date: 2005-10-13 19:36:39
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E48507D9@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----Original Message-----
From: Martijn van Oosterhout [mailto:kleptog(at)svana(dot)org]
Sent: Thu 10/13/2005 8:08 PM
To: Tom Lane
Cc: Thomas Hallgren; Dave Page; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] pg_config --pgxs on Win32

> Besides, Windows has accepted the forward slash as directory seperator
> all the way since DOS 2.0 when directories were introduced. The only
> reason they sometimes don't work as expected is because it's also the
> option indicator :(.
>
> Presumably things break when commands read /path as an option rather
> than a path. Hopefully they're smart enough to realize c:/path does not
> actually contain an option but is just a path. Presumably that's
> fixable some other way?

When we first discussed this I posted a very simple example 'cd /' which does absolutely nothing unlike 'cd \' or 'cd \\' which work as expected, quite possibly for the reason you suggest. Although the / is accepted, I don't believe it can be called reliable as it obviously doesn't work in all situations.

Regardless, the msys/gmake case is definately the most important to support, but I do think we should note in the docs that pg_config may not work well in non-msys/cygwin environments.

Regards, dave.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2005-10-13 19:39:00 Re: pg_config --pgxs on Win32
Previous Message Kevin Grittner 2005-10-13 19:20:46 Re: auto vacuum lock on 8.1beta1