The PIC issue will not be resolved for dp 1 as it doesn’t impact our toolchains
on travis or vulcan and as Mark pointed out there’s a workaround.
> On 14 May 2019, at 10:25 am, Brian Milby via use-livecode
> wrote:
>
> Yes, building against develop.
> Using gcc 7.4.0
>
> This was a laptop I
Yes, building against develop.
Using gcc 7.4.0
This was a laptop I setup about 8 months ago with Ubuntu 18.04. I loaded all
of the build stuff then but ran into the PIC issue and stopped. I had VMs with
16.04 that I could still use to build on Linux.
After all of the recent activity I
On 5/13/19 12:46 PM, Brian Milby via use-livecode wrote:
I was just able to build for the first time in Ubuntu 18.04 and it comes up 9.5
(dp 1).
I never went far enough to figure out how to overcome the PIC issue myself and
waited for it to make it to develop.
It's still in progress.
Are
I've looked thru the descriptions on how to build it your self on
github, but never tried it.
Maybe it gives some insights, on the other hand for me it may give to
much distraction instead of developing the apps i'm working on
Op 13-5-2019 om 21:46 schreef Brian Milby via use-livecode:
I
I was just able to build for the first time in Ubuntu 18.04 and it comes up 9.5
(dp 1).
I never went far enough to figure out how to overcome the PIC issue myself and
waited for it to make it to develop.
Thanks,
Brian
On May 13, 2019, 3:31 PM -0400, Mark Wieder via use-livecode
, wrote:
> On
On 5/13/19 12:13 PM, JJS via use-livecode wrote:
there is also a 9.0.5rc1, so i think they changed it from 9.1.0dp1 to
9.5.0dp1, but unclear why
My guess is that it was originally a typo that then propagated to
several commits, and by that point it was too much trouble to fix. FWIW
the last
Subject: Re: Android needs 64 bit builds
Message-ID:
Content-Type: text/plain; charset=US-ASCII; format=flowed
a minor thing probably i noticed. The 9.1.0DP1 jumped to 9.5.0DP1. Is
this a typo? or do have to wait longer? Just asking.
___
use
Hopefully it's a type for 9.0.5DP1 since 9.0.4 was released today. I
can't wait to use some new faster Android emulators!
--Andrew Bell
Subject: Re: Android needs 64 bit builds
Message-ID:
Content-Type: text/plain; charset=US-ASCII; format=flowed
a minor thing probably i noticed
a minor thing probably i noticed. The 9.1.0DP1 jumped to 9.5.0DP1. Is
this a typo? or do have to wait longer? Just asking.
Mark Wieder via use-livecode schreef op 2019-05-06 23:26:
On 5/6/19 3:44 PM, Monte Goulding via use-livecode wrote:
Ah. OK. So the problem with running on the pi isn't
On 5/6/19 3:44 PM, Monte Goulding via use-livecode wrote:
Ah. OK. So the problem with running on the pi isn't with building form arm
devices, but with interacting with the pi os?
I believe it is largely an issue of getting the build configuration and
toolchains correct for cross compiling
> On 7 May 2019, at 3:08 am, Mark Wieder via use-livecode
> wrote:
>
> On 5/5/19 9:52 PM, Monte Goulding via use-livecode wrote:
>>> On 6 May 2019, at 12:18 pm, Mark Wieder via use-livecode
>>> wrote:
>>>
Most new devices will be arm64 however I think what you are seeing there
On 5/5/19 9:52 PM, Monte Goulding via use-livecode wrote:
On 6 May 2019, at 12:18 pm, Mark Wieder via use-livecode
wrote:
Most new devices will be arm64 however I think what you are seeing there is the
binaries that you have for use in an emulator. I have come across a few devices
that
Ah ok, that makes it clear. I thought it was related to what one was
able to build for.
Thanks Monte.
Jerry
Op 6-5-2019 om 01:25 schreef Monte Goulding via use-livecode:
On 4 May 2019, at 3:45 am, JJS via use-livecode
wrote:
@Monte. I only see Atom x64 ARM for Android 7.1.1 in the SDK
> On 6 May 2019, at 12:18 pm, Mark Wieder via use-livecode
> wrote:
>
>> Most new devices will be arm64 however I think what you are seeing there is
>> the binaries that you have for use in an emulator. I have come across a few
>> devices that have arm64 processors but did not include the
On 5/5/19 4:25 PM, Monte Goulding via use-livecode wrote:
Most new devices will be arm64 however I think what you are seeing there is the
binaries that you have for use in an emulator. I have come across a few devices
that have arm64 processors but did not include the arm64 OS libraries so
> On 4 May 2019, at 3:45 am, JJS via use-livecode
> wrote:
>
> @Monte. I only see Atom x64 ARM for Android 7.1.1 in the SDK list in Android
> Studio. For all the higher Android versions i only see x86 and no ARM. I
> don't know if there are phones sold which have Android 8.x.x based on
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
JJS via use-livecode
Sent: Friday, May 03, 2019 1:46 PM
To: Richmond via use-livecode
Cc: JJS
Subject: Re: Android needs 64 bit builds
@Monte. I only see Atom x64
@Monte. I only see Atom x64 ARM for Android 7.1.1 in the SDK list in
Android Studio. For all the higher Android versions i only see x86 and
no ARM. I don't know if there are phones sold which have Android 8.x.x
based on ARMx64. Do you know any details?
@Ralph, i did not see that (the
Time to dust off my Intel chip Android tablet
Richmond.
On 3.05.19 г. 1:38 ч., Monte Goulding via use-livecode wrote:
On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode
wrote:
Wow. X86 too! Now we can use the faster emulator. :)
Yes that was the main reason for us doing x86
-boun...@lists.runrev.com] On Behalf Of
Monte Goulding via use-livecode
Sent: Thursday, May 02, 2019 6:39 PM
To: How to use LiveCode
Cc: Monte Goulding
Subject: Re: Android needs 64 bit builds
> On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode
> wrote:
>
> Wow. X86 too
> On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode
> wrote:
>
> Wow. X86 too! Now we can use the faster emulator. :)
Yes that was the main reason for us doing x86 and x86_64 although there are
some devices available for those architectures they aren’t very common so you
probably
Wow. X86 too! Now we can use the faster emulator. :)
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 2, 2019 12:24:21 PM JJS via use-livecode
wrote:
Jacque, check the image on this page :
Jacque, check the image on this page :
https://github.com/livecode/livecode-ide/pull/1990
:)
Op 1-5-2019 om 23:23 schreef J. Landman Gay via use-livecode:
Fantastic. Thank you.
On 5/1/19 3:30 PM, JJS via use-livecode wrote:
it will be in 9.1
Op 1-5-2019 om 17:33 schreef J. Landman Gay via
Fantastic. Thank you.
On 5/1/19 3:30 PM, JJS via use-livecode wrote:
it will be in 9.1
Op 1-5-2019 om 17:33 schreef J. Landman Gay via use-livecode:
I remember your question and have also been waiting for a response.
Hopefully someone on the team will see this, but if not a note to
support
it will be in 9.1
Op 1-5-2019 om 17:33 schreef J. Landman Gay via use-livecode:
I remember your question and have also been waiting for a response.
Hopefully someone on the team will see this, but if not a note to
support may give us an answer.
--
Jacqueline Landman Gay |
I remember your question and have also been waiting for a response.
Hopefully someone on the team will see this, but if not a note to support
may give us an answer.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 1, 2019 9:08:38
This was originally mentioned in a message at the end of January, but
that thread never went anywhere. I submitted an updated app to Google
Play today and noticed the warning message myself for the first time.
It seems we have a few more months to prepare for this, but can't
recall seeing
27 matches
Mail list logo
