Building failed after upgrading to 0.36

OK, then that plan didn’t work out. Thanks for your patience!

Can you build with uno build native --debug to open the project in Xcode, add a breakpoint on exception (exceptions tab in Xcode, plus sign at the bottom left), and run the app until it breaks and paste the disassembly and any other relevant info here?

here u have:

Thanks! Is that after adding an exception breakpoint?

yes… i added a breakpoint on all exceptions

Hmm, then that wasn’t very helpful. What happens if you preview with

fuse preview . -DDISABLE_HARFBUZZ

or build with

uno build native --debug -DDISABLE_HARFBUZZ

?

first one works… second one raises the same exception on Xcode

That’s disappointing, but thanks for testing.

I have tried rebuilding some more of the library dependencies for your CPU. Can you try the following?

/* 1.54MB */ OSX: "https://az664292.vo.msecnd.net/files/Y7tp7tmB5amd9I35-OSX.zip"

If that doesn’t work we will have to look into getting a machine similar to yours to debug this issue on.

Thanks for your patience.

Don’t worry it’s a pleasure being able to help a bit on your work :slight_smile:

here you have the output:

$ uno clean && uno build native --run --libs
Clean completed

Uno 0.47.13 (build 5304) OS X 10.11 i386 627d8b4

Configuring (4.0 s)
Installing dependencies
stuff: GET https://az664292.vo.msecnd.net/files/Y7tp7tmB5amd9I35-OSX.zip
(3.3 s)

Compiling syntax tree (3.1 s)
Generating code and data (6.6 s)
Building Native app (50.1 s)

Build completed in 67.01 seconds


/Users/saul/Desktop/Work/Fuse Projects/sample36/build/Native/Debug/run.sh: line 23: 1560 Illegal instruction: 4 sample36.app/MacOS/sample36

ERROR: Native run failed.

Hi again Zaulin,

We finally got our hands on a machine where we could reproduce this problem,
and we’ve found out that there were several problems with the prebuilt libraries that we ship with Fuse when it comes to compatibility with older Mac models.

I’ve submitted a pull request for a fix, and you can follow its progress here. It’s too late for it to be included in the coming patch release since that’s already being tested, but it will likely be included in the release after that. If you’re feeling brave you can try a local checkout of the fuselibs branch in the pull request linked above in the meantime.

Many thanks for your report, which really helped us nail this one down!

Olle

The Fuse 1.0.1 pre-release, available at https://www.fusetools.com/downloads/channel/qa, now allows you to pass defines to the preview command again, so another workaround for this issue that should work is to start Fuse with fuse preview . -DDISABLE_HARFBUZZ. The fix mentioned above will be included in the release after 1.0.1 if all goes according to plan.

Thanks again!

Olle