Support device-only frameworks when run cache warm

[kientux]

Caching is a great feature of Tuist, I move from CocoaPods to Tuist because of how easy Tuist enable caching for targets and dependencies. My team runs CI build alot and with cached targets we save hours of time per day.

Tuist does not support device-only frameworks when cache targets. This brings up two problems:

• Our CI builds are for real test devices, so we must enable cache with --xcframeworks. But this will build each target 2 times, one for device and one for simulator. This doubles the cache build time and simulator parts are wasted because of not being used.
• Our projects contain some closed-source prebuilt xcframeworks that support only x86_64 simulator. Currently our CI macs are Intel-based so Tuist cache builds will work. But if in the future we switch to ARM macs then cache builds will produce error:

While building for iOS Simulator, no library for this platform was found in '...xcframework'

So it would be great if Tuist has an option to build cache into device-only frameworks.

// This is not a bug report so I create a new discussion, not sure if this belongs here.

[danieleformichelli]

I think it makes sense. @fortmarek or @kwridan do you have in mind any problem it might come with this?

[fortmarek]

Yeah, I agree. I think we can support this in the Cache profile. You could then build the framework only for simulator or for device here.

Using a cache profile, it should also be automatically included in the framework's hash to ensure we don't pull in a framework that's not compatible with the target we're building for.

@kientux, would you want to try and build this? Happy to help out 🤞

[kientux]

Yeah, using cache profile is great. I will try to work on this. If I can make it work there will be a PR soon, thanks.

[kientux]

I'm unable to commit because of this linting. But those "offenses" aren't even in my works 😁 How to fix or disable this?

// Nevermind, it seems that all is fixed in latest main, just need to rebase to my branch

[shahzadmajeed]

Why not generate project with “Build Active Architectures” set to yes and then do normal caching?

On Tue, Jan 10, 2023 at 1:07 PM Daniele Formichelli < ***@***.***> wrote: I think it makes sense. @fortmarek <https://github.com/fortmarek> or @kwridan <https://github.com/kwridan> do you have in mind any problem it might come with this? — Reply to this email directly, view it on GitHub <#4972 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJHI44BX433EEJ4DOLYVQ3WRWQP5ANCNFSM6AAAAAATXB2UWM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Sent from my iPhone.

[kientux]

Why not generate project with “Build Active Architectures” set to yes and then do normal caching?

This relies on how Tuist run cache build command I guess? Even if project set ONLY_ACTIVE_ARCH to YES (which is default value for Debug configuration anyway), Tuist still builds and archives 2 cache frameworks for each target.

[shahzadmajeed]

Really? Even if you don’t specify —xcframeworks (-x) param?

On Tue, Jan 10, 2023 at 9:00 PM Kien Nguyen ***@***.***> wrote: Why not generate project with “Build Active Architectures” set to yes and then do normal caching? This relies on how Tuist run cache build command I guess? Even if project set ONLY_ACTIVE_ARCH to YES (which is default value for Debug configuration anyway), Tuist still builds and archives 2 cache frameworks for each target. — Reply to this email directly, view it on GitHub <#4972 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJHI457UA2LR6R3P5OWSNDWRYH45ANCNFSM6AAAAAATXB2UWM> . You are receiving this because you commented.Message ID: ***@***.***>

-- Sent from my iPhone.

[kientux]

No, only when --xcframeworks is enabled. What I want to say here is Tuist has full control over this and nothing we Tuist users can do.