On Tue, Sep 04, 2018 at 04:31:27PM +0200, Andrea Bolognani wrote:
> On Tue, 2018-09-04 at 16:11 +0200, Erik Skultety wrote:
> > On Tue, Sep 04, 2018 at 01:01:34PM +0200, Andrea Bolognani wrote:
> > > Up until now, we've been considering MinGW builds as
> > > part of the respective project, at
On Tue, 2018-09-04 at 16:11 +0200, Erik Skultety wrote:
> On Tue, Sep 04, 2018 at 01:01:34PM +0200, Andrea Bolognani wrote:
> > Up until now, we've been considering MinGW builds as
> > part of the respective project, at least when it
> > comes to grouping them. This, however, does not quite
> >
On Tue, Sep 04, 2018 at 01:01:34PM +0200, Andrea Bolognani wrote:
> Up until now, we've been considering MinGW builds as
> part of the respective project, at least when it
> comes to grouping them. This, however, does not quite
> work for a number of reasons:
>
> * MinGW builds have their own
Up until now, we've been considering MinGW builds as
part of the respective project, at least when it
comes to grouping them. This, however, does not quite
work for a number of reasons:
* MinGW builds have their own workspace, separate
from the native one. It goes further than that:
