From: | Yuriy Zhuravlev <stalkerg(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Setting rpath on llvmjit.so? |
Date: | 2018-04-18 15:54:59 |
Message-ID: | CANiD2e_bWD3R3fOCZExbkyrZuxk03yZn+XSD7z-vXh8h-hYBJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Current autoconf system not working on Windows at all, what we talk about?
On Wed, 18 Apr 2018, 23:57 Robert Haas, <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Apr 17, 2018 at 4:13 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I'd not advocate for this solely based on the age of autoconf. But the
> > separate windows buildsystem which makes it very hard to build
> > extensions separately is a good reason on its own. As is the fact that
> > recursive make as we're using it has significant issues. Both of those
> > would be avoided by using cmake or such.
>
> How much of the pain building extensions on Windows comes from our
> build system and how much of it comes from the fact that it's Windows?
> My guess would have been that the latter is by far the bigger issue,
> but maybe I'm wrong.
>
> There is really nothing keeping us from removing or reducing the use
> of recursive make without switching to cmake. And it's probably not
> even that much work.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-04-18 15:58:04 | Re: Setting rpath on llvmjit.so? |
Previous Message | Andres Freund | 2018-04-18 15:50:55 | Re: Query is over 2x slower with jit=on |