I have the following directory structure setup, to support building of multiple *.dar files (an interface and an implementation): src/interface/daml.yaml src/implementation/daml.yaml src/main/daml.yaml src/main/daml/Daml/Finance/Implementation/Token.daml src/main/daml/Daml/Finance/Interface/Transfe…

Hi @Luciano . As far as I can tell, the source field in a daml.yaml file defines either a .daml file to use as an entry point for compilation, or a directory, which is equivalent to having every .daml file in said directory (including nested files) simultaneously as entry points. Then, during com…

I should add here, that in a previous approach, instead of using the source : with a relative path, I created symlinks from within src/interface and src/implementation pointing inside src/main/Daml/Finance/{Interface, Implementation}. And I guess my surprise comes from the fact that in this setup, …

This is still surprising behavior, don’t get me wrong, but it arises from the implicit assumption in the compiler that the source field in daml.yaml will always be a file or directory under or equal to the directory with the daml.yaml file, which breaks when a .. parent directory is used. I think t…

Maybe a bit of history helps understand the current behavior: There are two concepts here which are orthogonal in the current implementation but from a user pov probably shouldn’t be. The first is the list of roots modules that are included in the DAR produced by daml build. Initially, you could o…

[image] cocreature: For that, we search for that file in all import paths and take the first match. If it is not found, we search in dependencies and if it doesn’t exist, we fail. So what are the import paths? It is the list of paths specified via -I but there is one special case: For module A.B…

[image] cocreature: It is the list of paths specified via -I but there is one special case: For module A.B.C located in file path/to/A/B/C.daml we add path/to to the front of the import path. I’m confused as to whether you are referring to A.B.C in the build-options : --include=path/to/A/B/C.…

Let’s say we’re trying to process module A.B.C from path/to/A/B/C.daml. This could be either because the file is a root itself (meaning it’s part of source) or because it was transitively imported from a root. Doesn’t really matter why we’re processing it. Now that file has a bunch of imports, let’…

Behaviour of relative paths in `source:` in multi-dar projects

App Development

Topic		Replies	Views
Daml.yaml source parameter, is it a single value or a list App Development daml , damlyaml	15	478	February 27, 2022
Build multiple DAML files App Development daml	2	405	September 17, 2020
Module collisions in multi-dar projects App Development	1	247	February 21, 2022
Git submodules with multiple daml source directories App Development	13	660	February 3, 2021
Module ‘Daml.Script’ It is a member of the hidden package ‘daml-script-1.10.0’ App Development sdk_1_10_0	3	781	March 12, 2021

Behaviour of relative paths in `source:` in multi-dar projects

Related topics