Issuing the following from some-path
:
daml build --project-root ../an-outer-path --output example.dar
results in ../an-outer-path/example.dar
.
I would assumed it gives some-path/example.dar
instead. Is this intentional?
Issuing the following from some-path
:
daml build --project-root ../an-outer-path --output example.dar
results in ../an-outer-path/example.dar
.
I would assumed it gives some-path/example.dar
instead. Is this intentional?
I play with this a bit. For example
daml build --project-root ../an-outer-path --output ../some-path/example.dar
results in ../some-path/example.dar
.
While if I issue the following from some-path
:
daml build --project-root ../an-outer-path --output ./example.dar
it still produces the DAR in the project root.
This sounds like a bug. I opened an issue on GitHub: daml build output path is relative to project root instead of being relative to current directory. · Issue #7913 · digital-asset/daml · GitHub
This has been fixed and merged today.
Note that the fix will not be available in the stable 1.7 release scheduled for later today, but will be available in the next 1.8-snapshot (also scheduled for later today) for early testing.
As always, bear in mind that snapshots should not be used for any production use-case, but we very much welcome early feedback on them, as it helps us ensure the stable ones are stable…