docs/cookbook/redoconf-simple: a simple redoconf C++ project.

This is a little simpler than the docs/cookbook/c project, which
doesn't actually have a doc yet because there was too much to explain.
I think I might make that a follow-on cookbook chapter, for people who
have read this simple one.

I think this doc is maybe a little too long; I intended it to be
"here's what you do to get started" but it turned into "here's what you
do to get started, and why it works, in excruciating detail." Not quite
sure how to fix.

(Also updated some other parts of the docs to refer to redoconf as a
real thing now instead of a "maybe someone should write this" thing.)
This commit is contained in:
Avery Pennarun 2019-03-05 23:33:11 -05:00
commit e24e045a07
26 changed files with 1025 additions and 46 deletions

View file

@ -1,13 +1,17 @@
# Is redo compatible with autoconf?
Yes. You don't have to do anything special, other than the above note about
declaring dependencies on config.h, which is no worse than what you would
have to do with make.
Yes. You don't have to do anything special, other than making sure you
`redo-ifchange config.h` (where `config.h` is generated by autoconf) in
whatever redo script you use to compile your object files. This
is about the same as what you would have to do with make.
# Is redo compatible with automake?
Hells no. You can thank me later. But see next question.
Not exactly; there is no point in generating Makefiles if you aren't going
to use make. However, we now include a similar project,
[redoconf](/cookbook/redoconf-simple/), which provides a lot of the same
features in a redo project that automake provides for a make project.
# Is redo compatible with make?
@ -22,7 +26,7 @@ In a file called myproject.stamp.do:
make -C myproject all
So, to amend our answer to the previous question, you *can* use
automake-generated Makefiles as part of your redo-based project.
automake-generated Makefiles as part of your hybrid redo/make-based project.
# Is redo -j compatible with make -j?