<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Peter,</p>
<p>Thanks for this feedback.</p>
<p>I remember when Apple switched from PowerPC to Intel that they
had kind of compatibility/abstraction layer that allowed old
software to work on the new intel platform. Are there similar
plans with the switch to arm?</p>
<p><font size="-1">Andreas</font><br>
</p>
<div class="moz-cite-prefix">Am 24.06.20 um 11:53 schrieb Peter
Petrik:<br>
</div>
<blockquote type="cite"
cite="mid:CA+T_MsL0+DaZbb1c-Dd9fn+Ua5u2Te3DT7OqCsBzenG5+fKFGA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">Hi,
<div><br>
</div>
<div>As building on iOS already works (<a
href="https://github.com/lutraconsulting/input-sdk/tree/master/ios"
moz-do-not-send="true">https://github.com/lutraconsulting/input-sdk/tree/master/ios</a>),
I imagine it would be possible to run another architecture
build for MacOS with a similar approach. It is in Apple's
interest to facilitate transition to developers. To evaluate
how hard it would be, that is more tricky at this point.
First of all, Qt has to support this new architecture, I
haven't found a statement from them yet if they plan it and
when. So even Qt supports it (hopefully from Qt5 releases
and not Qt6), we have to build all the deps with the new
architecture, which takes some time to create recipes. And
of course find a hardware where it all can be built
(probably another machine , yes). Not saying that it is very
frustrating to do development of such a new package if you
do not own such hardware yourself...</div>
<div><br>
</div>
<div>P. </div>
<div><br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jun 24, 2020 at 11:33
AM Régis Haubourg <<a
href="mailto:regis.haubourg@gmail.com"
moz-do-not-send="true">regis.haubourg@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hi Andreas, <br>
</div>
<div>I'm also worried about this move.</div>
<div><br>
</div>
<div>But one way to forward the cost to Apple is now to stop
buying macs. <br>
</div>
<div>Sorry to troll, but the vendor lockin' nightmare they
are building is not of the same nature as of the powerpc
era. <br>
</div>
<div>I sold mine because they stopped to support it though
it worked very well on the hardware side. And switching to
linux on Mac is made hard on purpose.. > never again
for me, even if they do really good stuff. <br>
</div>
<div>I found in LENOVO some durable hardware, easy to
repair, hardware that works nicely and avoid me to trash a
working computer. <br>
</div>
<div>Best</div>
<div>Régis<br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le mer. 24 juin 2020
à 11:11, Andreas Neumann <<a
href="mailto:a.neumann@carto.net" target="_blank"
moz-do-not-send="true">a.neumann@carto.net</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div
style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p>Hi all, esp. Peter,</p>
<p>So I wonder what the new announcement of Apple
switching everything from Intel to arm architecture
will mean for our project? According to Apple they
will switch all of their devices to arm over the next
2 years.</p>
<p>Will it be a lot of work to adapt the build system to
the new processor architecture? It will probably mean
that we will need an additional Mac build server for
arm architecture in our infrastructure and will have
to provide packages for both systems for many years to
come ...</p>
<p>Not so nice for us as a project - can we forward
these costs to Apple for that move?</p>
<p>Greetings,<br>
Andreas</p>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank" moz-do-not-send="true">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank" moz-do-not-send="true">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote>
</div>
</blockquote>
</body>
</html>