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 Feb 4, 2020. It is now read-only.
So I am using CMake with VS, to avoid the error described in #342 , I am using this at the top of my CMakeLists.txt
set( ENV{CLCACHE_DIR} C:/clcache_cache )
Which works great!... except any calls to things like clcache -s in the terminal still point to the default, userspace, directory for the cache.
This will most likely be because CMake doesn't, and I believe can't export the env var for general use. Would it be possible to have clcache detect where it is currently actually using the cache, or to specify which cache dir to use like clcache -s -d C:/clcache_cache or something similar.
The text was updated successfully, but these errors were encountered:
Yeah that's not too bad, but this will be used with a large development team and having a nicer way to specify which cache I want to inspect would feel better to me!
Or maybe if I run clcache from a cache directory it could detect that.
So I am using CMake with VS, to avoid the error described in #342 , I am using this at the top of my CMakeLists.txt
set( ENV{CLCACHE_DIR} C:/clcache_cache )
Which works great!... except any calls to things like
clcache -s
in the terminal still point to the default, userspace, directory for the cache.This will most likely be because CMake doesn't, and I believe can't export the env var for general use. Would it be possible to have clcache detect where it is currently actually using the cache, or to specify which cache dir to use like
clcache -s -d C:/clcache_cache
or something similar.The text was updated successfully, but these errors were encountered: