That's right. Universal builds would require some major re-tooling and for, at least what I can determine, minimal benefit. After all, we still need to work out DMG/App signing for Gatekeeper which, IMO, should be the higher priority.
On 2026/09/03 17:52:46 [email protected] wrote: > > Am 03.09.2026 um 19:38 schrieb Dave Fisher: > > > >> On Sep 3, 2026, at 9:03 AM, Rory O'Farrell <[email protected]> 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. > > Here’s what ChatGPT has to say about it when asked: > > https://chatgpt.com/s/t_6a99b06444ac81918b93b5e0071aab32 > > yes, But we need to build twice. The main challeng is that our dmake > build system is not made for this, and needs the new feature. > > With bazel we could build universal directly, since it better propagates > the flag through our build then our build system does. > > > > > Best, > > Dave > > > > > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
