Is this a known issue with Xojo that when you have a App Wrapper script set for MacOS and you don’t tick you want to build for MacOS and you run the project in the IDE it causes an error message from App Wrapper “App Wrapper currently only support Mac Builds”
not sure what the point of your post is… App Wrapper does only support Mac Builds…
Why it it displaying an error message I’m debugging on a Mac just because I haven’t ticked the box for building macOS it shouldn’t cause an error.
The BuildMac variable doesn’t appear to be set to true by Xojo, it would appear this variable is controlled based on if you have ticked macOS.
If you are debugging on macOS but haven’t selected macOS surely the BuildMac variable should be set to true regardless.
why not? if you haven’t ticked the mac box, then it is building for something that is not mac, and Appwrapper doesn’t support builds that are not mac… Just becausing you are building on a mac doesn’t mean what you are doing is compatible with appwrapper
Oh… I see your issue… it isn’t with AppWrapper… .it is why is your script even RUNNING AppWrapper… THAT I would say is an error
You don’t have to select build for macOS if you are debugging on a mac, BuildMac should equal true in this case as you are technically building for macOS.
I’ve worked round the issue by putting two build scripts either side of AppWrapper thats enables BuildMac and then disables it after.
[quote=402466:@Graham Spratt]You don’t have to select build for macOS if you are debugging on a mac, BuildMac should equal true in this case as you are technically building for macOS.
I’ve worked round the issue by putting two build scripts either side of AppWrapper thats enables BuildMac and then disables it after.[/quote]
Please report this as a bug so we can look into it. We’d need a copy of the build script as well.
I’ve raised a report 53127
Huh? This isn’t something that I’ve come across before.
So you debug on the Mac, but you’re making a Windows executable.
Without looking too deep, I’d be inclined to agree with you.
Jason, if you need anything from me, then please let me know.
Okay, so with a little help from Xojo, I’ve changed the constants that the script uses. In my quick tests here, it works as I would expect it to. Please give it a test and let me know how you get on.
Norman replied and closed the case, maybe you want to take a look.
[quote=402497:@Sam Rowlands]Okay, so with a little help from Xojo, I’ve changed the constants that the script uses. In my quick tests here, it works as I would expect it to. Please give it a test and let me know how you get on.
Thanks Sam this does indeed fix it. I only come across this with a few bits of software we use internally that are developed on a mac and are used mostly on Windows so most of the time we don’t have macOS as a build option selected unless we need a macOS build.
You’re welcome, because I don’t do any window (at the moment), I’ve not come across it before and AFAIR it’s not been reported before either, thankfully the guys at Xojo jumped in and quickly found that I was using the wrong constant and let me know. It was an easy fix.
Thanks to the staff members at Xojo for getting involved and making it quick and easy for me to fix, especially when the bug was mine.
Do you already know when you can release it?
Probably this coming week, theres a couple of other bug fixes in that build and almost everybody has confirmed their fixed.
Down to 1 64-Bit issue (that I know off), so that shouldnt be too much longer.
And also done a lot of work on preparing it to be themed in Mojave.
Thank you @Sam Rowlands for your excellent service!