Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Ninja: Use binary dir for `$subdir/all` targets | Alexis Murzeau | 2016-10-24 | 1 | -0/+1 |
| | | | | | | | | | | The targets added by commit v3.6.0-rc1~240^2~2 (Ninja: Add `$subdir/all` targets, 2016-03-11) use as `$subdir` the relative path from the top of the source tree to the current source directory. This is not correct when using `add_subdirectory(test test_bin)`. Instead we need to use the relative path from the top of the binary tree to the current binary directory as was done for related targets by commit v3.7.0-rc1~268^2 (Ninja: Add `$subdir/{test,install,package}` targets, 2016-08-05). | ||||
* | Ninja: Add `$subdir/{test,install,package}` targets | Brad King | 2016-08-09 | 1 | -0/+5 |
| | | | | | | | | | | | | | With the Makefile generator one can use `cd $subdir; make install` to build and install targets associated with a given subdirectory. This is not possible to do with the Ninja generator since there is only one `build.ninja` file at the top of the build tree. However, we can approximate it by allowing one to run `ninja $subdir/install` at the top of the tree to build the targets in the corresponding subdirectory and install them. This also makes sense for `test`, `package`, and other GLOBAL_TARGET targets. It was already done for `all` by commit v3.6.0-rc1~240^2~2 (Ninja: Add `$subdir/all` targets, 2016-03-11). | ||||
* | Ninja: Add test for `$subdir/all` targets | Brad King | 2016-03-22 | 1 | -0/+2 |