Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generator Cache doesn't work with --no-export #673

Open
nicorum opened this issue Feb 21, 2024 · 2 comments · May be fixed by #704
Open

Generator Cache doesn't work with --no-export #673

nicorum opened this issue Feb 21, 2024 · 2 comments · May be fixed by #704

Comments

@nicorum
Copy link

nicorum commented Feb 21, 2024

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?

@olofk
Copy link
Owner

olofk commented Mar 7, 2024

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.

@nicorum
Copy link
Author

nicorum commented Mar 12, 2024

I'm using cache_type: input in the generator core.
Caching works with this generator when not using the --no-export flag.

If you can't reproduce the problem, I can create and upload a minimal example.

@nicorum nicorum linked a pull request Sep 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants