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 platform, Apple products are disproportionately expensive, and I do so much for AOO already (being its biggest contributor), I think asking me to test Mac builds is unreasonable. If you want to change that, I could be bought a Mac or given remote access to one, Mac developers could pull their own weight, or Mac could be dropped as a supported platform. Now as for the store build regression, please post the output of "build --from store". Regards Damjan On Tue, Mar 27, 2018 at 3:29 PM, Jim Jagielski <j...@jagunet.com> wrote: > Looks like recent build changes have broken the macOS > build again... This time we die when trying to build > store. > > <rant> > IMO, it would be nice if when updating, people were > a little more circumspect on how/if this would affect > other builds. I realize that it is hard to anticipate > such things, but at least some sort of warning, or > "head's up" or some summary of what was changed and > why/how, instead of just a huge commit, might make > things easier for people who then need to dig into > the weeds and fix other platforms. > </rant> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
