search for: lldnativ

...exist. [ 1501s] This warning is for project developers. Use -Wno-dev to suppress it. [ 1501s] [ 1501s] CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle): [ 1501s] "lldPasses" of type SHARED_LIBRARY [ 1501s] depends on "lldNative" (weak) [ 1501s] depends on "lldYAML" (weak) [ 1501s] "lldNative" of type SHARED_LIBRARY [ 1501s] depends on "lldYAML" (weak) [ 1501s] depends on "lldPasses" (weak) [ 1501s] "lldYAML" of type SHARED_LIBRARY [ 1501s] depends...

...my debug build (that has dynamic linking to avoid re-linking of huge libraries during development cycle), and I got this: CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle): "lldPasses" of type SHARED_LIBRARY depends on "lldNative" (weak) depends on "lldYAML" (weak) "lldNative" of type SHARED_LIBRARY depends on "lldYAML" (weak) depends on "lldPasses" (weak) "lldYAML" of type SHARED_LIBRARY depends on "lldNative" (weak) depends on "...

We are modeling target specific functionally using references, Doesn't your idea defeat the purpose of the atom model? Atoms are mostly target neutral and yaml/native format represents just an atom. Having a derived class for atoms will have a impact on the testing method with lld IMO. We could continue to model using references in my opinion and add some meta data information in the atom