daml/.dadew

{
    "version": "0.0.8",
    "manifests": "dev-env\\windows\\manifests",
    "tools": [
        "7zip",
        "java-openjdk-8u201",
        "msys2",
        "curl-7.65.3",
        "cacert",
        "vcredist-14.24.28127.4",
        "bazel",
        "nodejs-10.16.3",
        "python-3.8.2",
        "nsis-3.04",
        "maven-3.6.1",
        "stack"
    ]
}
open-sourcing daml 2019-04-04 11:33:38 +03:00			`{`
			`"version": "0.0.8",`
			`"manifests": "dev-env\\windows\\manifests",`
			`"tools": [`
			`"7zip",`
			`"java-openjdk-8u201",`
windows: use msys2 provided patch - fixes: #916 (#942) 2019-05-10 13:41:11 +03:00			`"msys2",`
Fix curl on Windows (#2643) The old URL has gone away. The definition is taken from upstream. 2019-08-23 10:48:48 +03:00			`"curl-7.65.3",`
open-sourcing daml 2019-04-04 11:33:38 +03:00			`"cacert",`
patching Bazel on Windows (infra bits, no patch yet) (#5918) patch Bazel on Windows (ci setup) We have a weird, intermittent bug on Windows where Bazel gets into a broken state. To investigate, we need to patch Bazel to add more debug output than present in the official distribution. This PR adds the basic infrastructure we need to download the Bazel source code, apply a patch, compile it, and make that binary available to the rest of the build. This is for Windows only as we already have the ability to do similar things on Linux and macOS through Nix. This PR does not contain any intresting patch to Bazel, just the minimum that we can check we are actually using the patched version. CHANGELOG_BEGIN CHANGELOG_END 2020-05-13 00:16:04 +03:00			`"vcredist-14.24.28127.4",`
open-sourcing daml 2019-04-04 11:33:38 +03:00			`"bazel",`
Upgrade to nodejs-10.16.3 on Windows (#3529) This matches the version we use on Linux. 2019-11-19 18:08:39 +03:00			`"nodejs-10.16.3",`
Fix Windows CI (#5648) The python install step started failing because there is a new pip release so we get a warning. I tried to just upgrade python but the new python manifest depends on functions that need an upgrade of scoop so I upgraded that as well. Not quite sure which of those upgrades fixes the issue … changelog_begin changelog_end 2020-04-21 16:31:57 +03:00			`"python-3.8.2",`
Fix SDK integration tests on Windows (#1125) * Fix SDK integration tests on Windows * Switch to Haskell-based tar extraction 2019-05-14 22:55:45 +03:00			`"nsis-3.04",`
Manually run stack update (#3590) * Add stack to dev-env * Manually run stack update before build To work around multiple concurrent attempts to take the hackage-security-lock. 2019-11-22 18:16:48 +03:00			`"maven-3.6.1",`
			`"stack"`
open-sourcing daml 2019-04-04 11:33:38 +03:00			`]`
			`}`