You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To me it seems as if parallelising isn't really needed
Do you think it's already being used? I've got zero experience with Xcode or xcodebuild itself, but a quick search suggests that the relevant options would be
Probably we could use the caching logic from macOS?
Yes, it looks like the paths for (a)qt and pip should be the same so the same logic can be used. I guess it should still be duplicated as we would otherwise rely on iOS and macOS using the exact same versions. The cache key has to be adjusted as well, of course.
Activity
ann0see commentedon Mar 5, 2022
To me it seems as if parallelising isn't really needed. Probably we could use the caching logic from macOS?
@hoffie ?
hoffie commentedon Mar 7, 2022
Do you think it's already being used? I've got zero experience with Xcode or
xcodebuilditself, but a quick search suggests that the relevant options would beBut maybe that is already the default? Do you have a way to check? If not, it seems to be possible to read it like that:
Yes, it looks like the paths for (a)qt and pip should be the same so the same logic can be used. I guess it should still be duplicated as we would otherwise rely on iOS and macOS using the exact same versions. The cache key has to be adjusted as well, of course.
ann0see commentedon Mar 7, 2022
I think I googled it once and I think I read that it is enabled by default (I assume this to be true since the build time is not that long).
Probably caching should go in with your refactoring.
ann0see commentedon Apr 22, 2022
@hoffie sorry to tag you here again, but this issue is still outstanding? Feel free to tag it for the next release.