Why are the libraries always re-build?

[rempas]

I'm trying to built the calculator example from the ui library and for a production build, it takes about 19 seconds on my machine. This is 80% slower than ved and the source code of the example is 16 times less so I'm pretty sure that V always builds "ui" too.

But why is this happening? It doesn't make much sense as the library will never change from me. How can I have the library to not automatically be build every time?

[changrui]

use-cache?

[rempas]

@spytheman Do you know if -usecache creates the library/executable for the library in a global scope? If I create another project, will I have to re-create the cache for that library the first time that I will try to compile?

[spytheman]

The cache for the modules is global, so it will work for all programs that use the same module (like builtin for example is used by every V program).

The cache keys however are dependent on the used CLI options, i.e.
v -usecache -prod file.v,
... will use a different cache entry for each module, than:
v -usecache file.v
... and a different for:
v -usecache -cflags -O2 file.v

[rempas]

That's awesome! From what you said:

NB: -usecache is not yet the default, because some modules are not compatible yet with -usecache (mainly the ones that depend on generics like datatype or math for example).

I suppose that you know that this will become the default in the future when it becomes stable?

[spytheman]

Yes, afaik it will be on by default, when it improves to work for all V code, including code that uses generics.

[rempas]

That's awesome! Thanks for your time!