Re: pg_config --pgxs on Win32
От | Thomas Hallgren |
---|---|
Тема | Re: pg_config --pgxs on Win32 |
Дата | |
Msg-id | thhal-0V1AqBJsj8rQq26SsUggm8IqYPlmBMq@mailblocks.com обсуждение исходный текст |
Ответ на | Re: pg_config --pgxs on Win32 ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgsql-hackers |
Dave Page wrote: > > -----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 docsthat pg_config may not work well in non-msys/cygwin environments. > > Regards, dave. > Perhaps pg_config should have a --pgxscanonical option? If someone then really wants the backslashes, he could use that. - thomas
В списке pgsql-hackers по дате отправления: