[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re:
From: |
Budi |
Subject: |
Re: |
Date: |
Wed, 17 Jun 2020 07:34:20 +0700 |
like was said
How can we have make's 'include' command in makefile not to precede
the first/default target in the actual processes in
https://github.com/mcostalba/Stockfish/blob/master/src/Makefile
the famous chess engine
it'll include what make's 'include' is given always at the earliest
I need Help target must be earlier than it if Help is really intended
i.e. by default behavior; the first target of others must be the
first processs, in here case is simply if user type "make"
On 6/17/20, Kaz Kylheku (gmake) <729-670-0061@kylheku.com> wrote:
> On 2020-06-15 16:53, Budi wrote:
>> How can we have make's 'include' command in makefile not to precede
>> the first/default target in the actual processes?
>> I found it always processed the earliest, how to solve this?
>
> E.g. in Vi type "dd" on the include line, move the cursor somewhere
> below the first target/rule, then paste with "p". :)
>
> include directives can appear anywhere in the Makefile (except, of
> course,
> in the middle of syntax that would break due to their presence).
>
> A rule can refer to variables that are defined later, possibly via
> inclusion:
>
> $ cat Makefile
> .PHONY: foo
> foo: $(OBJS)
> echo update $(OBJS)
>
> OBJS = a b c # this could come from an include!
>
> $ make
> echo update a b c
> update a b c
>
>
- [no subject], Budi, 2020/06/15
- Re:, Budi, 2020/06/15
- Re:, Philip Guenther, 2020/06/15
- Re:, Budi, 2020/06/16
- Re:, David Deutsch, 2020/06/16
- Re:, Kaz Kylheku (gmake), 2020/06/16
- Re:,
Budi <=
- Re:, Kaz Kylheku (gmake), 2020/06/16