Thanks Alessandro and Even for your replies,
I try your suggestions but I still get the error. I opened an issue
https://github.com/qgis/QGIS/issues/37386
Kind regards,
Julien
> On Wed, Jun 24, 2020 at 2:57 PM Julien Cabieces
> wrote:
>>
>>
>> Hi alls,
>>
>> I was looking to create an empty
In addition to what Even mentioned, QGIS might also hit some performance
issues/bugs on the new platform. For example, the rule-based rendering with
expressions that contains LIKE will make QGIS project completely unusable
on iOS:
https://github.com/lutraconsulting/input/issues/433
This could be
Hi,
Yes, I also heard about the better energy efficiency of the arm
processor. That's probably the main reason why typical mobile devices
almost never run on Intel processors. What effect the change to arm will
have performance wise, esp. when libraries aren't yet optimized for that
Julien,
> I was looking to create an empty GPKG layer and try the solution Even
> provide, but it creates an invalid file.
>
> fields=QgsFields()
> fields.append(QgsField("note", QVariant.Double))
> QgsVectorFileWriter.create("/tmp/test.gpkg", fields,
> QgsWkbTypes.MultiLineString,
On mercredi 24 juin 2020 11:53:37 CEST Peter Petrik wrote:
> Hi,
>
> As building on iOS already works (
> https://github.com/lutraconsulting/input-sdk/tree/master/ios), I imagine it
> would be possible to run another architecture build for MacOS with a
> similar approach. It is in Apple's
Hi,
Well, Linux systems for ARM have existed for ages NOW.
Simply put, the energy consumption of ARM devices is far lower than intel’s
crap.
That’s why Apple is doing it, they have announced that intention years ago.
Microsoft has started shipping tables for ARM, too, btw.
Though, MS is not
Hi
> On 24 Jun 2020, at 11:52, Andreas Neumann wrote:
>
> Hi Peter,
>
> Thanks for this feedback.
>
> 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
On Wed, Jun 24, 2020 at 2:57 PM Julien Cabieces
wrote:
>
>
> Hi alls,
>
> I was looking to create an empty GPKG layer and try the solution Even
> provide, but
> it creates an invalid file.
>
> fields=QgsFields()
> fields.append(QgsField("note", QVariant.Double))
>
Hi alls,
I was looking to create an empty GPKG layer and try the solution Even provide,
but
it creates an invalid file.
fields=QgsFields()
fields.append(QgsField("note", QVariant.Double))
QgsVectorFileWriter.create("/tmp/test.gpkg", fields,
QgsWkbTypes.MultiLineString,
Surely the code ought to all build on arm64 (and earmv7, sparc, sparc64,
RISC-V, and many others). If not it needs fixing anyway.
(No disagreement with your points about CI and build servers.)
I suspect there will be a lot of aarch64 and RISC-V hardare in the open
source world over the next few
Hi Peter,
Thanks for this feedback.
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?
Andreas
Am 24.06.20 um 11:53 schrieb
Hi,
As building on iOS already works (
https://github.com/lutraconsulting/input-sdk/tree/master/ios), 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
Hi Andreas,
I'm also worried about this move.
But one way to forward the cost to Apple is now to stop buying macs.
Sorry to troll, but the vendor lockin' nightmare they are building is not
of the same nature as of the powerpc era.
I sold mine because they stopped to support it though it worked
Hi all, esp. Peter,
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.
Will it be a lot of work to adapt the build system to the
14 matches
Mail list logo
