mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-19 08:48:21 +03:00
9f46df8cd6
* Hazel: Shorten target names Previously, Hazel would generate library and binary targets, that repeated the package name in their target name. This easily lead to too long paths on Windows, which could induce errors with code that did not use API functions with long path support. This change modifies Hazel to name the library target "lib" and shorten the binary target names to "bin" or just the Cabal exe component name. This change had further reaching consequences, because the package name in the generated version macros was derived from the library target name. rules_haskell has been extended to allow to override that default behaviour. * data-default: Remove custom build definitions These had been introduced to resolve issues on Windows due to too long target names. Hazel has meanwhile been patched to generate such shorter target names by default, making the custom builds superfluous. * Hazel: unshorten cbits name This is a temporary workaround for otherwise clashing cbits library names in the case of static only linking. |
||
|---|---|---|
| .. | ||
| 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.