summaryrefslogtreecommitdiffstats
path: root/README.rst
diff options
context:
space:
mode:
authorPierre Rossi <pierre.rossi@digia.com>2013-05-24 17:20:33 +0200
committerSimon Hausmann <simon.hausmann@digia.com>2013-05-31 10:55:53 +0200
commitc5a19a2599298da6c1fc3d3602a1d9ef787704c6 (patch)
treec938646373944999522889e63794808ef2c4ab6c /README.rst
parent252c0e77614b8f2bfb2a4cb12287453df6653ffc (diff)
Ease the switching between Debug and Release builds
Change the semantics of getOutDir, introduce getConfigDir. Rely on Gyp's configurations mechanism to get a sensible path for the BLINQ_PROCESS_PATH in both cases. Also make the build smarter in that re-generation of gyp files will lead to re-gyping.
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.rst b/README.rst
index 7f255880a..ce627e880 100644
--- a/README.rst
+++ b/README.rst
@@ -21,8 +21,8 @@ This is a prototype of allowing embedding Chromium/Blink into Qt.
* set the CHROMIUM_SRC_DIR environment variable to point to /path/to/src/
* Simply run qmake in the top-level directory (it will call ninja behind the scenes).
Use qmake -r to forcefully re-gyp (without relying on make to determine if it's necessary).
- * switching between a debug and a release build can still be a bit cumbersome, for now it seems:
- rm **/Makefile && qmake -r CONFIG+=<debug or release> depending on what's needed should work well
+ * Release or debug builds can be obtained by running 'make release' or 'make debug' in the
+ top level directory (only lib and process for now, and not so smart with dependencies)
(4) build with make ;)