p. Each target group could be treated sort of like a conditional
PHONY that would run if any of the group's members were out-of-date.
What do you think?
-Nick
--
Nicholas Clark
Email: nicholas.cl...@gmail.com
___
Help-make mailing list
Help-make@gnu.
> echo "$@";
>
> # eg: section/section1/group1/step3/do_step
> section/%/step3/do_step: \
> section/%/step2/do_step \
>
> echo "$@";
>
> # eg: section/section1/group1/group_end
> section/%/group_end: \
> section/%/step3/do_step \
>
> echo "$@";
>
> # eg: section/section1/section_end
> section/%/section_end: \
> section/%/group2/group_end \
>
> echo "$@";
>
>
>
> ___
> Help-make mailing list
> Help-make@gnu.org
> https://lists.gnu.org/mailman/listinfo/help-make
>
--
Nicholas Clark
Email: nicholas.cl...@gmail.com
___
Help-make mailing list
Help-make@gnu.org
https://lists.gnu.org/mailman/listinfo/help-make
ithin a recipe, because recipes are
> passed to the shell and run there. If you want to set a make variable
> you have to do it outside of a recipe, using make's shell function:
>
> ESTK := $(shell python estimationkmer.py $(G_SIZE))
>
> Quake:
>
Hi Gorlash,
On the subject of your "syntax error near unexpected token `('" errors,
have you tried putting your parentheses arguments in quotes?
Instead of this:
lint: $(SOURCE_FILES)
$(LINT_TOOL) +v -width(160,4) +fcp -ic:\lint9 mingw.lnt -os(_lint.tmp)
$(SOURCE_FILES)
Try this:
lint:
So I was reading through the (excellent) documentation for GNU Make, and I
noticed something that might be a bug - or maybe misleading?
The Makefile Conventions section has this page on 'variables for
installation directories' (
https://www.gnu.org/software/make/manual/html_node/Directory-Variable
I'd describe OOPs as "just like a regular dependency, except that the
timestamp isn't checked. Only whether it exists on the filesystem."
On Sun, Nov 3, 2019 at 7:51 AM Robert P. J. Day
wrote:
>
> was asked on friday by a make newbie to explain order-only
> prerequisite (OOP), as he was readin
As a user, I just wanted to say congrats and thanks to the GNU Make team
for 4.3!
I'm very excited about the new grouped-target and EXTRA_PREREQS features.
Those are both going to be very useful. Good work folks.
-Nick
On Sun, Jan 19, 2020 at 3:46 PM Paul Smith wrote:
> --
Hmm, I don't read that as acting like a double-colon rule.
Instead, GNU Make does this:
1. You asked for a.o and b.o.
2. The Makefile has a rule that makes %.o from %.c, and one that makes %.o
from %.d
3. GNU Make looks for a.c and finds it, then uses recipe #1 for a.o.
4. GNU Make looks for b.c
Hi all,
I was experimenting with Make today, and I noticed a possible bug in Make's
target-specific variable handling.
>From the GNU Make manual (
https://www.gnu.org/software/make/manual/html_node/Target_002dspecific.html#Target_002dspecific),
I'd expect that I could combine "export" and "privat
I think it's a great change. I'd love for Make to understand trailing
slashes intelligently, and I think it makes sense as a default.
Are we concerned enough about compatibility breaks that it would make sense
to enable it via special-target (a-la delete-on-error)?
On Fri, Oct 8, 2021, 10:36 Paul
10 matches
Mail list logo
