docs: n3xx: Add link to README for building custom filesystems

1 files changed, 1 insertions, 37 deletions

diff --git a/host/docs/usrp_n3xx.dox b/host/docs/usrp_n3xx.dox
index 5630cff40..6ffe2be62 100644
--- a/host/docs/usrp_n3xx.dox
+++ b/host/docs/usrp_n3xx.dox
@@ -742,43 +742,7 @@ Note that building SD cards is very disk space and RAM intensive.
 \subsection n3xx_fsbuild_docker Using Docker to build filesystems
 
 Ettus Research provides a Docker containers to facilitate building filesystems.
-Using Docker hub, the container can be downloaded by running
-
-    $ docker pull ettusresearch/oe-build
-
-Then, navigate to a location with enough disk space:
-
-    $ cd $BUILDDIR
-
-Create a world-writable directory called 'build':
-
-    $ mkdir build && chmod 777 build
-
-Then run the Docker container:
-
-    $ docker run -i -t -v $(pwd)/build:/home/oe-builder/build:rw,z ettusresearch/oe-build /bin/bash
-
-Note the order of the naming above might vary by docker version, sometimes it might need to be:
-
-    $ docker run -i -t ettusresearch/oe-build -v $(pwd)/build:/home/oe-builder/build:rw,z /bin/bash
-
-After running the previous command, you will be inside the container. First,
-configure your build environment:
-
-    $ TEMPLATECONF=$(pwd)/meta-ettus/conf/sulfur source ./oe-core/oe-init-build-env ./build ./bitbake
-
-Then, you can invoke bitbake to build the image:
-
-    $ bitbake $image_name
-
-where `$image_name` could be `developer-image` or `deployment-image`. If you
-want to build the SDK, append `-cpopulate_sdk` to the above line.
-
-If you keep the build directory, bitbake will reuse it on consecutive runs,
-which will speed up builds significantly between runs.
-
-This step will build the SDK, the SD card image, and the Mender artefact.
-
+Refer to the <a href="https://github.com/EttusResearch/ettus-docker/blob/master/oe-build/README.md"> README </a> for more details.
 
 \section n3xx_software_dev Modifying and compiling UHD and MPM for the N3XX