Re: pg_config --pgxs on Win32 - Mailing list pgsql-hackers

From Dave Page
Subject Re: pg_config --pgxs on Win32
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E48507D9@ratbert.vale-housing.co.uk
Whole thread Raw
In response to pg_config --pgxs on Win32  (Thomas Hallgren <thhal@mailblocks.com>)
Responses Re: pg_config --pgxs on Win32
Re: pg_config --pgxs on Win32
Re: pg_config --pgxs on Win32
List pgsql-hackers


-----Original Message-----
From: Martijn van Oosterhout [mailto:kleptog@svana.org]
Sent: Thu 10/13/2005 8:08 PM
To: Tom Lane
Cc: Thomas Hallgren; Dave Page; pgsql-hackers@postgresql.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
canbe 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
thatpg_config may not work well in non-msys/cygwin environments. 

Regards, dave.


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: auto vacuum lock on 8.1beta1
Next
From: Robert Creager
Date:
Subject: Re: auto vacuum lock on 8.1beta1