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
Currently, make qvm-sdk will kill ~/.cache/common-lisp/<sbcl-cache>. Ideally, it would work with its own cache so that (1) it pulls fresh packages when building, and (2) doesn't affect the current cache, which might be unexpected behaviour.
The text was updated successfully, but these errors were encountered:
From the sdk build's point of view, I think this is usually run inside a fresh docker container via the docker-sdk target. From the standpoint of testing things out without getting docker involved, it should be safe to blow the cache away. In theory it should just mean a potentially slower build the next time you build qvm.
Currently,
make qvm-sdk
will kill~/.cache/common-lisp/<sbcl-cache>
. Ideally, it would work with its own cache so that (1) it pulls fresh packages when building, and (2) doesn't affect the current cache, which might be unexpected behaviour.The text was updated successfully, but these errors were encountered: