[ovs-dev] [PATCH] INSTALL: Describe how to use a separate build directory.

Ben Pfaff blp at nicira.com
Fri May 9 15:05:59 UTC 2014


CC: YAMAMOTO Takashi <yamamoto at valinux.co.jp>
CC: Andy Zhou <azhou at nicira.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>
---
 INSTALL | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/INSTALL b/INSTALL
index afefb51..5c869b2 100644
--- a/INSTALL
+++ b/INSTALL
@@ -149,9 +149,8 @@ Prerequisites section, follow the procedure below to build.
 
       % ./boot.sh
 
-2. In the top source directory, configure the package by running the
-   configure script.  You can usually invoke configure without any
-   arguments:
+2. Configure the package by running the configure script.  You can
+   usually invoke configure without any arguments.  For example:
 
       % ./configure
 
@@ -203,7 +202,16 @@ Prerequisites section, follow the procedure below to build.
    additional environment variables.  For a full list, invoke
    configure with the --help option.
 
-3. Run GNU make in the top source directory, e.g.:
+   You can also run configure from a separate build directory.  This
+   is helpful if you want to build Open vSwitch in more than one way
+   from a single source directory, e.g. to try out both GCC and Clang
+   builds, or to build kernel modules for more than one Linux version.
+   Here is an example:
+
+      % mkdir _gcc && (cd _gcc && ../configure CC=gcc)
+      % mkdir _clang && (cd _clang && ../configure CC=clang)
+
+3. Run GNU make in the build directory, e.g.:
 
       % make
 
@@ -211,6 +219,12 @@ Prerequisites section, follow the procedure below to build.
 
       % gmake
 
+   If you used a separate build directory, run make or gmake from that
+   directory, e.g.:
+
+      % make -C _gcc
+      % make -C _clang
+
    For improved warnings if you installed "sparse" (see
    "Prerequisites"), add C=1 to the command line.
 
-- 
1.9.1




More information about the dev mailing list