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
The Cachelib build output contains many local absolute file path, especially in pkgconfig and cmake files. If we want to copy the output to another machine, we need to put them to the same path, or may not found some dependency when we building. It seems so inflexible.
So, how can we solve this problem if we want our build output library can be used by different user and different hosts?
The text was updated successfully, but these errors were encountered:
The Cachelib build output contains many local absolute file path, especially in pkgconfig and cmake files. If we want to copy the output to another machine, we need to put them to the same path, or may not found some dependency when we building. It seems so inflexible.
So, how can we solve this problem if we want our build output library can be used by different user and different hosts?
The text was updated successfully, but these errors were encountered: