USDCore plugin Mac arm64 build issue

This question was created in reference to: [Fail to load USD plugin during cooking on Mac [Content removed]

Hi! We’re upgrading to 5.5.4 from 5.3.x and after we’ve got new engine we’ve met an issue with building our project for Mac, during the packaging of the project we got a bunch of .dylib files missing for USDCore plugin, see the log attached.

As a temporary solution we’ve found out that putting libusd_usd.dylib, libusd_usdMtlx.dylib and usdAbc.dylib (taken from /Engine/Plugins/Runtime/USDCore/Source/ThirdParty/Mac/bin after engine build) to Binaries/Mac folder in the game repo manually solves the issue.

Could you please clarify what’s the proper way to solve this? I can provide full build log if needed.

Best regards,

Daniil.

Hi Daniil,

Can you share the content of this file: USDCore/Resources/UsdResources/Mac/plugins/usdAbc/resources/plugInfo.json?

Also, if you launch the cook from xcode or with a debugger connected, can you see where libusd_arch.dylib is loaded from?

Regards,

Anousack

Hi Anousack!

Here’s the content of plugInfo.json, I’ll try to give info regarding libusd_arch.dylib a bit later.

Regards,

Daniil

Hi Daniil,

The file looks ok.

Is there anything particular about your binaries (you build from source with modifications) or the way you package your project (from command-line as part of some automation)?

I’ve tested both with the binaries from the Epic Games Store Launcher and built from source in Xcode and I do not see any issues when I “Package Project” from the editor.

Hi Anousack,

I’ve used build from source with our engine modifications but most likely they have nothing to do with the plugin, so there’s nothing much special about it, and also the packaging is performed manually right from the editor.

I’ll continue investigation on our side and will provide the updates on this if anything appears, thanks!

Regards,

Daniil.

Hi Daniil,

Yeah your engine modifications shouldn’t cause this, rather it was to confirm that our distributed binaries did not exhibit this issue. I don’t know how you package and deploy your custom binaries but it looks like this is where the issue is coming from? I don’t know why it’s only those 3 .dylib it fails to find though.