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.

Sign up for GitHub

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

Jump to bottom

Should unite the binary cache directory #426

Closed
spacewander opened this issue Mar 29, 2024 · 1 comment · Fixed by #609
Closed

Should unite the binary cache directory #426

spacewander opened this issue Mar 29, 2024 · 1 comment · Fixed by #609
Labels
good first issue Good for newcomers

Comments

@spacewander
Copy link
Member

Description

Currently, each module has its own binary cache, and some tools are cached in different directories if they are required in different Makefiles. Let's unite the binary cache path.

Environment

  • HTNN version:
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged with no stale labels or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 28, 2024
@spacewander spacewander added good first issue Good for newcomers and removed stale labels Apr 28, 2024
@Chever-John Chever-John mentioned this issue Jun 25, 2024
Merged
spacewander pushed a commit that referenced this issue Jul 2, 2024
@Chever-John
chore: unite the bin cache dir for all projects in go.work (#609)
02945c9 
Fix #426
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: unite the bin cache dir for all projects in go.work Chever-John/htnn
1 participant
@spacewander