Hi Paul,
On 3/11/23 15:20, Paul Smith wrote:
> On Sat, 2023-03-11 at 01:54 +0100, Alejandro Colomar wrote:
>> Let's say I have a build tree that has directories which are created
>> during build. The build system has some linters in a `lint` target,
>> which touches files when it succeeds. When
On Sat, 2023-03-11 at 01:54 +0100, Alejandro Colomar wrote:
> Let's say I have a build tree that has directories which are created
> during build. The build system has some linters in a `lint` target,
> which touches files when it succeeds. When I want to lint only a
> specific file, it's interes
Hi Dmitry,
On 3/11/23 14:36, Dmitry Goncharov wrote:
> On Fri, Mar 10, 2023 at 7:55 PM Alejandro Colomar
> wrote:
>> How about using `mkdir -p` instead of touch(1) for nonexistent files?
>
> mkdir -p would create a directory where a file is supposed to be.
> Let's say you have hello.c, but no he
On Fri, Mar 10, 2023 at 7:55 PM Alejandro Colomar
wrote:
> How about using `mkdir -p` instead of touch(1) for nonexistent files?
mkdir -p would create a directory where a file is supposed to be.
Let's say you have hello.c, but no hello.o.If you run make -t it'll
create an empty hello.o. Then you
Hi!
Let's say I have a build tree that has directories which are created
during build. The build system has some linters in a `lint` target,
which touches files when it succeeds. When I want to lint only a
specific file, it's interesting to convince make(1) to touch all files,
and then touch the
