From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: About CMake v2 |
Date: | 2015-09-01 22:10:01 |
Message-ID: | CAM-w4HMAS+NVp_t20Ma-JtDod7gHvHJKCHE5Tf+Kixv_inEK7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 1, 2015 at 2:41 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Maybe we should merge all of the makefiles for subdirectories of
> src/backend into a single makefile. The major disadvantage would be
> that you couldn't rebuild a subdirectory any more by typing make -C
> src/backend/executor or whatever. And I do do that sometimes, so
> maybe it would be annoying, but presumably it would make the
> dependency issues a lot easier to deal with.
Actually I think it's possible to cater to that use case though I've
never tried.
What I think does become difficult in this scenario are directories
that are built more than once, eg, for client and server side builds.
I guess you could still do it but it would require doubling up every
rule and creating lots of extra targets representing the two builds
since you can't just call make with different variables.
It is tempting and I've been wanting to evalangize this approach ever
since read http://aegis.sourceforge.net/auug97.pdf but I've never
actually had practical experience with it and iirc it's always this
scenario of wanting to compile submodules multiple times that blocked
using it.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-09-01 22:11:45 | Re: Horizontal scalability/sharding |
Previous Message | Josh Berkus | 2015-09-01 22:09:09 | Re: Horizontal scalability/sharding |