2019-07-05 17:04:47 +03:00
|
|
|
|
workspace(
|
|
|
|
|
|
name = "com_github_digital_asset_daml",
|
|
|
|
|
|
managed_directories = {
|
|
|
|
|
|
"@npm": ["node_modules"],
|
2019-07-08 12:40:48 +03:00
|
|
|
|
"@daml_extension_deps": ["compiler/daml-extension/node_modules"],
|
2019-07-05 17:04:47 +03:00
|
|
|
|
"@navigator_frontend_deps": ["navigator/frontend/node_modules"],
|
2020-01-22 00:23:51 +03:00
|
|
|
|
"@language_support_ts_deps": ["language-support/ts/packages/node_modules"],
|
2019-07-05 17:04:47 +03:00
|
|
|
|
},
|
|
|
|
|
|
)
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
2019-04-23 15:56:40 +03:00
|
|
|
|
# NOTE(JM): Load external dependencies from deps.bzl.
|
|
|
|
|
|
# Do not put "http_archive" and similar rules into this file. Put them into
|
|
|
|
|
|
# deps.bzl. This allows using this repository as an external workspace.
|
2021-07-12 19:11:52 +03:00
|
|
|
|
# (though with the caveat that that user needs to repeat the relevant bits of
|
2019-04-23 15:56:40 +03:00
|
|
|
|
# magic in this file, but at least right versions of external rules are picked).
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load("//:deps.bzl", "daml_deps")
|
2020-06-24 20:40:03 +03:00
|
|
|
|
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive", "http_file")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
daml_deps()
|
|
|
|
|
|
|
2019-08-13 17:46:31 +03:00
|
|
|
|
load("@rules_haskell//haskell:repositories.bzl", "rules_haskell_dependencies")
|
2021-01-28 20:57:09 +03:00
|
|
|
|
load("@com_github_bazelbuild_remote_apis//:repository_rules.bzl", "switched_rules_by_language")
|
|
|
|
|
|
|
|
|
|
|
|
switched_rules_by_language(
|
|
|
|
|
|
name = "bazel_remote_apis_imports",
|
|
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-08-13 17:46:31 +03:00
|
|
|
|
rules_haskell_dependencies()
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2021-07-12 19:11:52 +03:00
|
|
|
|
load("@com_github_googleapis_googleapis//:repository_rules.bzl", "switched_rules_by_language")
|
|
|
|
|
|
|
|
|
|
|
|
switched_rules_by_language(
|
|
|
|
|
|
name = "com_google_googleapis_imports",
|
|
|
|
|
|
grpc = True,
|
|
|
|
|
|
java = True,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-05-27 20:44:34 +03:00
|
|
|
|
load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")
|
|
|
|
|
|
|
|
|
|
|
|
protobuf_deps()
|
|
|
|
|
|
|
2020-07-30 18:53:16 +03:00
|
|
|
|
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
|
|
|
|
|
|
|
|
|
|
|
|
rules_pkg_dependencies()
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
register_toolchains(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
"//:c2hs-toolchain",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-11-22 20:27:42 +03:00
|
|
|
|
load("//bazel_tools/dev_env_tool:dev_env_tool.bzl", "dadew", "dev_env_tool")
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
"@io_tweag_rules_nixpkgs//nixpkgs:nixpkgs.bzl",
|
2020-11-30 17:36:46 +03:00
|
|
|
|
"nixpkgs_cc_configure",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
"nixpkgs_local_repository",
|
|
|
|
|
|
"nixpkgs_package",
|
2020-04-23 18:30:32 +03:00
|
|
|
|
"nixpkgs_python_configure",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
2020-01-22 18:07:20 +03:00
|
|
|
|
load("//bazel_tools:create_workspace.bzl", "create_workspace")
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load("//bazel_tools:os_info.bzl", "os_info")
|
|
|
|
|
|
|
|
|
|
|
|
os_info(name = "os_info")
|
|
|
|
|
|
|
introduce new release process (#4513)
Context
=======
After multiple discussions about our current release schedule and
process, we've come to the conclusion that we need to be able to make a
distinction between technical snapshots and marketing releases. In other
words, we need to be able to create a bundle for early adopters to test
without making it an officially-supported version, and without
necessarily implying everyone should go through the trouble of
upgrading. The underlying goal is to have less frequent but more stable
"official" releases.
This PR is a proposal for a new release process designed under the
following constraints:
- Reuse as much as possible of the existing infrastructure, to minimize
effort but also chances of disruptions.
- Have the ability to create "snapshot"/"nightly"/... releases that are
not meant for general public consumption, but can still be used by savvy
users without jumping through too many extra hoops (ideally just
swapping in a slightly-weirder version string).
- Have the ability to promote an existing snapshot release to "official"
release status, with as few changes as possible in-between, so we can be
confident that the official release is what we tested as a prerelease.
- Have as much of the release pipeline shared between the two types of
releases, to avoid discovering non-transient problems while trying to
promote a snapshot to an official release.
- Triggerring a release should still be done through a PR, so we can
keep the same approval process for SOC2 auditability.
The gist of this proposal is to replace the current `VERSION` file with
a `LATEST` file, which would have the following format:
```
ef5d32b7438e481de0235c5538aedab419682388 0.13.53-alpha.20200214.3025.ef5d32b7
```
This file would be maintained with a script to reduce manual labor in
producing the version string. Other than that, the process will be
largely the same, with releases triggered by changes to this `LATEST`
and the release notes files.
Version numbers
===============
Because one of the goals is to reduce the velocity of our published
version numbers, we need a different version scheme for our snapshot
releases. Fortunately, most version schemes have some support for that;
unfortunately, the SDK sits at the intersection of three different
version schemes that have made incompatible choices. Without going into
too much detail:
- Semantic versioning (which we chose as the version format for the SDK
version number) allows for "prerelease" version numbers as well as
"metadata"; an example of a complete version string would be
`1.2.3-nightly.201+server12.43`. The "main" part of the version string
always has to have 3 numbers separated by dots; the "prerelease"
(after the `-` but before the `+`) and the "metadata" (after the `+`)
parts are optional and, if present, must consist of one or more segments
separated by dots, where a segment can be either a number or an
alphanumeric string. In terms of ordering, metadata is irrelevant and
any version with a prerelease string is before the corresponding "main"
version string alone. Amongst prereleases, segments are compared in
order with purely numeric ones compared as numbers and mixed ones
compared lexicographically. So 1.2.3 is more recent than 1.2.3-1,
which is itself less recent than 1.2.3-2.
- Maven version strings are any number of segments separated by a `.`, a
`-`, or a transition between a number and a letter. Version strings
are compared element-wise, with numeric segments being compared as
numbers. Alphabetic segments are treated specially if they happen to be
one of a handful of magic words (such as "alpha", "beta" or "snapshot"
for example) which count as "qualifiers"; a version string with a
qualifier is "before" its prefix (`1.2.3` is before `1.2.3-alpha.3`,
which is the same as `1.2.3-alpha3` or `1.2.3-alpha-3`), and there is a
special ordering amongst qualifiers. Other alphabetic segments are
compared alphabetically and count as being "after" their prefix
(`1.2.3-really-final-this-time` counts as being released after `1.2.3`).
- GHC package numbers are comprised of any number of numeric segments
separated by `.`, plus an optional (though deprecated) alphanumeric
"version tag" separated by a `-`. I could not find any official
documentation on ordering for the version tag; numeric segments are
compared as numbers.
- npm uses semantic versioning so that is covered already.
After much more investigation than I'd care to admit, I have come up
with the following compromise as the least-bad solution. First,
obviously, the version string for stable/marketing versions is going to
be "standard" semver, i.e. major.minor.patch, all numbers, which works,
and sorts as expected, for all three schemes. For snapshot releases, we
shall use the following (semver) format:
```
0.13.53-alpha.20200214.3025.ef5d32b7
```
where the components are, respectively:
- `0.13.53`: the expected version string of the next "stable" release.
- `alpha`: a marker that hopefully scares people enough.
- `20200214`: the date of the release commit, which _MUST_ be on
master.
- `3025`: the number of commits in master up to the release commit
(included). Because we have a linear, append-only master branch, this
uniquely identifies the commit.
- `ef5d32b7ù : the first 8 characters of the release commit sha. This is
not strictly speaking necessary, but makes it a lot more convenient to
identify the commit.
The main downsides of this format are:
1. It is not a valid format for GHC packages. We do not publish GHC
packages from the SDK (so far we have instead opted to release our
Haskell code as separate packages entirely), so this should not be an
issue. However, our SDK version currently leaks to `ghc-pkg` as the
version string for the stdlib (and prim) packages. This PR addresses
that by tweaking the compiler to remove the offending bits, so `ghc-pkg`
would see the above version number as `0.13.53.20200214.3025`, which
should be enough to uniquely identify it. Note that, as far as I could
find out, this number would never be exposed to users.
2. It is rather long, which I think is good from a human perspective as
it makes it more scary. However, I have been told that this may be
long enough to cause issues on Windows by pushing us past the max path
size limitation of that "OS". I suggest we try it and see what
happens.
The upsides are:
- It clearly indicates it is an unstable release (`alpha`).
- It clearly indicates how old it is, by including the date.
- To humans, it is immediately obvious which version is "later" even if
they have the same date, allowing us to release same-day patches if
needed. (Note: that is, commits that were made on the same day; the
release date itself is irrelevant here.)
- It contains the git sha so the commit built for that release is
immediately obvious.
- It sorts correctly under all schemes (modulo the modification for
GHC).
Alternatives I considered:
- Pander to GHC: 0.13.53-alpha-20200214-3025-ef5d32b7. This format would
be accepted by all schemes, but will not sort as expected under semantic
versioning (though Maven will be fine). I have no idea how it will sort
under GHC.
- Not having any non-numeric component, e.g. `0.13.53.20200214.3025`.
This is not valid semantic versioning and is therefore rejected by
npm.
- Not having detailed info: just go with `0.13.53-snapshot`. This is
what is generally done in the Java world, but we then lose track of what
version is actually in use and I'm concerned about bug reports. This
would also not let us publish to the main Maven repo (at least not more
than once), as artifacts there are supposed to be immutable.
- No having a qualifier: `0.13.53-3025` would be acceptable to all three
version formats. However, it would not clearly indicate to humans that
it is not meant as a stable version, and would sort differently under
semantic versioning (which counts it as a prerelease, i.e. before
`0.13.53`) than under maven (which counts it as a patch, so after
`0.13.53`).
- Just counting releases: `0.13.53-alpha.1`, where we just count the
number of prereleases in-between `0.13.52` and the next. This is
currently the fallback plan if Windows path length causes issues. It
would be less convenient to map releases to commits, but it could still
be done via querying the history of the `LATEST` file.
Release notes
=============
> Note: We have decided not to have release notes for snapshot releases.
Release notes are a bit tricky. Because we want the ability to make
snapshot releases, then later on promote them to stable releases, it
follows that we want to build commits from the past. However, if we
decide post-hoc that a commit is actually a good candidate for a
release, there is no way that commit can have the appropriate release
notes: it cannot know what version number it's getting, and, moreover,
we now track changes in commit messages. And I do not think anyone wants
to go back to the release notes file being a merge bottleneck.
But release notes need to be published to the releases blog upon
releasing a stable version, and the docs website needs to be updated and
include them.
The only sensible solution here is to pick up the release notes as of
the commit that triggers the release. As the docs cron runs
asynchronously, this means walking down the git history to find the
relevant commit.
> Note: We could probably do away with the asynchronicity at this point.
> It was originally included to cover for the possibility of a release
> failing. If we are releasing commits from the past after they have been
> tested, this should not be an issue anymore. If the docs generation were
> part of the synchronous release step, it would have direct access to the
> correct release notes without having to walk down the git history.
>
> However, I think it is more prudent to keep this change as a future step,
> after we're confident the new release scheme does indeed produce much more
> reliable "stable" releases.
New release process
===================
Just like releases are currently controlled mostly by detecting
changes to the `VERSION` file, the new process will be controlled by
detecting changes to the `LATEST` file. The format of that file will
include both the version string and the corresponding SHA.
Upon detecting a change to the `LATEST` file, CI will run the entire
release process, just like it does now with the VERSION file. The main
differences are:
1. Before running the release step, CI will checkout the commit
specified in the LATEST file. This requires separating the release
step from the build step, which in my opinion is cleaner anyway.
2. The `//:VERSION` Bazel target is replaced by a repository rule
that gets the version to build from an environment variable, with a
default of `0.0.0` to remain consistent with the current `daml-head`
behaviour.
Some of the manual steps will need to be skipped for a snapshot release.
See amended `release/RELEASE.md` in this commit for details.
The main caveat of this approach is that the official release will be a
different binary from the corresponding snapshot. It will have been
built from the same source, but with a different version string. This is
somewhat mitigated by Bazel caching, meaning any build step that does
not depend on the version string should use the cache and produce
identical results. I do not think this can be avoided when our artifact
includes its own version number.
I must note, though, that while going through the changes required after
removing the `VERSION` file, I have been quite surprised at the sheer number of
things that actually depend on the SDK version number. I believe we should
look into reducing that over time.
CHANGELOG_BEGIN
CHANGELOG_END
2020-02-25 19:01:23 +03:00
|
|
|
|
load("//bazel_tools:build_environment.bzl", "build_environment")
|
2020-01-21 17:41:40 +03:00
|
|
|
|
|
introduce new release process (#4513)
Context
=======
After multiple discussions about our current release schedule and
process, we've come to the conclusion that we need to be able to make a
distinction between technical snapshots and marketing releases. In other
words, we need to be able to create a bundle for early adopters to test
without making it an officially-supported version, and without
necessarily implying everyone should go through the trouble of
upgrading. The underlying goal is to have less frequent but more stable
"official" releases.
This PR is a proposal for a new release process designed under the
following constraints:
- Reuse as much as possible of the existing infrastructure, to minimize
effort but also chances of disruptions.
- Have the ability to create "snapshot"/"nightly"/... releases that are
not meant for general public consumption, but can still be used by savvy
users without jumping through too many extra hoops (ideally just
swapping in a slightly-weirder version string).
- Have the ability to promote an existing snapshot release to "official"
release status, with as few changes as possible in-between, so we can be
confident that the official release is what we tested as a prerelease.
- Have as much of the release pipeline shared between the two types of
releases, to avoid discovering non-transient problems while trying to
promote a snapshot to an official release.
- Triggerring a release should still be done through a PR, so we can
keep the same approval process for SOC2 auditability.
The gist of this proposal is to replace the current `VERSION` file with
a `LATEST` file, which would have the following format:
```
ef5d32b7438e481de0235c5538aedab419682388 0.13.53-alpha.20200214.3025.ef5d32b7
```
This file would be maintained with a script to reduce manual labor in
producing the version string. Other than that, the process will be
largely the same, with releases triggered by changes to this `LATEST`
and the release notes files.
Version numbers
===============
Because one of the goals is to reduce the velocity of our published
version numbers, we need a different version scheme for our snapshot
releases. Fortunately, most version schemes have some support for that;
unfortunately, the SDK sits at the intersection of three different
version schemes that have made incompatible choices. Without going into
too much detail:
- Semantic versioning (which we chose as the version format for the SDK
version number) allows for "prerelease" version numbers as well as
"metadata"; an example of a complete version string would be
`1.2.3-nightly.201+server12.43`. The "main" part of the version string
always has to have 3 numbers separated by dots; the "prerelease"
(after the `-` but before the `+`) and the "metadata" (after the `+`)
parts are optional and, if present, must consist of one or more segments
separated by dots, where a segment can be either a number or an
alphanumeric string. In terms of ordering, metadata is irrelevant and
any version with a prerelease string is before the corresponding "main"
version string alone. Amongst prereleases, segments are compared in
order with purely numeric ones compared as numbers and mixed ones
compared lexicographically. So 1.2.3 is more recent than 1.2.3-1,
which is itself less recent than 1.2.3-2.
- Maven version strings are any number of segments separated by a `.`, a
`-`, or a transition between a number and a letter. Version strings
are compared element-wise, with numeric segments being compared as
numbers. Alphabetic segments are treated specially if they happen to be
one of a handful of magic words (such as "alpha", "beta" or "snapshot"
for example) which count as "qualifiers"; a version string with a
qualifier is "before" its prefix (`1.2.3` is before `1.2.3-alpha.3`,
which is the same as `1.2.3-alpha3` or `1.2.3-alpha-3`), and there is a
special ordering amongst qualifiers. Other alphabetic segments are
compared alphabetically and count as being "after" their prefix
(`1.2.3-really-final-this-time` counts as being released after `1.2.3`).
- GHC package numbers are comprised of any number of numeric segments
separated by `.`, plus an optional (though deprecated) alphanumeric
"version tag" separated by a `-`. I could not find any official
documentation on ordering for the version tag; numeric segments are
compared as numbers.
- npm uses semantic versioning so that is covered already.
After much more investigation than I'd care to admit, I have come up
with the following compromise as the least-bad solution. First,
obviously, the version string for stable/marketing versions is going to
be "standard" semver, i.e. major.minor.patch, all numbers, which works,
and sorts as expected, for all three schemes. For snapshot releases, we
shall use the following (semver) format:
```
0.13.53-alpha.20200214.3025.ef5d32b7
```
where the components are, respectively:
- `0.13.53`: the expected version string of the next "stable" release.
- `alpha`: a marker that hopefully scares people enough.
- `20200214`: the date of the release commit, which _MUST_ be on
master.
- `3025`: the number of commits in master up to the release commit
(included). Because we have a linear, append-only master branch, this
uniquely identifies the commit.
- `ef5d32b7ù : the first 8 characters of the release commit sha. This is
not strictly speaking necessary, but makes it a lot more convenient to
identify the commit.
The main downsides of this format are:
1. It is not a valid format for GHC packages. We do not publish GHC
packages from the SDK (so far we have instead opted to release our
Haskell code as separate packages entirely), so this should not be an
issue. However, our SDK version currently leaks to `ghc-pkg` as the
version string for the stdlib (and prim) packages. This PR addresses
that by tweaking the compiler to remove the offending bits, so `ghc-pkg`
would see the above version number as `0.13.53.20200214.3025`, which
should be enough to uniquely identify it. Note that, as far as I could
find out, this number would never be exposed to users.
2. It is rather long, which I think is good from a human perspective as
it makes it more scary. However, I have been told that this may be
long enough to cause issues on Windows by pushing us past the max path
size limitation of that "OS". I suggest we try it and see what
happens.
The upsides are:
- It clearly indicates it is an unstable release (`alpha`).
- It clearly indicates how old it is, by including the date.
- To humans, it is immediately obvious which version is "later" even if
they have the same date, allowing us to release same-day patches if
needed. (Note: that is, commits that were made on the same day; the
release date itself is irrelevant here.)
- It contains the git sha so the commit built for that release is
immediately obvious.
- It sorts correctly under all schemes (modulo the modification for
GHC).
Alternatives I considered:
- Pander to GHC: 0.13.53-alpha-20200214-3025-ef5d32b7. This format would
be accepted by all schemes, but will not sort as expected under semantic
versioning (though Maven will be fine). I have no idea how it will sort
under GHC.
- Not having any non-numeric component, e.g. `0.13.53.20200214.3025`.
This is not valid semantic versioning and is therefore rejected by
npm.
- Not having detailed info: just go with `0.13.53-snapshot`. This is
what is generally done in the Java world, but we then lose track of what
version is actually in use and I'm concerned about bug reports. This
would also not let us publish to the main Maven repo (at least not more
than once), as artifacts there are supposed to be immutable.
- No having a qualifier: `0.13.53-3025` would be acceptable to all three
version formats. However, it would not clearly indicate to humans that
it is not meant as a stable version, and would sort differently under
semantic versioning (which counts it as a prerelease, i.e. before
`0.13.53`) than under maven (which counts it as a patch, so after
`0.13.53`).
- Just counting releases: `0.13.53-alpha.1`, where we just count the
number of prereleases in-between `0.13.52` and the next. This is
currently the fallback plan if Windows path length causes issues. It
would be less convenient to map releases to commits, but it could still
be done via querying the history of the `LATEST` file.
Release notes
=============
> Note: We have decided not to have release notes for snapshot releases.
Release notes are a bit tricky. Because we want the ability to make
snapshot releases, then later on promote them to stable releases, it
follows that we want to build commits from the past. However, if we
decide post-hoc that a commit is actually a good candidate for a
release, there is no way that commit can have the appropriate release
notes: it cannot know what version number it's getting, and, moreover,
we now track changes in commit messages. And I do not think anyone wants
to go back to the release notes file being a merge bottleneck.
But release notes need to be published to the releases blog upon
releasing a stable version, and the docs website needs to be updated and
include them.
The only sensible solution here is to pick up the release notes as of
the commit that triggers the release. As the docs cron runs
asynchronously, this means walking down the git history to find the
relevant commit.
> Note: We could probably do away with the asynchronicity at this point.
> It was originally included to cover for the possibility of a release
> failing. If we are releasing commits from the past after they have been
> tested, this should not be an issue anymore. If the docs generation were
> part of the synchronous release step, it would have direct access to the
> correct release notes without having to walk down the git history.
>
> However, I think it is more prudent to keep this change as a future step,
> after we're confident the new release scheme does indeed produce much more
> reliable "stable" releases.
New release process
===================
Just like releases are currently controlled mostly by detecting
changes to the `VERSION` file, the new process will be controlled by
detecting changes to the `LATEST` file. The format of that file will
include both the version string and the corresponding SHA.
Upon detecting a change to the `LATEST` file, CI will run the entire
release process, just like it does now with the VERSION file. The main
differences are:
1. Before running the release step, CI will checkout the commit
specified in the LATEST file. This requires separating the release
step from the build step, which in my opinion is cleaner anyway.
2. The `//:VERSION` Bazel target is replaced by a repository rule
that gets the version to build from an environment variable, with a
default of `0.0.0` to remain consistent with the current `daml-head`
behaviour.
Some of the manual steps will need to be skipped for a snapshot release.
See amended `release/RELEASE.md` in this commit for details.
The main caveat of this approach is that the official release will be a
different binary from the corresponding snapshot. It will have been
built from the same source, but with a different version string. This is
somewhat mitigated by Bazel caching, meaning any build step that does
not depend on the version string should use the cache and produce
identical results. I do not think this can be avoided when our artifact
includes its own version number.
I must note, though, that while going through the changes required after
removing the `VERSION` file, I have been quite surprised at the sheer number of
things that actually depend on the SDK version number. I believe we should
look into reducing that over time.
CHANGELOG_BEGIN
CHANGELOG_END
2020-02-25 19:01:23 +03:00
|
|
|
|
build_environment(name = "build_environment")
|
2020-01-21 17:41:40 +03:00
|
|
|
|
|
2021-04-27 14:50:39 +03:00
|
|
|
|
load("//bazel_tools:oracle.bzl", "oracle_configure")
|
|
|
|
|
|
|
|
|
|
|
|
oracle_configure(name = "oracle")
|
|
|
|
|
|
|
2021-03-30 14:02:18 +03:00
|
|
|
|
load("//bazel_tools:scala_version.bzl", "scala_version_configure")
|
2020-12-14 14:42:26 +03:00
|
|
|
|
|
2021-03-30 14:02:18 +03:00
|
|
|
|
scala_version_configure(name = "scala_version")
|
2020-12-14 14:42:26 +03:00
|
|
|
|
|
2021-05-27 16:41:28 +03:00
|
|
|
|
load(
|
|
|
|
|
|
"@scala_version//:index.bzl",
|
|
|
|
|
|
"scala_artifacts",
|
|
|
|
|
|
"scala_major_version",
|
|
|
|
|
|
"scala_major_version_suffix",
|
|
|
|
|
|
"scala_version",
|
|
|
|
|
|
)
|
2020-12-14 14:42:26 +03:00
|
|
|
|
|
2019-11-22 20:27:42 +03:00
|
|
|
|
dadew(name = "dadew")
|
|
|
|
|
|
|
2020-03-05 18:56:01 +03:00
|
|
|
|
load("@os_info//:os_info.bzl", "is_darwin", "is_linux", "is_windows")
|
2019-08-13 21:00:14 +03:00
|
|
|
|
load("//bazel_tools:ghc_dwarf.bzl", "ghc_dwarf")
|
|
|
|
|
|
|
|
|
|
|
|
ghc_dwarf(name = "ghc_dwarf")
|
|
|
|
|
|
|
|
|
|
|
|
load("@ghc_dwarf//:ghc_dwarf.bzl", "enable_ghc_dwarf")
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
2019-11-15 13:50:12 +03:00
|
|
|
|
# Configure msys2 POSIX toolchain provided by dadew.
|
|
|
|
|
|
load("//bazel_tools/dev_env_tool:dev_env_tool.bzl", "dadew_sh_posix_configure")
|
|
|
|
|
|
|
|
|
|
|
|
dadew_sh_posix_configure() if is_windows else None
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nixpkgs_local_repository(
|
|
|
|
|
|
name = "nixpkgs",
|
|
|
|
|
|
nix_file = "//nix:nixpkgs.nix",
|
|
|
|
|
|
nix_file_deps = [
|
2019-06-27 19:47:42 +03:00
|
|
|
|
"//nix:nixpkgs/default.nix",
|
|
|
|
|
|
"//nix:nixpkgs/default.src.json",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
],
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
dev_env_nix_repos = {
|
|
|
|
|
|
"nixpkgs": "@nixpkgs",
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
# Bazel cannot automatically determine which files a Nix target depends on.
|
|
|
|
|
|
# rules_nixpkgs offers the nix_file_deps attribute for that purpose. It should
|
|
|
|
|
|
# list all files that a target depends on. This allows Bazel to rebuild the
|
|
|
|
|
|
# target using Nix if any of these files has been changed. Omitting files from
|
|
|
|
|
|
# this list can cause subtle bugs or cache misses when Bazel loads an outdated
|
|
|
|
|
|
# store path. You can use the following command to determine what files a Nix
|
|
|
|
|
|
# target depends on. E.g. for tools.curl
|
|
|
|
|
|
#
|
|
|
|
|
|
# $ nix-build -vv -A tools.curl nix 2>&1 \
|
|
|
|
|
|
# | egrep '(evaluating file|copied source)' \
|
|
|
|
|
|
# | egrep -v '/nix/store'
|
|
|
|
|
|
#
|
|
|
|
|
|
# Unfortunately there is no mechanism to automatically keep this list up to
|
|
|
|
|
|
# date at the moment. See https://github.com/tweag/rules_nixpkgs/issues/74.
|
|
|
|
|
|
common_nix_file_deps = [
|
|
|
|
|
|
"//nix:bazel.nix",
|
|
|
|
|
|
"//nix:nixpkgs.nix",
|
2019-06-27 19:47:42 +03:00
|
|
|
|
"//nix:nixpkgs/default.nix",
|
|
|
|
|
|
"//nix:nixpkgs/default.src.json",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
|
|
# Use Nix provisioned cc toolchain
|
2020-11-30 17:36:46 +03:00
|
|
|
|
nixpkgs_cc_configure(
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel-cc-toolchain.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps + [
|
2019-05-08 11:57:28 +03:00
|
|
|
|
"//nix:tools/bazel-cc-toolchain/default.nix",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
],
|
2019-04-12 14:10:16 +03:00
|
|
|
|
repositories = dev_env_nix_repos,
|
2020-05-18 19:03:51 +03:00
|
|
|
|
) if not is_windows else None
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
2020-04-23 18:30:32 +03:00
|
|
|
|
nixpkgs_python_configure(repository = "@nixpkgs") if not is_windows else None
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# Curl system dependency
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "curl_nix",
|
|
|
|
|
|
attribute_path = "curl",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2021-09-07 16:41:43 +03:00
|
|
|
|
# Sysctl system dependency
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "sysctl_nix",
|
|
|
|
|
|
attribute_path = "sysctl",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-05-26 19:32:33 +03:00
|
|
|
|
# Toxiproxy dependency
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "toxiproxy_nix",
|
|
|
|
|
|
attribute_path = "toxiproxy",
|
2020-05-27 19:07:54 +03:00
|
|
|
|
fail_not_supported = False,
|
2020-05-26 19:32:33 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-05-27 19:07:54 +03:00
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "toxiproxy_dev_env",
|
|
|
|
|
|
nix_include = ["bin/toxiproxy-cmd"],
|
|
|
|
|
|
nix_label = "@toxiproxy_nix",
|
|
|
|
|
|
nix_paths = ["bin/toxiproxy-cmd"],
|
|
|
|
|
|
tools = ["toxiproxy"],
|
|
|
|
|
|
win_include = ["toxiproxy-server-windows-amd64.exe"],
|
|
|
|
|
|
win_paths = ["toxiproxy-server-windows-amd64.exe"],
|
|
|
|
|
|
win_tool = "toxiproxy",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# Patchelf system dependency
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "patchelf_nix",
|
|
|
|
|
|
attribute_path = "patchelf",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-11-13 19:27:28 +03:00
|
|
|
|
# netcat dependency
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "netcat_nix",
|
|
|
|
|
|
attribute_path = "netcat-gnu",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "netcat_dev_env",
|
|
|
|
|
|
nix_include = ["bin/nc"],
|
|
|
|
|
|
nix_label = "@netcat_nix",
|
|
|
|
|
|
nix_paths = ["bin/nc"],
|
|
|
|
|
|
tools = ["nc"],
|
|
|
|
|
|
win_include = ["usr/bin/nc.exe"],
|
|
|
|
|
|
win_paths = ["usr/bin/nc.exe"],
|
|
|
|
|
|
win_tool = "msys2",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-03-12 12:36:40 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "openssl_nix",
|
|
|
|
|
|
attribute_path = "openssl",
|
|
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "openssl_dev_env",
|
|
|
|
|
|
nix_include = ["bin/openssl"],
|
|
|
|
|
|
nix_label = "@openssl_nix",
|
|
|
|
|
|
nix_paths = ["bin/openssl"],
|
|
|
|
|
|
tools = ["openssl"],
|
2020-03-18 15:09:03 +03:00
|
|
|
|
win_include = [
|
|
|
|
|
|
"usr/bin",
|
|
|
|
|
|
"usr/ssl",
|
|
|
|
|
|
],
|
|
|
|
|
|
win_paths = ["usr/bin/openssl.exe"],
|
|
|
|
|
|
win_tool = "msys2",
|
2020-03-12 12:36:40 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# Tar & gzip dependency
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "tar_nix",
|
|
|
|
|
|
attribute_path = "gnutar",
|
|
|
|
|
|
fail_not_supported = False,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
dev_env_tool(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "tar_dev_env",
|
|
|
|
|
|
nix_include = ["bin/tar"],
|
|
|
|
|
|
nix_label = "@tar_nix",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nix_paths = ["bin/tar"],
|
|
|
|
|
|
tools = ["tar"],
|
2019-04-12 14:10:16 +03:00
|
|
|
|
win_include = ["usr/bin/tar.exe"],
|
2019-06-17 10:40:28 +03:00
|
|
|
|
win_paths = ["usr/bin/tar.exe"],
|
2019-05-10 13:41:11 +03:00
|
|
|
|
win_tool = "msys2",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "gzip_nix",
|
|
|
|
|
|
attribute_path = "gzip",
|
|
|
|
|
|
fail_not_supported = False,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
dev_env_tool(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "gzip_dev_env",
|
|
|
|
|
|
nix_include = ["bin/gzip"],
|
|
|
|
|
|
nix_label = "@gzip_nix",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nix_paths = ["bin/gzip"],
|
|
|
|
|
|
tools = ["gzip"],
|
2019-04-12 14:10:16 +03:00
|
|
|
|
win_include = ["usr/bin/gzip.exe"],
|
2019-06-17 10:40:28 +03:00
|
|
|
|
win_paths = ["usr/bin/gzip.exe"],
|
2019-05-10 13:41:11 +03:00
|
|
|
|
win_tool = "msys2",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2020-04-11 22:53:44 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "patch_nix",
|
|
|
|
|
|
attribute_path = "gnupatch",
|
|
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "patch_dev_env",
|
|
|
|
|
|
nix_include = ["bin/patch"],
|
|
|
|
|
|
nix_label = "@patch_nix",
|
|
|
|
|
|
nix_paths = ["bin/patch"],
|
|
|
|
|
|
tools = ["patch"],
|
|
|
|
|
|
win_include = ["usr/bin/patch.exe"],
|
|
|
|
|
|
win_paths = ["usr/bin/patch.exe"],
|
|
|
|
|
|
win_tool = "msys2",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-05-14 22:55:45 +03:00
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "mvn_dev_env",
|
|
|
|
|
|
nix_include = ["bin/mvn"],
|
|
|
|
|
|
nix_label = "@mvn_nix",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nix_paths = ["bin/mvn"],
|
|
|
|
|
|
tools = ["mvn"],
|
2019-05-14 22:55:45 +03:00
|
|
|
|
win_include = [
|
|
|
|
|
|
"bin",
|
|
|
|
|
|
"boot",
|
|
|
|
|
|
"conf",
|
|
|
|
|
|
"lib",
|
|
|
|
|
|
],
|
2019-06-17 10:40:28 +03:00
|
|
|
|
win_paths = ["bin/mvn"],
|
2019-05-14 22:55:45 +03:00
|
|
|
|
win_tool = "maven-3.6.1",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "awk_nix",
|
|
|
|
|
|
attribute_path = "gawk",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-11-13 19:27:28 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "coreutils_nix",
|
|
|
|
|
|
attribute_path = "coreutils",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "grpcurl_nix",
|
|
|
|
|
|
attribute_path = "grpcurl",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "hlint_nix",
|
|
|
|
|
|
attribute_path = "hlint",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
2021-02-08 14:12:07 +03:00
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "zip_nix",
|
|
|
|
|
|
attribute_path = "zip",
|
|
|
|
|
|
fail_not_supported = False,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-05-05 20:35:30 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "jekyll_nix",
|
|
|
|
|
|
attribute_path = "jekyll",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load(
|
2019-08-13 17:46:31 +03:00
|
|
|
|
"@rules_haskell//haskell:ghc_bindist.bzl",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
"haskell_register_ghc_bindists",
|
2019-04-16 12:37:07 +03:00
|
|
|
|
)
|
|
|
|
|
|
load(
|
2019-08-13 17:46:31 +03:00
|
|
|
|
"@rules_haskell//haskell:nixpkgs.bzl",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
"haskell_register_ghc_nixpkgs",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "glibc_locales",
|
|
|
|
|
|
attribute_path = "glibcLocales",
|
|
|
|
|
|
build_file_content = """
|
|
|
|
|
|
package(default_visibility = ["//visibility:public"])
|
|
|
|
|
|
filegroup(
|
|
|
|
|
|
name = "locale-archive",
|
|
|
|
|
|
srcs = ["lib/locale/locale-archive"],
|
|
|
|
|
|
)
|
|
|
|
|
|
""",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
) if is_linux else None
|
|
|
|
|
|
|
2019-04-25 14:10:28 +03:00
|
|
|
|
# This is used to get ghc-pkg on Linux.
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "ghc_nix",
|
2021-01-25 14:53:53 +03:00
|
|
|
|
attribute_path = "ghc",
|
2019-04-25 14:10:28 +03:00
|
|
|
|
build_file_content = """
|
|
|
|
|
|
package(default_visibility = ["//visibility:public"])
|
|
|
|
|
|
exports_files(glob(["lib/**/*"]))
|
|
|
|
|
|
""",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
2021-02-08 14:12:07 +03:00
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
2019-04-25 14:10:28 +03:00
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
) if not is_windows else None
|
|
|
|
|
|
|
2019-08-16 14:03:51 +03:00
|
|
|
|
common_ghc_flags = [
|
2019-08-19 18:10:30 +03:00
|
|
|
|
# We default to -c opt but we also want -O1 in -c dbg builds
|
|
|
|
|
|
# since we use them for profiling.
|
2019-08-16 14:03:51 +03:00
|
|
|
|
"-O1",
|
|
|
|
|
|
"-hide-package=ghc-boot-th",
|
|
|
|
|
|
"-hide-package=ghc-boot",
|
|
|
|
|
|
]
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# Used by Darwin and Linux
|
|
|
|
|
|
haskell_register_ghc_nixpkgs(
|
2021-01-25 14:53:53 +03:00
|
|
|
|
attribute_path = "ghcDwarf" if enable_ghc_dwarf else "ghc",
|
2019-05-20 15:20:34 +03:00
|
|
|
|
build_file = "@io_tweag_rules_nixpkgs//nixpkgs:BUILD.pkg",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
|
|
|
|
|
# -fexternal-dynamic-refs is required so that we produce position-independent
|
|
|
|
|
|
# relocations against some functions (-fPIC alone isn’t sufficient).
|
|
|
|
|
|
|
|
|
|
|
|
# -split-sections would allow us to produce significantly smaller binaries, e.g., for damlc,
|
|
|
|
|
|
# the binary shrinks from 186MB to 83MB. -split-sections only works on Linux but
|
|
|
|
|
|
# we get a similar behavior on Darwin by default.
|
|
|
|
|
|
# However, we had to disable split-sections for now as it seems to interact very badly
|
|
|
|
|
|
# with the GHCi linker to the point where :main takes several minutes rather than several seconds.
|
2019-08-16 14:03:51 +03:00
|
|
|
|
compiler_flags = common_ghc_flags + [
|
2019-04-12 14:10:16 +03:00
|
|
|
|
"-fexternal-dynamic-refs",
|
2020-03-05 18:56:01 +03:00
|
|
|
|
] + (["-g3"] if enable_ghc_dwarf else ([
|
|
|
|
|
|
"-optl-unexported_symbols_list=*",
|
2020-05-07 10:36:45 +03:00
|
|
|
|
"-optc-mmacosx-version-min=10.14",
|
|
|
|
|
|
"-opta-mmacosx-version-min=10.14",
|
|
|
|
|
|
"-optl-mmacosx-version-min=10.14",
|
2020-03-05 18:56:01 +03:00
|
|
|
|
] if is_darwin else ["-optl-s"])),
|
2019-07-02 15:51:09 +03:00
|
|
|
|
compiler_flags_select = {
|
|
|
|
|
|
"@com_github_digital_asset_daml//:profiling_build": ["-fprof-auto"],
|
|
|
|
|
|
"//conditions:default": [],
|
|
|
|
|
|
},
|
2019-04-12 14:10:16 +03:00
|
|
|
|
locale_archive = "@glibc_locales//:locale-archive",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
2021-02-08 14:12:07 +03:00
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
2019-04-12 14:10:16 +03:00
|
|
|
|
repl_ghci_args = [
|
|
|
|
|
|
"-O0",
|
|
|
|
|
|
"-fexternal-interpreter",
|
2019-05-01 11:24:45 +03:00
|
|
|
|
"-Wwarn",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
],
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2021-03-26 23:26:40 +03:00
|
|
|
|
version = "8.10.4",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# Used by Windows
|
|
|
|
|
|
haskell_register_ghc_bindists(
|
2019-08-16 14:03:51 +03:00
|
|
|
|
compiler_flags = common_ghc_flags,
|
2021-03-26 23:26:40 +03:00
|
|
|
|
version = "8.10.4",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
) if is_windows else None
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "jq",
|
|
|
|
|
|
attribute_path = "jq",
|
2019-05-22 23:31:04 +03:00
|
|
|
|
fail_not_supported = False,
|
2019-04-12 14:10:16 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-05-22 23:31:04 +03:00
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "jq_dev_env",
|
|
|
|
|
|
nix_include = ["bin/jq"],
|
|
|
|
|
|
nix_label = "@jq",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nix_paths = ["bin/jq"],
|
|
|
|
|
|
tools = ["jq"],
|
2019-05-28 16:45:38 +03:00
|
|
|
|
win_include = ["mingw64/bin"],
|
|
|
|
|
|
win_include_as = {"mingw64/bin": "bin"},
|
2019-06-17 10:40:28 +03:00
|
|
|
|
win_paths = ["bin/jq.exe"],
|
2019-05-28 16:45:38 +03:00
|
|
|
|
win_tool = "msys2",
|
2019-05-22 23:31:04 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-15 18:53:05 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "mvn_nix",
|
|
|
|
|
|
attribute_path = "mvn",
|
2019-05-14 22:55:45 +03:00
|
|
|
|
fail_not_supported = False,
|
2019-04-15 18:53:05 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
#node & npm
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "node_nix",
|
2020-01-21 19:38:11 +03:00
|
|
|
|
attribute_path = "nodejsNested",
|
|
|
|
|
|
build_file_content = 'exports_files(glob(["node_nix/**"]))',
|
2019-04-12 14:10:16 +03:00
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
#sass
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "sass_nix",
|
|
|
|
|
|
attribute_path = "sass",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
2019-11-20 17:27:32 +03:00
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
2019-04-12 14:10:16 +03:00
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
#tex
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "texlive_nix",
|
|
|
|
|
|
attribute_path = "texlive",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
#sphinx
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "sphinx_nix",
|
2020-06-29 13:34:40 +03:00
|
|
|
|
attribute_path = "sphinx183-exts",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
2019-10-14 10:35:18 +03:00
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
2019-04-12 14:10:16 +03:00
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
#Imagemagick
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "imagemagick_nix",
|
|
|
|
|
|
attribute_path = "imagemagick",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
#Javadoc
|
|
|
|
|
|
nixpkgs_package(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "jdk_nix",
|
|
|
|
|
|
attribute_path = "jdk8",
|
|
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2021-04-08 11:42:40 +03:00
|
|
|
|
# To run canton
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "jdk11_nix",
|
|
|
|
|
|
attribute_path = "jdk11",
|
|
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-29 11:16:11 +03:00
|
|
|
|
# This only makes sense on Windows so we just put dummy values in the nix fields.
|
|
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "makensis_dev_env",
|
|
|
|
|
|
nix_include = [""],
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nix_paths = ["bin/makensis.exe"],
|
|
|
|
|
|
tools = ["makensis"],
|
2019-04-29 11:16:11 +03:00
|
|
|
|
win_include = [
|
|
|
|
|
|
"bin",
|
|
|
|
|
|
"contrib",
|
|
|
|
|
|
"include",
|
|
|
|
|
|
"plugins",
|
|
|
|
|
|
"stubs",
|
|
|
|
|
|
],
|
2019-06-17 10:40:28 +03:00
|
|
|
|
win_paths = ["bin/makensis.exe"],
|
2019-04-29 11:16:11 +03:00
|
|
|
|
win_tool = "nsis-3.04",
|
|
|
|
|
|
) if is_windows else None
|
|
|
|
|
|
|
2019-05-27 13:59:19 +03:00
|
|
|
|
# Scaladoc
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "scala_nix",
|
2021-02-16 12:39:16 +03:00
|
|
|
|
attribute_path = "scala_{}".format(scala_major_version_suffix),
|
2019-05-27 13:59:19 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# Dummy target //external:python_headers.
|
|
|
|
|
|
# To avoid query errors due to com_google_protobuf.
|
|
|
|
|
|
# See https://github.com/protocolbuffers/protobuf/blob/d9ccd0c0e6bbda9bf4476088eeb46b02d7dcd327/util/python/BUILD
|
|
|
|
|
|
bind(
|
|
|
|
|
|
name = "python_headers",
|
|
|
|
|
|
actual = "@com_google_protobuf//util/python:python_headers",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-09-27 17:26:20 +03:00
|
|
|
|
http_archive(
|
|
|
|
|
|
name = "static_asset_d3plus",
|
|
|
|
|
|
build_file_content = 'exports_files(["js/d3.min.js", "js/d3plus.min.js"])',
|
|
|
|
|
|
sha256 = "7d31a500a4850364a966ac938eea7f2fa5ce1334966b52729079490636e7049a",
|
|
|
|
|
|
strip_prefix = "d3plus.v1.9.8",
|
|
|
|
|
|
type = "zip",
|
|
|
|
|
|
urls = ["https://github.com/alexandersimoes/d3plus/releases/download/v1.9.8/d3plus.zip"],
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-11-22 17:24:08 +03:00
|
|
|
|
load("//:bazel-haskell-deps.bzl", "daml_haskell_deps")
|
2019-09-11 09:57:48 +03:00
|
|
|
|
|
2019-11-22 17:24:08 +03:00
|
|
|
|
daml_haskell_deps()
|
2019-11-15 13:50:12 +03:00
|
|
|
|
|
2020-01-06 13:24:15 +03:00
|
|
|
|
load("@rules_haskell//tools:repositories.bzl", "rules_haskell_worker_dependencies")
|
|
|
|
|
|
|
|
|
|
|
|
# We don't use the worker mode, but this is required for bazel query to function.
|
|
|
|
|
|
# Call this after `daml_haskell_deps` to ensure that the right `stack` is used.
|
|
|
|
|
|
rules_haskell_worker_dependencies()
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load("//bazel_tools:java.bzl", "java_home_runtime")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
java_home_runtime(name = "java_home")
|
|
|
|
|
|
|
|
|
|
|
|
# rules_go used here to compile a wrapper around the protoc-gen-scala plugin
|
|
|
|
|
|
load("@io_bazel_rules_go//go:deps.bzl", "go_register_toolchains", "go_rules_dependencies")
|
|
|
|
|
|
|
|
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "go_nix",
|
|
|
|
|
|
attribute_path = "go",
|
|
|
|
|
|
build_file_content = """
|
|
|
|
|
|
filegroup(
|
|
|
|
|
|
name = "sdk",
|
|
|
|
|
|
srcs = glob(["share/go/**"]),
|
|
|
|
|
|
visibility = ["//visibility:public"],
|
|
|
|
|
|
)
|
|
|
|
|
|
""",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# A repository that generates the Go SDK imports, see
|
|
|
|
|
|
# ./bazel_tools/go_sdk/README.md
|
|
|
|
|
|
local_repository(
|
|
|
|
|
|
name = "go_sdk_repo",
|
|
|
|
|
|
path = "bazel_tools/go_sdk",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
load("@io_bazel_rules_go//go:deps.bzl", "go_wrap_sdk")
|
|
|
|
|
|
|
|
|
|
|
|
# On Nix platforms we use the Nix provided Go SDK, on Windows we let Bazel pull
|
|
|
|
|
|
# an upstream one.
|
|
|
|
|
|
go_wrap_sdk(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "go_sdk",
|
2019-05-07 14:55:30 +03:00
|
|
|
|
root_file = "@go_nix//:share/go/ROOT",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
) if not is_windows else None
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
|
|
|
|
|
go_rules_dependencies()
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
go_register_toolchains()
|
|
|
|
|
|
|
|
|
|
|
|
load("@bazel_gazelle//:deps.bzl", "gazelle_dependencies", "go_repository")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
gazelle_dependencies()
|
|
|
|
|
|
|
|
|
|
|
|
# protoc-gen-doc repo
|
|
|
|
|
|
go_repository(
|
|
|
|
|
|
name = "com_github_pseudomuto_protoc_gen_doc",
|
|
|
|
|
|
commit = "0c4d666cfe1175663cf067963396a0b9b34f543f",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
importpath = "github.com/pseudomuto/protoc-gen-doc",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# protokit repo
|
|
|
|
|
|
go_repository(
|
|
|
|
|
|
name = "com_github_pseudomuto_protokit",
|
|
|
|
|
|
commit = "7037620bf27b13fcdc10b1b17ddef82540db670b",
|
2019-04-12 14:10:16 +03:00
|
|
|
|
importpath = "github.com/pseudomuto/protokit",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-10-28 15:53:14 +03:00
|
|
|
|
load("//:bazel-java-deps.bzl", "install_java_deps")
|
|
|
|
|
|
|
|
|
|
|
|
install_java_deps()
|
|
|
|
|
|
|
|
|
|
|
|
load("@maven//:defs.bzl", "pinned_maven_install")
|
|
|
|
|
|
|
|
|
|
|
|
pinned_maven_install()
|
|
|
|
|
|
|
2020-12-08 08:59:23 +03:00
|
|
|
|
load("@io_bazel_rules_scala//:scala_config.bzl", "scala_config")
|
|
|
|
|
|
|
2020-12-14 14:42:26 +03:00
|
|
|
|
scala_config(scala_version)
|
2020-12-08 08:59:23 +03:00
|
|
|
|
|
2021-05-27 16:41:28 +03:00
|
|
|
|
load("@io_bazel_rules_scala//scala:scala.bzl", "scala_repositories")
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
2020-09-23 18:13:06 +03:00
|
|
|
|
scala_repositories(
|
2020-12-08 16:52:41 +03:00
|
|
|
|
fetch_sources = True,
|
2021-04-26 20:49:43 +03:00
|
|
|
|
overriden_artifacts = scala_artifacts,
|
2020-09-23 18:13:06 +03:00
|
|
|
|
)
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
|
|
|
|
|
load("@io_bazel_rules_scala//scala:toolchains.bzl", "scala_register_toolchains")
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
scala_register_toolchains()
|
|
|
|
|
|
|
2020-12-08 08:59:23 +03:00
|
|
|
|
load("@io_bazel_rules_scala//testing:scalatest.bzl", "scalatest_repositories", "scalatest_toolchain")
|
|
|
|
|
|
|
|
|
|
|
|
scalatest_repositories()
|
|
|
|
|
|
|
|
|
|
|
|
scalatest_toolchain()
|
|
|
|
|
|
|
2021-05-27 16:41:28 +03:00
|
|
|
|
load("//bazel_tools:scalapb.bzl", "scalapb_version")
|
|
|
|
|
|
|
|
|
|
|
|
http_archive(
|
|
|
|
|
|
name = "scalapb",
|
|
|
|
|
|
build_file_content = """
|
|
|
|
|
|
proto_library(
|
|
|
|
|
|
name = "scalapb_proto",
|
|
|
|
|
|
srcs = ["protobuf/scalapb/scalapb.proto"],
|
|
|
|
|
|
strip_import_prefix = "protobuf/",
|
|
|
|
|
|
deps = [
|
|
|
|
|
|
"@com_google_protobuf//:descriptor_proto",
|
|
|
|
|
|
],
|
|
|
|
|
|
visibility = ["//visibility:public"],
|
|
|
|
|
|
)
|
|
|
|
|
|
""",
|
|
|
|
|
|
sha256 = "a5395d89ad804e2bec21ed3b61e5ccd44dc48d69a660f62244c6b15d095b5ca0",
|
|
|
|
|
|
strip_prefix = "ScalaPB-{}".format(scalapb_version),
|
|
|
|
|
|
urls = ["https://github.com/scalapb/ScalaPB/archive/refs/tags/v{}.zip".format(scalapb_version)],
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
load("@io_bazel_rules_scala//jmh:jmh.bzl", "jmh_repositories")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
jmh_repositories()
|
|
|
|
|
|
|
2020-01-21 19:38:11 +03:00
|
|
|
|
# TODO (aherrmann) This wrapper is only used on Windows.
|
|
|
|
|
|
# Replace by an appropriate Windows only `dadew_tool` call.
|
2019-11-08 11:40:26 +03:00
|
|
|
|
dev_env_tool(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "nodejs_dev_env",
|
2019-11-08 11:40:26 +03:00
|
|
|
|
nix_include = [
|
|
|
|
|
|
"bin",
|
|
|
|
|
|
"include",
|
|
|
|
|
|
"lib",
|
|
|
|
|
|
"share",
|
|
|
|
|
|
],
|
2019-04-12 14:10:16 +03:00
|
|
|
|
nix_label = "@node_nix",
|
2019-11-08 11:40:26 +03:00
|
|
|
|
nix_paths = [],
|
|
|
|
|
|
prefix = "nodejs_dev_env",
|
|
|
|
|
|
tools = [],
|
|
|
|
|
|
win_include = [
|
|
|
|
|
|
".",
|
|
|
|
|
|
],
|
|
|
|
|
|
win_paths = [],
|
2020-05-28 22:58:52 +03:00
|
|
|
|
win_tool = "nodejs-12.17.0",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# Setup the Node.js toolchain
|
2020-01-16 17:55:32 +03:00
|
|
|
|
load("@build_bazel_rules_nodejs//:index.bzl", "node_repositories", "yarn_install")
|
2019-04-04 11:33:38 +03:00
|
|
|
|
|
|
|
|
|
|
node_repositories(
|
|
|
|
|
|
package_json = ["//:package.json"],
|
2020-01-21 19:38:11 +03:00
|
|
|
|
# Using `dev_env_tool` introduces an additional layer of symlink
|
|
|
|
|
|
# indirection. Bazel doesn't track dependencies through symbolic links.
|
|
|
|
|
|
# Occasionally, this can cause build failures on CI if a build is not
|
|
|
|
|
|
# invalidated despite a change of an original source. To avoid such issues
|
|
|
|
|
|
# we use the `nixpkgs_package` directly.
|
|
|
|
|
|
vendored_node = "@nodejs_dev_env" if is_windows else "@node_nix",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
yarn_install(
|
|
|
|
|
|
name = "npm",
|
2020-01-22 19:28:14 +03:00
|
|
|
|
args = ["--frozen-lockfile"],
|
2019-04-04 11:33:38 +03:00
|
|
|
|
package_json = "//:package.json",
|
|
|
|
|
|
yarn_lock = "//:yarn.lock",
|
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# TODO use fine-grained managed dependency
|
|
|
|
|
|
yarn_install(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "daml_extension_deps",
|
2020-01-22 19:28:14 +03:00
|
|
|
|
args = ["--frozen-lockfile"],
|
2019-07-08 12:40:48 +03:00
|
|
|
|
package_json = "//compiler/daml-extension:package.json",
|
|
|
|
|
|
yarn_lock = "//compiler/daml-extension:yarn.lock",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
# TODO use fine-grained managed dependency
|
|
|
|
|
|
yarn_install(
|
2019-04-12 14:10:16 +03:00
|
|
|
|
name = "navigator_frontend_deps",
|
2020-01-22 19:28:14 +03:00
|
|
|
|
args = ["--frozen-lockfile"],
|
2019-04-12 14:10:16 +03:00
|
|
|
|
package_json = "//navigator/frontend:package.json",
|
|
|
|
|
|
yarn_lock = "//navigator/frontend:yarn.lock",
|
2019-04-04 11:33:38 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2020-01-22 19:19:45 +03:00
|
|
|
|
# We’ve had a bunch of problems with typescript rules on Windows.
|
|
|
|
|
|
# Therefore we’ve disabled them completely for now.
|
|
|
|
|
|
# Since we need to @load stuff in @language_support_ts_deps
|
|
|
|
|
|
# and load statements can’t be conditional, we create a dummy
|
|
|
|
|
|
# workspace on Windows.
|
|
|
|
|
|
# See #4162 for more details.
|
2020-01-20 18:02:33 +03:00
|
|
|
|
yarn_install(
|
|
|
|
|
|
name = "language_support_ts_deps",
|
2020-01-22 19:28:14 +03:00
|
|
|
|
args = ["--frozen-lockfile"],
|
2020-01-22 00:23:51 +03:00
|
|
|
|
package_json = "//language-support/ts/packages:package.json",
|
|
|
|
|
|
yarn_lock = "//language-support/ts/packages:yarn.lock",
|
2020-01-22 18:07:20 +03:00
|
|
|
|
) if not is_windows else create_workspace(
|
|
|
|
|
|
name = "language_support_ts_deps",
|
|
|
|
|
|
files = {
|
|
|
|
|
|
"eslint/BUILD.bazel": 'exports_files(["index.bzl"])',
|
|
|
|
|
|
"eslint/index.bzl": "def eslint_test(*args, **kwargs):\n pass",
|
|
|
|
|
|
"jest-cli/BUILD.bazel": 'exports_files(["index.bzl"])',
|
|
|
|
|
|
"jest-cli/index.bzl": "def jest_test(*args, **kwargs):\n pass",
|
2020-12-09 13:45:35 +03:00
|
|
|
|
"@bazel/typescript/BUILD.bazel": 'exports_files(["index.bzl"])',
|
|
|
|
|
|
"@bazel/typescript/index.bzl": "def ts_project(*args, **kwargs):\n pass",
|
2020-01-22 18:07:20 +03:00
|
|
|
|
},
|
2020-01-20 18:02:33 +03:00
|
|
|
|
)
|
|
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
# We usually use the _deploy_jar target to produce self-contained jars, but here we're using jar_jar because the size
|
|
|
|
|
|
# of codegen tool is substantially reduced (as shown below) and that the presence of JVM internal com.sun classes could
|
|
|
|
|
|
# theoretically stop the codegen running against JVMs other the OpenJDK 8 (the current JVM used for building).
|
|
|
|
|
|
load("@com_github_johnynek_bazel_jar_jar//:jar_jar.bzl", "jar_jar_repositories")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
jar_jar_repositories()
|
|
|
|
|
|
|
|
|
|
|
|
# The following is advertised by rules_proto, but we define our own dependencies
|
|
|
|
|
|
# in dependencies.yaml. So all we need to do is replicate the binds here
|
|
|
|
|
|
# https://github.com/stackb/rules_proto/tree/master/java#java_grpc_library
|
|
|
|
|
|
|
|
|
|
|
|
# load("@io_grpc_grpc_java//:repositories.bzl", "grpc_java_repositories")
|
|
|
|
|
|
# grpc_java_repositories()
|
|
|
|
|
|
|
|
|
|
|
|
# Load the grpc deps last, since it won't try to load already loaded
|
|
|
|
|
|
# dependencies.
|
|
|
|
|
|
load("@com_github_grpc_grpc//bazel:grpc_deps.bzl", "grpc_deps")
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-04-04 11:33:38 +03:00
|
|
|
|
grpc_deps()
|
2019-04-12 14:10:16 +03:00
|
|
|
|
|
2019-08-26 17:00:41 +03:00
|
|
|
|
load("@upb//bazel:workspace_deps.bzl", "upb_deps")
|
|
|
|
|
|
|
|
|
|
|
|
upb_deps()
|
|
|
|
|
|
|
|
|
|
|
|
load("@build_bazel_rules_apple//apple:repositories.bzl", "apple_rules_dependencies")
|
|
|
|
|
|
|
|
|
|
|
|
apple_rules_dependencies()
|
|
|
|
|
|
|
2019-04-12 14:10:16 +03:00
|
|
|
|
load("@com_github_bazelbuild_buildtools//buildifier:deps.bzl", "buildifier_dependencies")
|
|
|
|
|
|
|
|
|
|
|
|
buildifier_dependencies()
|
2019-06-17 10:40:28 +03:00
|
|
|
|
|
2021-10-12 14:43:20 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "grpc_nix",
|
|
|
|
|
|
attribute_path = "grpc",
|
|
|
|
|
|
build_file_content = """
|
|
|
|
|
|
load("@os_info//:os_info.bzl", "is_linux")
|
|
|
|
|
|
cc_library(
|
|
|
|
|
|
name = "grpc_lib",
|
|
|
|
|
|
srcs = [":lib/libgrpc.so", ":lib/libgrpc.so.18", ":lib/libgrpc.so.18.0.0", ":lib/libgpr.so", ":lib/libgpr.so.18", ":lib/libgpr.so.18.0.0"] if is_linux else [":lib/libgrpc.dylib", ":lib/libgpr.dylib"],
|
|
|
|
|
|
visibility = ["//visibility:public"],
|
|
|
|
|
|
hdrs = [":include"],
|
|
|
|
|
|
includes = ["include"],
|
|
|
|
|
|
)
|
|
|
|
|
|
filegroup(
|
|
|
|
|
|
name = "grpc_file",
|
|
|
|
|
|
srcs = glob(["lib/*"]),
|
|
|
|
|
|
visibility = ["//visibility:public"],
|
|
|
|
|
|
)
|
|
|
|
|
|
""",
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2019-06-17 10:40:28 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "postgresql_nix",
|
2019-10-14 10:35:18 +03:00
|
|
|
|
attribute_path = "postgresql_9_6",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
)
|
|
|
|
|
|
|
2020-05-20 09:08:18 +03:00
|
|
|
|
nixpkgs_package(
|
|
|
|
|
|
name = "z3_nix",
|
|
|
|
|
|
attribute_path = "z3",
|
|
|
|
|
|
fail_not_supported = False,
|
|
|
|
|
|
nix_file = "//nix:bazel.nix",
|
|
|
|
|
|
nix_file_deps = common_nix_file_deps,
|
|
|
|
|
|
repositories = dev_env_nix_repos,
|
|
|
|
|
|
) if not is_windows else None
|
|
|
|
|
|
|
2019-06-17 10:40:28 +03:00
|
|
|
|
dev_env_tool(
|
|
|
|
|
|
name = "postgresql_dev_env",
|
|
|
|
|
|
nix_include = [
|
|
|
|
|
|
"bin",
|
|
|
|
|
|
"include",
|
|
|
|
|
|
"lib",
|
|
|
|
|
|
"share",
|
|
|
|
|
|
],
|
|
|
|
|
|
nix_label = "@postgresql_nix",
|
|
|
|
|
|
nix_paths = [
|
|
|
|
|
|
"bin/createdb",
|
2020-05-08 15:36:42 +03:00
|
|
|
|
"bin/dropdb",
|
|
|
|
|
|
"bin/initdb",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
"bin/pg_ctl",
|
2019-06-27 19:47:42 +03:00
|
|
|
|
"bin/postgres",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
],
|
2020-05-14 10:06:34 +03:00
|
|
|
|
required_tools = {
|
|
|
|
|
|
"initdb": ["postgres"],
|
|
|
|
|
|
"pg_ctl": ["postgres"],
|
|
|
|
|
|
},
|
2019-06-17 10:40:28 +03:00
|
|
|
|
tools = [
|
|
|
|
|
|
"createdb",
|
2020-05-08 15:36:42 +03:00
|
|
|
|
"dropdb",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
"initdb",
|
|
|
|
|
|
"pg_ctl",
|
2020-05-08 15:36:42 +03:00
|
|
|
|
"postgres",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
],
|
|
|
|
|
|
win_include = [
|
|
|
|
|
|
"mingw64/bin",
|
|
|
|
|
|
"mingw64/include",
|
|
|
|
|
|
"mingw64/lib",
|
|
|
|
|
|
"mingw64/share",
|
|
|
|
|
|
],
|
|
|
|
|
|
win_include_as = {
|
|
|
|
|
|
"mingw64/bin": "bin",
|
|
|
|
|
|
"mingw64/include": "include",
|
|
|
|
|
|
"mingw64/lib": "lib",
|
|
|
|
|
|
"mingw64/share": "share",
|
|
|
|
|
|
},
|
|
|
|
|
|
win_paths = [
|
|
|
|
|
|
"bin/createdb.exe",
|
2020-05-08 15:36:42 +03:00
|
|
|
|
"bin/dropdb.exe",
|
|
|
|
|
|
"bin/initdb.exe",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
"bin/pg_ctl.exe",
|
2019-11-08 11:40:26 +03:00
|
|
|
|
"bin/postgres.exe",
|
2019-06-17 10:40:28 +03:00
|
|
|
|
],
|
|
|
|
|
|
win_tool = "msys2",
|
|
|
|
|
|
)
|
