mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-21 09:48:35 +03:00
85c72f87d1
* Move to using proto3-wire from upstream * Move to upstream proto3-suite, with some custom patches in my fork * Delete the BUILD.bazel for hte proto3 stuff, not used and the test was failing * Delete the old proto3-wire and proto3-suite forks * Delete proto3-wire * Prettify BUILD.bazel files, sort the deps * Remove some special cases from the license checker * Delete unused Nix files from grpc-haskell * Switch to upstream proto3-suite * Make old-time work on Windows * Formatting * Patch rules_haskell to use a response file for -optP to avoid overflowing argument size limits on Windows * Update 3rdparty/haskell/BUILD.old-time Co-Authored-By: neil-da <35463327+neil-da@users.noreply.github.com> * Update the comments in old-time * Use the revised location of proto3-suite |
||
---|---|---|
.. | ||
c | ||
haskell | ||
jvm | ||
BUILD | ||
dependencies.digest | ||
NO_AUTO_COPYRIGHT | ||
README.md | ||
workspace.bzl |
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
.