Using CMake to build, rather than calling 'make' directly.

This should improve cross-platform support.
micadam · Sep 25, 2015 · 4439d1a · 4439d1a
1 parent 84de0e7
commit 4439d1a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -16,11 +16,9 @@ do so. Run `python setup.py build` to build, and `python setup.py install` to in
 Alternatively, if you want an in-place build that puts the compiled library right in
 the current directory, run `python setup.py build_ext --inplace'
 
-Only tested with Python 2.7 and 3.4 on Ubuntu Linux. At the moment, the setup.py script
-uses a Linux/Unix-specific method to build the RVO2 library itself, before building the
-Python wrappers.
-
-If you have success (or failure) stories, please share them!
+Only tested with Python 2.7 and 3.4 on Ubuntu Linux. The setup.py script uses CMake to build
+the RVO2 library itself, before building the Python wrappers. If you have success (or failure)
+stories, please share them!
 
 
 Differences with the C++ version

diff --git a/setup.py b/setup.py
@@ -17,7 +17,7 @@ def run(self):
             os.makedirs(build_dir)
             subprocess.check_call(['cmake', '../..', '-DCMAKE_CXX_FLAGS=-fPIC'],
                                   cwd=build_dir)
-        subprocess.check_call(['make', '-j8'], cwd=build_dir)
+        subprocess.check_call(['cmake', '--build', '.'], cwd=build_dir)
 
         _build_ext.run(self)