Skip to content
The DAML smart contract language
Branch: master
Clone or download
akalburgi and mergify Adding stepts to run daml scenario in daml-ghc readme (#619)
* Adding stepts to run daml scenario in damlc

* Adopting the suggested change
Latest commit 2b3c4e7 Apr 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.vscode
3rdparty Build and run damlc on Windows (#568) Apr 17, 2019
bazel_tools Build //daml-assistant:daml on Windows (#595) Apr 18, 2019
build-scripts
ci windows: full build; more targets (#529) Apr 17, 2019
compiler
da-assistant
daml-assistant
daml-foundations Adding stepts to run daml scenario in daml-ghc readme (#619) Apr 19, 2019
daml-lf Check contract visibility when looking up contracts in sandbox (#405) Apr 19, 2019
dev-env
docs
extractor
ghc-lib
hazel open-sourcing daml Apr 4, 2019
infra
language-support
ledger-api
ledger
libs-haskell
navigator Navigator: Print important messages to stderr (#522) Apr 16, 2019
nix bazel: move .bazelrc back to the repo root (#596) Apr 18, 2019
notices-gen Enforce consistent formatting of BUILD files. (#412) Apr 12, 2019
oss-compliance
pipeline/samples Enforce consistent formatting of BUILD files. (#412) Apr 12, 2019
rattle
release Release codegen front-end shaded binary, #615 (#617) Apr 19, 2019
replacements
rules_daml
scala-protoc-plugins
sdk Enforce consistent formatting of BUILD files. (#412) Apr 12, 2019
web-ide
.bazelignore open-sourcing daml Apr 4, 2019
.bazelrc bazel: move .bazelrc back to the repo root (#596) Apr 18, 2019
.dadew
.dockerignore
.envrc
.gitattributes
.gitignore Prototype to accelerate Windows development (#411) Apr 12, 2019
.hlint.yaml
.mergify.yml strictify mergify (#576) Apr 17, 2019
.scalafmt.conf open-sourcing daml Apr 4, 2019
.stylish-haskell.yaml
.watchmanconfig
BAZEL-JVM.md
BAZEL-haskell.md
BAZEL.md Remove damli completely (#481) Apr 15, 2019
BUILD
CHANGELOG
CODE_OF_CONDUCT.md open-sourcing daml Apr 4, 2019
CONTRIBUTING.md Clean up the guidelines for PR title/description (#427) Apr 12, 2019
COPY HOTFIX rename COPYRIGHT so github correctly shows apache2 license for… Apr 6, 2019
LICENSE
NOTICES open-sourcing daml Apr 4, 2019
README.md ***NO_CI*** download sdk badge (#269) Apr 12, 2019
VERSION
WORKSPACE Integrate ghc-lib-0.20190417 (#588) Apr 18, 2019
azure-pipelines.yml
build.ps1 Build SDK release tarball on Windows (#597) Apr 18, 2019
build.sh run perf tests separately (#605) Apr 18, 2019
daml-logo.png open-sourcing daml Apr 4, 2019
dependencies.yaml
deps.bzl Build and run damlc on Windows (#568) Apr 17, 2019
dotfiles
fmt.sh Enforce consistent formatting of BUILD files. (#412) Apr 12, 2019
package.json Map Protobuf's 64 bit integers to strings in JS (#324) Apr 9, 2019
release-dry-run.sh Unify Scala and Java Codegen Inputs (#585) Apr 18, 2019
scalafmt.sh
tsconfig.json
util.bzl Build grpc-haskell on Windows (#532) Apr 16, 2019
yarn.lock open-sourcing daml Apr 4, 2019

README.md

DAML logo

Build Status Build Status License

Download SDK

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 and SDK, 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. The DAML SDK is a set of tools to help you develop applications based on DAML.

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 the DAML SDK

We warmly welcome contributions. To get set up for contributing to the SDK, follow these instructions:

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

  1. Use cd daml to switch into the new daml repository you just cloned
  2. Install Nix by running: bash <(curl https://nixos.org/nix/install)
  3. Enter dev-env by running: 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.

You can’t perform that action at this time.