summaryrefslogtreecommitdiff
path: root/libc/ci/docker/wasm32-unknown-emscripten/Dockerfile
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-06 14:17:31 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-06 14:17:31 -0800
commit47ac62fa4b70b2172b9f279d3bd41b6a8709a5a4 (patch)
tree4e251adcd193a626dd4c8e6f5449c8ea8ee61584 /libc/ci/docker/wasm32-unknown-emscripten/Dockerfile
parentd080927468c7e0e0d03e08ceb01fdab85c3ba9fd (diff)
downloadnitrocli-47ac62fa4b70b2172b9f279d3bd41b6a8709a5a4.tar.gz
nitrocli-47ac62fa4b70b2172b9f279d3bd41b6a8709a5a4.tar.bz2
Use [patch] section to control local crate replacements
The nitrokey-sys crate poses a challenge in that upgrading it causes build errors caused by linking against the system's nitrokey library from multiple crates, which is not allowed. The exact cause of the problem is unclear but the suspicion is that a bug in Cargo's replacing logic is the cause of the issue. To work around this problem, this change switches to using the [patch] section for replacing crates with local copies instead of the [replace] one.
Diffstat (limited to 'libc/ci/docker/wasm32-unknown-emscripten/Dockerfile')
0 files changed, 0 insertions, 0 deletions