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
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Where does buck cache server store the actual cache?
Also, can I configure the path?
I'm looking at running 2 cache servers (on different ports) on the same machine.
The reason for that is buck's current limitation with support for min sdk compiler option (facebook/buck#1803).
There's no way to set min sdk per target and in our case we have a bunch or libraries that need to be built both for iOS 9 and 10, depending on which app we plan to integrate them into.
This means a cache generated for iOS 10.0 build is not usable when building for 9.0, causing all kinds of errors.
Until buck has that option, we just have 2 different cache directories per min sdk.
So we'd want to have 2 cache servers running for each target sdk, and we need to make sure each server will have its separate storage path.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Where does buck cache server store the actual cache?
Also, can I configure the path?
I'm looking at running 2 cache servers (on different ports) on the same machine.
The reason for that is buck's current limitation with support for min sdk compiler option (facebook/buck#1803).
There's no way to set min sdk per target and in our case we have a bunch or libraries that need to be built both for iOS 9 and 10, depending on which app we plan to integrate them into.
This means a cache generated for iOS 10.0 build is not usable when building for 9.0, causing all kinds of errors.
Until buck has that option, we just have 2 different cache directories per min sdk.
So we'd want to have 2 cache servers running for each target sdk, and we need to make sure each server will have its separate storage path.
The text was updated successfully, but these errors were encountered: