From 086180812c10b3425b6957061cc7385cb26a0f15 Mon Sep 17 00:00:00 2001 From: Sebastien Bourdeauducq Date: Wed, 8 May 2019 15:04:38 +0800 Subject: [PATCH] manual: update link to nix-scripts repository. Closes #1314 --- doc/manual/developing.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/developing.rst b/doc/manual/developing.rst index eb64ab6b6..83019ac95 100644 --- a/doc/manual/developing.rst +++ b/doc/manual/developing.rst @@ -9,7 +9,7 @@ ARTIQ itself does not depend on Nix, and it is also possible to compile everythi * Install the `Nix package manager `_ and Git (e.g. ``$ nix-shell -p git``). * Set up the M-Labs Hydra channels (:ref:`same procedure as the user section `) to allow binaries to be downloaded. Otherwise, tools such as LLVM and the Rust compiler will be compiled on your machine, which uses a lot of CPU time, memory, and disk space. Simply setting up the channels is sufficient, Nix will automatically detect when a binary can be downloaded instead of being compiled locally. -* Clone the repositories https://github.com/m-labs/artiq and https://github.com/m-labs/nix-scripts. +* Clone the repositories https://github.com/m-labs/artiq and https://git.m-labs.hk/m-labs/nix-scripts. * Run ``$ nix-shell -I artiqSrc=path_to_artiq_sources shell-dev.nix`` to obtain an environment containing all the required development tools (e.g. Migen, MiSoC, Clang, Rust, OpenOCD...) in addition to the ARTIQ user environment. ``artiqSrc`` should point to the root of the cloned ``artiq`` repository, and ``shell-dev.nix`` can be found in the ``artiq`` folder of the ``nix-scripts`` repository. * This enters a FHS chroot environment that simplifies the installation and patching of Xilinx Vivado. * Download Vivado from Xilinx and install it (by running the official installer in the FHS chroot environment). If you do not want to write to ``/opt``, you can install it in a folder of your home directory. The "appropriate" Vivado version to use for building the bitstream can vary. Some versions contain bugs that lead to hidden or visible failures, others work fine. Refer to the `M-Labs Hydra logs `_ to determine which version is currently used when building the binary packages.