Re: Making makefiles with primarily phony targets more friendly

2022-08-10 Thread Alejandro Colomar
Hi, On 8/10/22 22:19, Jean-Baptiste Poittevin wrote: By using a lot of PHONY targets, I think you're closing a door to one make greatest feature : not redoing those things that are already up to date. If you consider that every rule can generate a useful file (file containing container

Re: Making makefiles with primarily phony targets more friendly

2022-08-10 Thread Britton Kerin
On Wed, Aug 10, 2022 at 12:33 PM Jean-Baptiste Poittevin wrote: > > By using a lot of PHONY targets, I think you're closing a door to one make > greatest feature : not redoing those things that are already up to date. > > If you consider that every rule can generate a useful file (file

Re: Making makefiles with primarily phony targets more friendly

2022-08-10 Thread Jean-Baptiste Poittevin
By using a lot of PHONY targets, I think you're closing a door to one make greatest feature : not redoing those things that are already up to date. If you consider that every rule can generate a useful file (file containing container image for example) or a dummy file, you can benefit from the

Fwd: Making makefiles with primarily phony targets more friendly

2022-08-10 Thread Britton Kerin
-- Forwarded message - From: Britton Kerin Date: Wed, Aug 10, 2022, 11:58 AM Subject: Re: Making makefiles with primarily phony targets more friendly To: Katherine Pata On Wed, Aug 10, 2022, 11:44 AM Katherine Pata wrote: > I often find myself using makefiles to handle

Making makefiles with primarily phony targets more friendly

2022-08-10 Thread Katherine Pata
I often find myself using makefiles to handle things like project linting, container images, various scripts, initiating tests, and other misc tasks. Sometimes these include tasks that have real dependencies that make should keep track of, but often the vast majority of targets are phony.

Re: Implicit rule for linking multiple object files

2022-08-10 Thread Paul Smith
On Thu, 2022-08-11 at 01:58 +0800, ljh wrote: > I have three c source files: x.c, y.c, z.c and I name x as the target > on left. Can I put x.o in the prerequisites on the right too? Are > they the same, with or without x.o in the prerequisites on the right? >     >     x: y.o z.o x.o  # with x.o

Implicit rule for linking multiple object files

2022-08-10 Thread ljh
Hello list, GNU Make Manual / 10.2 / Linking a single object file, mentions this: x: y.o z.o I have three c source files: x.c, y.c, z.c and I name x as the target on left. Can I put x.o in the prerequisites on the right too? Are they the same, with or without x.o in the prerequisites on

Re: The order of compiling multiple c++ source files

2022-08-10 Thread ljh
Thanks Paul, I have another quetion. Please help me. On section 10.2 of the manual: ` x: y.o z.o ` Can I put x.o on the prerequisites on the right part? ` x: y.o z.o x.o` # with x.o Are they the same? --- The section 10.2 inspired me to write my little minimal general Makefile

[bug #57242] Non-recursive command passes invalid jobserver file descriptors

2022-08-10 Thread Martin Liška
Follow-up Comment #15, bug #57242 (project make): Note the FIFO support has been added to the current GCC master. May I please ask about the next Make release, is it planned any time soon? ___ Reply to this item at: