daml/3rdparty
Nicolas Mattia f57c74d706 Build and run damlc on Windows (#568)
* Fix network build on Windows

Some files were not added to the build, which led missing symbols at
link time.

* Drop dll.a files from Windows GHC bindist

Those files greatly confuse GHC when linking statically.

* Add some Windows system libraries

These libraries are needed when linking GRPC.

* Statically link pthread on Windows

Otherwise the executables fail at runtime because they cannot find the
shared object.

* Build and run damlc on CI

* Try to fix package_db/* nullglob error

* Fix powershell command

* Cleanup package db rule

* Make formatting ugly again
2019-04-17 20:37:35 +00:00
..
c Enforce consistent formatting of BUILD files. (#412) 2019-04-12 13:10:16 +02:00
haskell Build and run damlc on Windows (#568) 2019-04-17 20:37:35 +00:00
jvm Sandbox - active contracts streaming + transaction validation (#197) 2019-04-08 11:56:14 +02:00
BUILD open-sourcing daml 2019-04-04 09:33:38 +01:00
dependencies.digest use .dars consistently in tests (#484) 2019-04-15 16:45:08 +02:00
NO_AUTO_COPYRIGHT open-sourcing daml 2019-04-04 09:33:38 +01:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
workspace.bzl Move POM file generation to Bazel rules (#374) 2019-04-11 11:24:52 +02:00

Third-Party JVM Dependencies

This subtree contains a Bazel workspace file workspace.bzl and BUILD files underneath jvm/ describing external Java and Scala dependencies. These files are automatically generated and should not be modified manually. If you need to add a third party dependency then modify the file dependencies.yaml in the repository root and re-run bazel-deps in order to regenerate these files as described at the top of the file dependencies.yaml.

Third-Party Haskell Dependencies

The haskell/ subtree contains BUILD files defining custom Hazel builds for Cabal packages imported via Hazel's hazel_custom_package_* rules in the WORKSPACE.