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 above code can successfully call the C function, but when I rebuild the libabc.a library, the unit tests still use the old libabc.a file. Even deleting the libabc.a file doesn't prevent the program from running.
I tried running go clean -cache, but it didn't work. Running go clean -cache -modcache does force the use of the new library, but rebuilding the program after running go clean -cache -modcache takes a very long time. If every modification to the library requires such a lengthy rebuild, it's unacceptable. How can this be resolved?
What did you expect to see?
Linked library changes should apply instantly, no cache clearing needed.
The text was updated successfully, but these errors were encountered:
Go version
go version go1.24.3 linux/amd64
Output of
go env
in your module/workspace:What did you do?
abc.go
abc_test.go
What did you see happen?
The above code can successfully call the C function, but when I rebuild the
libabc.a
library, the unit tests still use the oldlibabc.a
file. Even deleting thelibabc.a
file doesn't prevent the program from running.I tried running
go clean -cache
, but it didn't work. Runninggo clean -cache -modcache
does force the use of the new library, but rebuilding the program after runninggo clean -cache -modcache
takes a very long time. If every modification to the library requires such a lengthy rebuild, it's unacceptable. How can this be resolved?What did you expect to see?
Linked library changes should apply instantly, no cache clearing needed.
The text was updated successfully, but these errors were encountered: