<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE-CH" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Well, Linux systems for ARM have existed for ages NOW.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Simply put, the energy consumption of ARM devices is far lower than intel’s crap.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">That’s why Apple is doing it, they have announced that intention years ago.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Microsoft has started shipping tables for ARM, too, btw.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Though, MS is not quite there, yet, and they probably never will be, not within the next few years at least.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">You can do cross-compile builds with CLANG/LLVM on a 250$ Chromebook using OSXcross.
<o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://github.com/tpoechtrager/osxcross"><span lang="FR-CH">https://github.com/tpoechtrager/osxcross</span></a><span lang="FR-CH" style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Chromebooks are the easiest commercially obtainable ARM-computers nowadays.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Switch to developer mode, install Crouton with ARM-Ubuntu in a chroot, and there you go.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Or install Chrubuntu if you don’t want to use the kernel of the underlying ChromeOS.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Using Chrubuntu, you might have trouble with drivers, though.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">That worked for me; mono (.NET) and Java work on ARM, too.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">PS: <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Why not simply ship a Linux-Docker-Image for ARM processors ?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">It is my understanding Linux Docker images work on OSX.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Certainly would work for server components.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">GUI might be a different chapter, but since OSX can do X11 ...
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Not sure how Wayland would play into that, though.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The most intelligent way would be dropping the proprietary Desktop-GUIs anyway.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Switching to a web-based editor.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Then you can drop everything but Linux, and just ship docker containers.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Users connect via browser.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Saves a lot of work.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US">Also a lot more secure.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR-CH" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">All you need to ship per platform then is an icon and a startup link/shell-script.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="DE">Von:</span></b><span lang="DE"> QGIS-Developer <qgis-developer-bounces@lists.osgeo.org>
<b>Im Auftrag von </b>Andreas Neumann<br>
<b>Gesendet:</b> Mittwoch, 24. </span><span lang="FR-CH">Juni 2020 11:11<br>
<b>An:</b> QGIS Developers List <qgis-developer@lists.osgeo.org><br>
<b>Betreff:</b> [QGIS-Developer] QGIS for Apple: Intel vs. arm<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="FR-CH"><o:p> </o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Hi all, esp. Peter,<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">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.<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">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 ...<o:p></o:p></span></p>
<p><span lang="FR-CH" style="font-size:10.0pt;font-family:"Verdana",sans-serif">Not so nice for us as a project - can we forward these costs to Apple for that move?<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Greetings,<br>
Andreas<o:p></o:p></span></p>
</div>
</body>
</html>