|
|
||
|---|---|---|
| .vscode | ||
| 3rdparty | ||
| bazel_tools | ||
| build-scripts | ||
| ci | ||
| compiler | ||
| da-assistant | ||
| daml-assistant | ||
| daml-foundations | ||
| daml-lf | ||
| dev-env | ||
| docs | ||
| extractor | ||
| ghc-lib | ||
| hazel | ||
| infra | ||
| language-support | ||
| ledger | ||
| ledger-api | ||
| libs-haskell | ||
| navigator | ||
| nix | ||
| notices-gen | ||
| oss-compliance | ||
| pipeline/samples | ||
| release | ||
| replacements | ||
| rules_daml | ||
| scala-protoc-plugins | ||
| sdk | ||
| web-ide | ||
| .bazelignore | ||
| .dadew | ||
| .dadew_azure | ||
| .dockerignore | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| .hlint.yaml | ||
| .scalafmt.conf | ||
| .stylish-haskell.yaml | ||
| .watchmanconfig | ||
| azure-pipelines.yml | ||
| BAZEL-haskell.md | ||
| BAZEL-JVM.md | ||
| BAZEL.md | ||
| BUILD | ||
| build.Jenkinsfile | ||
| build.ps1 | ||
| build.sh | ||
| CHANGELOG | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| COPYRIGHT | ||
| daml-logo.png | ||
| dependencies.yaml | ||
| deps.bzl | ||
| dotfiles | ||
| LICENSE | ||
| NOTICES | ||
| package.json | ||
| README.md | ||
| release-dry-run.sh | ||
| scalafmt.sh | ||
| tsconfig.json | ||
| VERSION | ||
| WORKSPACE | ||
| yarn.lock | ||
Copyright 2019 Digital Asset (Switzerland) GmbH and/or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0
Welcome to the DAML repository!
This repository hosts all code for the DAML smart contract language, originally created by Digital Asset. DAML is an open-source smart contract language for building future-proof distributed applications on a safe, privacy-aware runtime.
To start using DAML
To download DAML, follow the installation instructions on docs.daml.com. To try out using it, follow the quickstart guide.
If you have questions about how to use DAML or how to build DAML-based solutions, please ask
them on StackOverflow using the daml tag.
To start contributing to DAML
We warmly welcome contributions.
1. Clone this repository
git clone git@github.com:digital-asset/daml.git.
2. Set up the DA Development Environment ("dev-env")
dev-env provides dependencies required during the build phase, like Java, Bazel, and Python
for some tooling scripts. The code itself is built using Bazel.
Set up dev-env on Linux or macOS
- Install Nix:
bash <(curl https://nixos.org/nix/install) - Enter
dev-env:eval "$(dev-env/bin/dade assist)"
If you don't want to enter dev-env manually each time using eval "$(dev-env/bin/dade assist)",
you can also install direnv. This repo already provides a .envrc
file, with an option to add more in a .envrc.private file.
Set up dev-env on Windows
We're working on Windows support (for both end users and developers), but it's not ready yet. Sign up to be notified when it is available.
3. Build the source code
Run bazel build //...
This builds the code, and will likely take an hour or more.
Now you've built, rebuilding the code after a change will be much faster because Bazel caches unchanged build artefacts. To read more about Bazel and how to use it, see the Bazel site.
To run the tests, run bazel test //...
4. Contribute!
If you are looking for ideas on how to contribute, please browse our issues.
Caching: build speed and disk space considerations
Bazel has a lot of nice properties, but they come at the cost of frequently rebuilding "the world".
To make that bearable, we make extensive use of caching. Most artifacts should be cached in our CDN,
which is configured in .bazelrc in this project.
However, even then, you may end up spending a lot of time (and bandwidth!) downloading artifacts from
the CDN. To alleviate that, by default, our build will create a subfolder .bazel-cache in this
project and keep an on-disk cache. This can take about 10GB at the time of writing.
To disable the disk cache, remove the following lines:
build:linux --disk_cache=.bazel-cache
build:darwin --disk_cache=.bazel-cache
from the .bazelrc file.
If you work with multiple copies of this repository, you can point all of them to the same disk cache
by overwriting these configs in either a .bazelrc.local file in each copy, or a ~/.bazelrc file
in your home directory.