Hi David
In a couple of my publications, I described developing apps with Livecode and
referred to www.livecode.org and www.livecode.com, but didn't include anything
in the references as there was nothing (AFAICS at that time) that would satisfy
scientific publication standards.
See:
Hm,
here in LC 9.6.8 RC2 and 10DP4 i see only 'macOS Intel' and 'macOS Apple
(experimental)'.
When i select both, then a universal standalone is created.
So to have separate Intel and M1 versions, I have to run the standalone
building 2 times.
Once with only Intel selected and then once
Indeed, but 'both' results in an app package containing 2 'slices', rather
than 2 distinct apps.
On Mon, 20 Jun 2022, 21:56 Niggemann, Bernd via use-livecode, <
use-livecode@lists.runrev.com> wrote:
> Richmond wrote:
>
> > In the standalone builder you have always separated
> > Linux 32-bit and
Richmond wrote:
> In the standalone builder you have always separated
> Linux 32-bit and 64-bit builds, and the same with
> Windows: could you alter the MacOS standalones so we
> end up with one INTEL 64-bit standalone, and one ARM
> standalone, rather than a awkward sandwich?
In the current
In the standalone builder you have always separated Linux 32-bit and
64-bit builds, and the same with Windows: could you
alter the MacOS standalones so we end up with one INTEL 64-bit
standalone, and one ARM standalone, rather than a awkward sandwich?
Best, Richmond.
On 20.06.22 17:50, Mark
On 2022-06-18 21:27, matthias rebbe via use-livecode wrote:
So, the question now is, is this a macOS problem or is it possible
that a standalone could show the wrong setting due to a wrong
configuration or so when it is created.
It is a macOS (Finder) bug - I think it was the same when they
