From: | Yuriy Zhuravlev <stalkerg(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Hartmut Holzgraefe <hartmut(dot)holzgraefe(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Is a modern build system acceptable for older platforms |
Date: | 2018-05-02 00:20:51 |
Message-ID: | CANiD2e-0ef6v_3xRAOPXcKZ+-oKkPv+pyRVngGRnzuGh0iipXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Indeed. It's possibly today to use CMake without a huge amount of
difficulty to build extensions out of tree against MSVC-built
postgres.
How? All builds what I saw was with tons of hacks.
On windows, Postgres can build against Mingw, many versions of MSVC and etc
Also, you can build Postgres without some features or with extra and no
good way to put this knowledge to CMake build system.
At least we should replace Windows build system by cmake and if your worry
about consistency of source files (it's very small problem actually) you
can use current
Perl script to generate files list for CMake, it will be same as your 1.5
build system.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-05-02 00:32:39 | Re: pgsql: Clean up warnings from -Wimplicit-fallthrough. |
Previous Message | Andrew Gierth | 2018-05-02 00:20:05 | Re: lazy detoasting |