Buildbot: use universal binary for macOS on Steam #58

New Issue

Brecht Van Lommel · 2023-04-13T14:36:13+02:00

Brecht Van Lommel commented

2023-04-13 14:36:13 +02:00

Currently it's always x86_64 as Steam does not support architecture specific builds.

Probably it's possible to create a single .app from two different ones with a script, without changing the Blender build process itself. This would require the macOS build to be made from the exact same revision, which is not guaranteed by the buildbot currently.

Currently it's always x86_64 as Steam does not support architecture specific builds. Probably it's possible to create a single .app from two different ones with a script, without changing the Blender build process itself. This would require the macOS build to be made from the exact same revision, which is not guaranteed by the buildbot currently.

Brecht Van Lommel referenced this issue from blender/blender

2023-04-13 14:36:50 +02:00

Blender Steam always installs Intel Executable even on ARM-based Macs #106444

Brecht Van Lommel added the

buildbot

label 2023-04-13 14:37:04 +02:00

Sergey Sharybin commented

2023-07-03 13:54:17 +02:00

This can be done using the lipo command. I think it can be done as a packaging step for Steam, and it operates on 2 binary builds (as in, no need to pass anything special to the compiler).

We did something very similar for the OpenData launcher there: infrastructure/blender-open-data@f09d081b66

One thing to keep in mind is that it needs to be done for blender executable and all dylibs we share.

This can be done using the `lipo` command. I think it can be done as a packaging step for Steam, and it operates on 2 binary builds (as in, no need to pass anything special to the compiler). We did something very similar for the OpenData launcher there: infrastructure/blender-open-data@f09d081b660 One thing to keep in mind is that it needs to be done for blender executable and all dylibs we share.

Sign in to join this conversation.