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
When using the --no-export argument the generator cache gets placed in the build/<core>/<target>-<tool>/generator_cache folder instead of the .cache/fusesoc/generator_cache folder. But this folder is removed at the start of each fusesoc run. Which is why the generator_cache does not work with the --no-export argument.
I can fix this problem for me by removing self.gen_root from the line that contains self.gen_root or self.core.cache_root, in the Ttptttg class. But I don't want to create a pull request with the possible fix. Because I don't understand what the exact purpose of using self.gen_root is. Is this behaviour intended?
The text was updated successfully, but these errors were encountered:
Hmm... good question. There is some complexity in that part of the code, so I can't honestly say right away if it's a bug or the intended way. One thing though, did you mark your generator as cacheable? That also needs to be done.
When using the --no-export argument the generator cache gets placed in the
build/<core>/<target>-<tool>/generator_cache
folder instead of the.cache/fusesoc/generator_cache
folder. But this folder is removed at the start of each fusesoc run. Which is why the generator_cache does not work with the --no-export argument.I can fix this problem for me by removing
self.gen_root
from the line that containsself.gen_root or self.core.cache_root,
in theTtptttg
class. But I don't want to create a pull request with the possible fix. Because I don't understand what the exact purpose of using self.gen_root is. Is this behaviour intended?The text was updated successfully, but these errors were encountered: