Closed elfring closed 9 years ago
make itself does not know about out-of-source builds. This is a product of autotools and its associated tooling.
As far as I know rake supports out-of-source builds just as well as make. If you try it and have difficulties please open new issues.
How can the corresponding output directory be configured for an out-of-source build with Rake?
The answer as always is "it depends". What are you building? Are you using a C toolchain? There's a few things to do, e.g. make sure the command lines for the tools all explicitly set the output filename.
Check out gaudi if you want to see something built on rake that does exactly what you're asking for for C/C++ toolchains. (disclosure: gaudi is my own construct so I'm biased)
Which variable (or Ruby class) does manage the output directory for an out-of-source build with the Rake software?
Which out-of-the-box tasks are you using? What does your build look like? There isn't some magic setting or variable to set to make build artefacts land somewhere, you have to code this in your tasks.
I would expect that there is a default output directory managed from the specification of a variable like VPATH
(or PATH_OUT
for example).
How would this configuration detail work together with the Rake build system?
How do you think about to benefit from parallel build trees also for your software? Would you like to support out-of-source (VPATH) builds?