Re: std::optional::value

[Christian Lohmaier <lohmaier@xxxxxxxxxxxxxx>]

Hi*,

On Thu, Jan 13, 2022 at 9:24 AM Stephan Bergmann <sbergman@xxxxxxxxxx> wrote:
>
> […]  (And that is apparently what happened for
> <https://gerrit.libreoffice.org/c/core/+/128308> "do not force pixel
> reading in VclCanvasBitmap ctor", where
> <https://ci.libreoffice.org/job/gerrit_mac/110583/> successfully built
> that change---introducing uses of std::optional::value---on tb86 with
> Xcode 13.2.1, but later builds of unrelated changes started to fail,
> like <https://ci.libreoffice.org/job/gerrit_mac/110609/> on tb69 with
> Xcode 11.3.1.)

tb86 is an apple silicon m1 mac mini, so that's why it doesn't match
the baseline compared to the other mac machines that still are on
Mojave…

> One option would apparently be to limit LO to building
> with Xcode >= 12.5, but some hardware (like my early 2013 15" Retina
> MacBook Pro) is stuck with macOS 10.15 and thus with Xcode 12.4 (see
> <https://en.wikipedia.org/wiki/Xcode#Xcode_11.x_-_13.x_(since_SwiftUI_framework)>).
>   (For me personally that wouldn't be much of a problem, as I usually
> built against a trunk LLVM libc++ on that machine.  But it would
> presumably be an issue at least for some of the Jenkins machines?)

Jenkins builders are either the trashcan macpro or macmini from 2014 and 2018
So I think they all should be able to run Monterey

ciao
Christian