Am 4. September 2026 13:58:42 MESZ schrieb Jim Jagielski <[email protected]>:
>I like that idea... I'm sure some Installer code could determine the arch and
>then copy the correct binary as required. I've never written anything like
>that, macOS-wise that is...
I don't think that is needed.
Build both versions separately
Then use apple tooling to create a combined version. At least this is my
understanding from chat got.
IMHO that returns is to the gatekeeper question. I am Sure WE find some
solution before Release.:)
>
>On 2026/09/03 16:03:19 Rory O'Farrell wrote:
>> On Thu, 3 Sep 2026 17:56:56 +0200
>> [email protected] wrote:
>>
>> >
>> > Am 03.09.2026 um 14:45 schrieb Jim Jagielski:
>> > > Hmmm if when doing a macOS build it tries to do Linux packaging, then
>> > > something is seriously wonky.
>> >
>> > This is the proposal the ai did for my build
>> >
>> > Is ~6–8 focused edits in
>> > |scp2/source/python/{file,profileitem,module}_python.scp| — make the
>> > macOS branches follow the existing non-macOS UNX path
>> > (|python-core-$(PYVERSION).zip|, |libpython3.11.dylib|,
>> > |$ORIGIN/python-core-…| for |PYTHONHOME|/|PYTHONPATH|), and delete the
>> > framework |Directory|/|Unixlink| block for macOS. It matches what's
>> > actually built. There's one runtime unknown (pyuno's |-framework Python|
>> > link flag on macOS) that we'd shake out by launching the built app.
>> >
>> > Can pus it for review.
>> >
>>
>>
>> A crude but easy suggestion: package both MacOS builds together, and them
>> with a small piece of code that decides which to install. The User need not
>> be queried about the CPU type.
>>
>> Not an elegant solution, but quick and simple.
>>
>> Rory
>>
>> > >> On Sep 3, 2026, at 8:12 AM, Peter Kovacs<[email protected]> wrote:
>> > >>
>> > >>
>> > >>
>> > >> Am 3. September 2026 12:00:37 MESZ schrieb Jim Jagielski
>> > >> <[email protected] <mailto:[email protected]>>:
>> > >>>
>> > >>>> On Sep 3, 2026, at 2:00 AM,[email protected] <mailto:[email protected]>
>> > >>>> wrote:
>> > >>>>
>> > >>>> Hi all,
>> > >>>>
>> > >>>> I was able to build a complete production build. Only the packaging
>> > >>>> did not work.
>> > >>> What happened during the packaging? I've been able to create the full
>> > >>> DMG.
>> > >> It was about the python 3 layout. Afaik it was in Linux layout but the
>> > >> packager expected something different.
>> > >> But exact issue I need to check again. I don't think it is a big deal.
>> > >> Maybe the config option was wrong too.
>> > >>>> Awesome work jim! I was not aware we are that far.
>> > >>>> I do a smoke test if that works then i will distribute the test
>> > >>>> version for testers. (the issue czeslaw found should be applicable on
>> > >>>> this build too.
>> > >>>>
>> > >>>> The fix is in testing on windows. If you want to test but do not have
>> > >>>> a machine I can provide you project referenced machine.
>> > >>>>
>> > >>>> I try to build intel version next.
>> > >>>>
>> > >>>> All the best
>> > >>>>
>> > >>>> Peter.
>> > >>>>
>> > >>>>
>> > >>>> ---------------------------------------------------------------------
>> > >>>> To unsubscribe, e-mail:[email protected]
>> > >>>> For additional commands, e-mail:[email protected]
>> > >>>>
>> > >>> --
>> > >>> Jim
>> > >>> "This is an outrage!"
>> > >>> Tony Harrison
>> > >>>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail:[email protected]
>> > >> <mailto:[email protected]>
>> > >> For additional commands, e-mail:[email protected]
>> > >> <mailto:[email protected]>
>> > > --
>> > > Jim
>> > > "This is an outrage!"
>> > > Tony Harrison
>> > >
>> > >
>>
>> --
>> Rory O'Farrell <[email protected]>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
