Building for M1

Question

Building for M1

esphynox opened this issue 3 years ago · 9 comments

esphynox commented 3 years ago

Compilation fails for Apple Silicon processor.

Error:

I believe this issue isn't about Xcode wrapper but about libde265 itself. Can we find workaround to make this work?

Answer 1 · 2021-11-22T03:33:18.000Z

Maybe we should fire GitHub issue firstly to the author: https://github.com/strukturag/libde265/issues

Next, for workaroung, maybe we can now modify that file or provide a overlay, using CocoaPods or SwiftPM to do this...

Put the same header file and move the header search path (-I) beyond the original one, to make other files compiled with load this mock file firstly.

Answer 2 · 2021-11-22T03:34:06.000Z

Wait, did this file get loaded in on macOS only ? Maybe we can get a better workaround.

Answer 3 · 2021-11-22T11:03:06.000Z

Yes, this issue occurs only when building for macOS.

Answer 4 · 2021-11-22T11:09:26.000Z

Oh, I noticed someone opened issue in libde265 - strukturag/libde265#308

Answer 5 · 2021-11-26T11:01:58.000Z

I think I found way to build correct fat framework without modifying libde265 itself. Will add PR soon.

Answer 6 · 2021-11-30T10:56:16.000Z

Hi there. I currently came up with two working ideas.

Remove all sse files from building. Its kinda easy and requires a little modification of .xcodeproj file, but I'm not sure how it will affect performance on x86 processors.
Have separate targets for x86 and Arm processor. This approach will require more work, since we will need to build those two libraries separately and merge them via some script that will perform lipo operation.

Maybe you can clarify for me what will exactly happen if I will remove sse.h includes from x86 library?

Answer 7 · 2021-12-14T13:09:15.000Z

Created PR, @dreampiggy

Answer 8 · 2021-12-15T09:03:01.000Z

Hi.
Recently I'm busying in daily work and may have no enough time for open-source project. I'll have a check for small changes PR soon.
For large refactory or features, please try to summerize the idea and core changes, and I may check back in weekend.

Answer 9 · 2021-12-17T09:57:52.000Z

Actually... The raw Xcodeproj for Carthage may not get long time maintained...Beucase the reason for this repo was for CocoaPods && SwiftPM. Carthage is deprecated..

Anyway, I'll release a new path version firstly.