Moritz Angermann writes:
> Hi Arnaud,
>
...
I second everything that Moritz said. Having spent countless hours
fighting other projects' "non-traditional" build systems in the past, my
heart fills with dread whenever I see a project trying to be "clever"
with autoconf. Inevitably such
Expanding on Moritz a bit:
configure creates a build plan, hadrian runs it.
Newcomers to autoconf-based ecosystems often add a rule to run configure to
their Makefiles, as a "shortcut". At some time thereafter, they discover
that there's a problem when configure alters the build plan make is
I have to admit I sympathize with Moritz's view. Since `-c` only
"subsumes" the case where we call 'configure' with no extra env var or
argument, and in the absence of a generic way to pass options to
'configure' when using -c, I'd quite like to keep -c as a "cherry on
top", for users who just
Hi Arnaud,
Great to hear you've been using Hadrian for a while and like it!
As others have already pointed, -c used to be default. I personally was always
inclined to run boot and configure by default, because to me they seem like an
unnecessary complication on the way to the first GHC build
Hi Arnaud,
> On Mar 15, 2019, at 8:32 PM, Spiwack, Arnaud wrote:
>
> On Thu, Mar 14, 2019 at 7:20 PM Herbert Valerio Riedel
> wrote:
> I don't have the ticket number at my fingertips but it should be fairly easy
> to find.
>
> I'm afraid it doesn't appear to be. Could you share your
On Thu, Mar 14, 2019 at 7:20 PM Herbert Valerio Riedel
wrote:
> I don't have the ticket number at my fingertips but it should be fairly
> easy to find.
>
I'm afraid it doesn't appear to be. Could you share your arguments in this
thread?
On Fri, Mar 15, 2019 at 3:10 AM Moritz Angermann
wrote:
