What I'm adding, and what I'm planning next...

[tperry2x]

Granted, it's not the 'normal' way things are done, but then if you consider LCC's own repo of the community version is split up into two parts, the IDE and the Engine.
What I'm essentially requesting, politely, if possible that the compiled binaries of the engine are made available under the releases section of github for all to download and try.

I'm sure Mark, Paul, myself and others would like to test these out for our two divergent projects. (Our two versions are deliberately different for reasons outlined here). That is intentional. The "Lite" version shouldn't be seen in any way as the gold standard of OXT, it's more me just trying things in as minimalistic fashion as I can. For anything 'official' (for want of a better word), I'd point people towards Paul's OXT build and his Github repos because that is after all, the main project. Mine is essentially just a testbed, which anyone involved in the OXT project is welcome to take bits of for their own use. I have no issue with that at all.

I will reiterate again though, that I certainly didn't mean to cause offence by my inability to use Github. I've tried and failed, and I'm sorry about that. I just can't wrap my head around it, and I've reached saturation-point with it frankly. That's not through lack of trying, and nor is it through lack of help from anyone here. I'll just use it as a glorified FTP directory, as that's what I essentially need from it.

[richmond62]

can you try building on a version of MacOS that isn't a beta

between the devil and the deep blue sea.

At present I have the Mac Mini on Sequoia beta something, and the iMac on MacOS 12: so, currently setting up your "108 tester" on the iMac . . .

On the Mac Mini I tried to build a standalone from my DW Pro code base (120 MB), so really don't know whether uploading such a chunky, clunky file to you is a good idea or not.

I am inclined to try again on both MacOS 15 & MacOS 12 with a smaller stack.

[tperry2x]

I am inclined to try again on both MacOS 15 & MacOS 12 with a smaller stack.

Okay. If that crashes too, then I might know why.
MacOS - or at least the MacOS engine, seems incredibly sensitive about putting if else statements inside a case statement. That might be the cause of it. If it is, it'll require I tweak a single file which I can get you to swap out if that's okay.
(This is why I wanted to do this as a 1.08 beta, and you can see why!) - thanks for being a willing victim!

[richmond62]

thanks for being a willing victim!

-

Screenshot 2024-08-28 at 13.34.20.png (308.62 KiB) Viewed 2593 times

-
Let's see what happens . . .
-

Screenshot 2024-08-28 at 13.36.22.jpg (232.54 KiB) Viewed 2592 times

-

Screenshot 2024-08-28 at 13.38.31.jpg (260.85 KiB) Viewed 2590 times

-
And Building/Churning . . .

[richmond62]

This appears to have got stuck here:
-

Screenshot 2024-08-28 at 13.41.00.png (84.42 KiB) Viewed 2588 times

-
As it did on MacOS 15.
-
BUT now it IS building standalones I DID NOT ask it to: Windows, Linux, and MacOS X:
-

Screenshot 2024-08-28 at 13.43.48.png (59.01 KiB) Viewed 2588 times

-

[richmond62]

Right . . .

I am currently attempting a build AGAIN on MacOS 15, and the first thing I notice is that the stack window is NOT closed (which it is on MacOS 12).

On MacOS 12 I would say the standalone builder took 2-3 longer than the 107 one, and built the wrong standalones.

Over on the Mac Mini (to my right at the moment) the thing is churning and churning on the 'Auto detecting library inclusions' . . .

[tperry2x]

BUT now it IS building standalones I DID NOT ask it to: Windows, Linux, and MacOS X:

Hmmm, okay - I thought those others were selected in your screenshot above, or did you turn them off when you went to build?

[richmond62]

What selected were 64-bit MacOS and Sonoma builds ONLY . . .

And what I got included a Windows build, and Linux build (not specified whether 32 or 64-bit), and a 'generic' MacOS build.

And MacOS 15 is really making heavy weather of things as it is STILL churning with the 'Autodetect' guff: stumping off for a cup of coffee: I'll give it another 10-15 minutes.

[tperry2x]

What selected were 64-bit MacOS and Sonoma builds ONLY . . .

And what I got included a Windows build, and Linux build (not specified whether 32 or 64-bit, and a 'generic' MacOS build.

Hmmm. Okay, I'll have to look at that. It didn't do that for me, but then I don't have a recent Mac to test on, so this is all valuable info.

[tperry2x]

And MacOS 15 is really making heavy weather of things as it is STILL churning with the 'Autodetect' guff: stumping off for a cup of coffee: I'll give it another 10-15 minutes.

Wow! Shouldn't take that long. Seems excessive. I wonder, (not that you should have to), but if you were to choose 'Select Inclusions' from the General tab instead, does that work any better?

[richmond62]

Well, did not go and get some coffee as 'someone' was having a go at me (c.f. my "Bite My Shiny Metal Ass" post), and the Mac Mini running MacOS 15 DID, finally, spit out the same selection of standalones that it did on MacOS 12.

I would assume (?) that there should be at least a 'MacOSX' standalone and a 'Sonoma' standalone: there wasn't.

[tperry2x]

I probably need to (grudgingly) get myself a mac capable of running MacOS 15 so I can test this kind of stuff... problem is, not the kind of thing that's abundantly cheap, and then it's another computer in the house which won't be popular

[tperry2x]

I would assume (?) that there should be at least a 'MacOSX' standalone and a 'Sonoma' standalone: there wasn't.

No, it doesn't at the moment. If that Sonoma checkbox is on, the mac version it spat out will have the sonoma patch.

I appreciate you testing all this, because otherwise I'd never know if it works on Sonoma+ or not. Having said that, your devawriter stack - does it use a custom macOS style menu at all?

[richmond62]

2018 Mac Minis running on ebay.co.uk at about £250 at the moment . . . personally I would ask if that is worth it.

[tperry2x]

2018 Mac Minis running on ebay.co.uk at about £250 at the moment . . . personally I would ask if that is worth it.

Yes, and I'd probably be better off getting myself an arm-based mac as that's the way things are going / have gone, if I'm serious about maintaining a mac build into the future.

[richmond62]

Indeed.
-

Screenshot 2024-08-28 at 14.10.00.png (115.47 KiB) Viewed 2599 times

[tperry2x]

Hmmm, with 5 days left. Time for silly bids aplenty I suspect.

Anyway, sorry - I digress. Am I right in thinking your Devawriter stack doesn't have a custom MacOs-style menu? If there's no custom MacOS menu used, you don't actually need the Sonoma patch. As mentioned in that warning alert, I also half expect image corruption issues with it turned on. (missing images)

This is where Paul was going to also test, because he wants to see if 'Prepare image' does the trick in sorting out those subsequent image issues or not.

But either way, I appreciate the testing nonetheless.

[richmond62]

Indeed: but a bit of scrolling and you might find a reasonably priced "buy now" option.

[richmond62]

No, my Devawriter has no menu items.

[tperry2x]

No, my Devawriter has no menu items.

Okay, well if it has built - I'd go through and now check for missing images. (don't want to sound pessimistic), but I have a nasty feeling I'm being realistic.