From 9cf3d4acbf0171d2de1d5d6d0158add0e09c5fa4 Mon Sep 17 00:00:00 2001 From: Matt McCormick Date: Sat, 16 Jul 2016 17:12:52 -0400 Subject: [PATCH] doc: Identify how to start up a shell in the build environment --- README.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.rst b/README.rst index ce6ee45..0e74b27 100644 --- a/README.rst +++ b/README.rst @@ -194,7 +194,10 @@ Examples 1. **dockcross make**: Build the Makefile in the current directory. 2. **dockcross cmake -Bbuild -H. -GNinja***: Run CMake with a build directory "build" for the CMakeLists.txt in the current directory and generate `ninja` files. 3. **dockcross ninja -Cbuild**: Run ninja in the generated build directory. -4. **dockcross bash -c 'find . -name \*.o | sort > objects.txt'**. +4. **dockcross bash -c '$CC test/C/hello.c -o hello'** Build the hello.c file + with the compiler identified with the `CC` environmental variable in the + build environment. +5. **dockcross bash**. Run a shell in the build environment. Note that commands are executed verbatim. If any shell processing for environment variable expansion or redirection is required, please use