Cache directories of `daml build`

Is there a way to define where the daml build command is placing the .daml directory?

If I run

cd /some/random/cwd
daml build --project-root /path/to/daml/project/foo --output /some/output/path

then the .daml directory ends up in /path/to/daml/project/foo where the daml.yaml exists. However, this confuses our build system as then the build system thinks that the project directory changed.

2 Likes

Right now there is no way to configure this directory. However, it wouldn’t be too hard to add. Maybe an environment variable would be a good option?

1 Like

I think using command line arguments would be better as this would be consistent with the UX of daml build.

1 Like

Works for me as well. I was mainly suggesting an environment variable because I’ve seen that quite commonly for other tools that have some caching directory.

1 Like

If you’re adding new options, would you mind trying to revive/conclude the discussion on Review and refactor Sandbox, JSON API, Extractor and maybe Navigator configurations · Issue #4610 · digital-asset/daml · GitHub first?

1 Like