A place to discuss and plan OpenSource xTalk (not exclusively LCC based)
and Community Builds of LCC ...Ask NOT what xTalk can do for you...
Get involved you DO have something to contribute, no matter your skillset!
Forum rules
A place to discuss and plan OpenSource xTalk (not exclusively LCC based) and Community Builds of LCC
Ask NOT what xTalk can do for you... get involved you DO have something to contribute, no matter your skillset!
That's probably all related to my if else statements which are also nested in a case statement. I always forget that MacOS gets itself confused by this.
Also, because I'm picking up someone else's work with the standalone builder, the way it's been constructed... I don't find logical. I mean, yes - I can see why and how it's supposed to do what it does, but I think it's not reaffirming it's selection. Potentially the same issue I found when I tried to use Mark's version of the same stack and clicked on the 'WASM' web option - it doesn't record the selection properly in some instances. I think I know why (to do with an array key not being set), but it's a bit counter intuitive. I would have scripted it differently I think. (but then it probably wouldn't have made sense to anyone except me )
That's the thing with human-typed-code or script: a lot of that person's personality kind of comes through the coding at times, for both better or worse.
That might be purely down to the size and amount of images in the stack, having said that - sounds like it builds quicker when you aren't 'sonoma'-ising it. (if that's a word now).
I think a lot of that delay is due to the MacOS binary filename being changed from "Standalone-" to "Standalone-Community" in the finder at some point. Then the standalone is trying to ad-hoc code sign it, which is probably part of the delay. Should be able to remove a lot of this delay by re-signing the 'Sonoma' patched standalone with the same certificate OXT Lite uses if that theory is correct.
Small stacks, and non-image heavy standalones should be fine *hopefully*
The whole thing is a bit of a cludge, and I'd be the first to admit that. It really needs fixing in the standalone runtime's C++ source to do it properly.
That's even better news.
I think I may have fixed the errant Windows and Linux builds being triggered in the v1.08 beta. If you can open the beta again and check for updates, there should be one that gets applied.
If you can then reopen the IDE and test, it *should* only produce a MacOS standalone when building for Sonoma.
I say *should* as I don't have the means to check this myself, and once again - you seem to have become the beta tester.
richmond62 wrote: ↑Wed Aug 28, 2024 5:28 pm
Oh, and the l-o-n-g time to build standalones...
That's the part that I don't quite understand as of yet. I have a few theories, but can't really test them right now as I need a recent mac to see this on. I'll have to make a stack with loads of images, on multiple cards and see if I can replicate the same thing.... another day.
One thing you could consider is if there is a way to properly time how long building standalones takes (rather than my subjective impression), I can run off DW Pro standalones with LC 963, OXT Lite 107, and 108 tester.
richmond62 wrote: ↑Thu Aug 29, 2024 10:40 am
...if you lob me the link to the new beta . . .
Ah, just seen this - I can see from your screenshot that you have since downloaded the update from yesterday....
richmond62 wrote: ↑Thu Aug 29, 2024 12:53 pm
Building a DW Pro standalone; waiting at 7 minutes . . . and NOTHING inside the build folder yet.
I am going shopping and leaving the thing to churn: back in about 90 minutes.
That's crazy. What about if you build a simple standalone from a new stack - something with just a button or a text field on a single new card?
Meanwhile, I'll create an image-heavy stack and see if I can make a standalone with it. It'll likely be tomorrow (friday) as real life things are keeping me preoccupied.
)
