Am 04.04.2018 um 15:06 schrieb Jim Jagielski:
>> On Apr 4, 2018, at 9:01 AM, Jim Jagielski wrote:
>>
>>
>> I will start another thread on the gbuild topic...
>>
> First and foremost, I am incredibly impressed with the work
> being done on the gbuild migration. I really am.
>
>
Thank you, I appreciate it.
The list of gbuild modules is in main/Module_ooo.mk. The rest are using
dmake. The next one I expect to port is main/jurt, and that will be a
substantial patch.
Will our release process keep testing trunk until it's ready, then make a
branch of it to use for the
> On Apr 4, 2018, at 9:01 AM, Jim Jagielski wrote:
>
>
> I will start another thread on the gbuild topic...
>
First and foremost, I am incredibly impressed with the work
being done on the gbuild migration. I really am.
However, and there's always a "however", there must
Sometimes just a "heads-up" before the (sizable) commits might be
nice, esp on commits that will likely break builds.
At some point, however, we need to draw a line in the sand and
say "we will hold things steady for awhile" or else we'll never get
to a point where we can reasonably build and
ache.org> wrote:
>>>
>>> On Wed, Mar 28, 2018 at 12:57 AM, Larry Gusaas <larry.gus...@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On 2018-03-27, 4:32 PM Dave Fisher wrote concerning "Re: Building module
>&
ns and try to
> build on your Mac?
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Mar 27, 2018, at 7:44 PM, Damjan Jovanovic <dam...@apache.org> wrote:
> >
> > On Wed, Mar 28, 2018 at 12:57 AM, Larry Gusaas <larry.gus...@gmail.com>
> > wrote:
&
on your Mac?
Regards,
Dave
Sent from my iPhone
> On Mar 27, 2018, at 7:44 PM, Damjan Jovanovic <dam...@apache.org> wrote:
>
> On Wed, Mar 28, 2018 at 12:57 AM, Larry Gusaas <larry.gus...@gmail.com>
> wrote:
>
>>
>>
>> On 2018-03-27, 4:32 PM Dave
On Wed, Mar 28, 2018 at 12:57 AM, Larry Gusaas <larry.gus...@gmail.com>
wrote:
>
>
> On 2018-03-27, 4:32 PM Dave Fisher wrote concerning "Re: Building module
> store error on macOS":
>
> For development purposes Apple does not allow virtualization and
>>
On 2018-03-27, 4:32 PM Dave Fisher wrote concerning "Re: Building module store error
on macOS":
For development purposes Apple does not allow virtualization and development
has to proceed on physical Apple boxes.
If we could have macOS on a VM not on Apple hardware then we
. Before you FUD me I’ve been a Mac guy
since the MacSE.
Regards,
Dave
> On Mar 27, 2018, at 12:01 PM, Larry Gusaas <larry.gus...@gmail.com> wrote:
>
>
>
> On 2018-03-27, 9:13 AM Damjan Jovanovic wrote concerning "Re: Building module
> store error
On 2018-03-27, 9:13 AM Damjan Jovanovic wrote concerning "Re: Building module store error on
macOS":
Apple products are disproportionately expensive
Bulllshit. No, they are not. Quit spreading FUD.
--
_
Larry I. Gusaas
Moose Jaw, Saskatche
Apologies on the name. Damjan gets autocorrected by Apple. It’s a problem.
Regards,
Dave
Sent from my iPhone
> On Mar 27, 2018, at 10:20 AM, Damjan Jovanovic wrote:
>
> Yes, a Mac buildbot would be very welcome. Please add one.
>
> I am primarily developing on Windows now,
Yes, a Mac buildbot would be very welcome. Please add one.
I am primarily developing on Windows now, as developing on the most
problematic platform first makes it easy to port to others later.
The general instability over the last few weeks has also been due to the
progress made, which has been
Damian,
Jim is reasonably asking for some heads up so that he can know what to expect
before he does Mac and Linux builds.
Matthias would certainly like the same as well for Windows although buildbots
do help.
Speaking of Mac Buildbots Jim did offer to make one available in his location
and
Hi
Between the gbuild migration, Win64 migration and MSVS 2015 migration, all
of which are project-wide, modules will break, a lot.
If I had access to a Mac, I would definitely be testing these changes.
Since I don't, Infra keep refusing to get us a Mac buildbot, Apple is my
least favourite
15 matches
Mail list logo