Hi,
On Tue, Jun 07, 2022 at 03:21:49PM +0200, David Demelier wrote:
> -include ${DEPS}
...
> And you're done. On a fresh directory the -include ${DEPS} will
> silently fail and rebuild everything. Then .d files will be generated
> and touching any file will rebuild exactly what should be.
>
> The
On Mon, 2022-06-06 at 15:13 +0200, Georg Lehner wrote:
> Hi,
>
> The topic of header dependency tracking is already addressed since
> the
> inception of redo by DJB.
About C header dependencies, you can actually do it using POSIX Make
(in the next version, the -include statement is not available
Hi,
The topic of header dependency tracking is already addressed since the
inception of redo by DJB.
The Appenwarr documentation offers a fairly simple answer in the form of
an "implicit" .do file for object files.
---
cat > default.o.do <2. build the object file and generate a make-style
*** Thomas Oltmann [2021-09-07 23:15]:
>Nevertheless, these are some of the reasons I care about redo, in no
>particular order: [...]
Good points I support too! Also:
* The whole redo build system description/rules fits on single screen,
like here: http://www.goredo.cypherpunks.ru/Usage-rules.h
*** Thomas Oltmann [2021-09-07 22:57]:
>For example, it is also able to properly recognize: [...]
I see, thanks!
However personally in C-projects I use https://include-what-you-use.org/
and h-extract.pl script to make depends only on local headers:
whatever.do:
[...]
redo-ifc
Dear Ben,
I believe Sergey Matveev here is much more of an expert on this matter
than I am,
seeing how he has even developed his own high-performance implementation.
Nevertheless, these are some of the reasons I care about redo, in no
particular order:
- It does not suffer from the same obvious
Dear Sergey,
Thank you for your reply!
Am Di., 7. Sept. 2021 um 21:39 Uhr schrieb Sergey Matveev
:
> Just out of curiosity, why POSIX shell abilities are not enough for that task?
>
> read D < "$2".d
> redo-ifchange ${D#* }
>
> POSIX "read" out-of-box understands \-newlines that can appea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What's wrong with plain old make? I don't think there's a need to write
more build tools when one is already enough; if we keep writing build
tools we'll end up with tools like autoconf.
Ben Raskin
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQSVj5
Greetings!
*** Thomas Oltmann [2021-09-07 19:50]:
>This tool is able to parse the dependency-only Makefiles that modern C
>compilers can
>produce during compilation, and feed these dependencies into redo (via
>'redo-ifchange').
Just out of curiosity, why POSIX shell abilities are not enough for t
Hi everybody!
redo is a pretty well-designed family of build-systems
that enjoys a certain popularity among people on this mailing list.
Its recursive nature makes it well-suited to projects comprising a
large amount of files.
However, unlike comparable build-systems like make or tup, it lacks pr
10 matches
Mail list logo
