Hi everybody,
I've put together a somewhat extensive build system on top of make which
relies heavily on generating and including Makefiles (partly to avoid
The Dreaded Recursive Make). The centerpiece is a complement to %-rules
where I have blueprints for certain filetypes that I match against a
ake behavior to make something like this happen? Note
that a complicating factor is that I sometimes have make blueprints that
span several targets (because I sometimes have to not just find a
recipe, but that could itself require additional prerequisites).
Best regards,
David
On 10/16/19 2:18 PM,
resolve.
Any pointers on the add-on question would be very much appreciated.
best regards,
David
On 10/16/19 3:27 PM, David Deutsch wrote:
> Hi Paul,
>
> Thank you for getting back to me (and thank you so much for all your work!).
>
> Race Condition - That was poorly worded on m
Hi Paul,
On 10/21/19 7:29 AM, Paul Smith wrote:
> I can only assume that the rules in question are pattern rules. If
> they were explicit rules then make would indeed give you a more clear
> declaration of which file is missing.
Actually, I'm quite sure that they are explicit rules. I will try t
seems to me like that is
only for adding functions, not adding to core behavior like pattern rules, or
am I missing something there?
best regards,
David
Am 21. Oktober 2019 14:36:04 MESZ schrieb Paul Smith :
>On Mon, 2019-10-21 at 07:51 +0200, David Deutsch wrote:
>> On 10/21/19 7:29
On 05.11.19 04:51, Kaz Kylheku (gmake) wrote:
> Why would we make a directory order-only? Because it's not a
> real input to the build.
That has always been the crux for me about understanding order-only
prerequisites: - It's an OOP if the prerequisite is not directly /used/
in the recipe for the
As a rule of thumb: Anything that you indent (the "recipe") as part of a
target is going to be executed in the shell.
What you did in your example is like typing "include makefile_a" in your
terminal, which fails as bash doesn't know what to do with it.
Conversely, "include" is a make directive t
essed
> ?
>
> On 6/18/20, Budi wrote:
>> How do we have 'make' to echo just like Bash but is done in place of
>> prerequisite so it must be really 'make' command not shell
>>
>> On 6/17/20, Budi wrote:
>>> David Deutsch, you are BRILLIAN
Hey everybody,
I use make to build a document tree, again and again, when prerequisites
change.
I observe outside change events and use inotify on some files and when a
change has occurred, I re-run make. So my problem is not detecting the
change - I already know when a change has occurred and wh
Hey everybody,
I've been looking through the mailing list trying to come up with an
answer to how I could do .NOT_PARALLEL for some targets but not others.
There hasn't been a solution thus far and it has been mentioned that
implementing it in make itself might be highly non-trivial. I think that
Perhaps this is a FORCE prerequisite:
https://www.gnu.org/software/make/manual/html_node/Force-Targets.html
On 17/11/2020 11:49, Budi wrote:
> I found in a Makefile the default target:
>
> all: all-yes
>
> but the text editor search won't find all-yes except in .PHONY
> How is it explained ?
>
Hi there,
I hope I'm not breaking any etiquette rules with this, but I was
interested in seeing how GPT4 would respond to this request, so here goes:
https://chat.openai.com/share/5eb73ccc-27f6-4d79-934b-add344ab41f6
Content:
Sure, let's try to clarify the aspects of pattern rules and
match
Hi there,
I hope I'm not breaking any etiquette rules with this, but I was
interested in seeing how GPT4 would respond to this request, so here goes:
https://chat.openai.com/share/72ec8309-6a66-45fc-b142-7fdc9cbb57b4
Content:
In GNU Make, a simple way to include all subdirectory makefiles in
t; a good community, but
perhaps they could be helpful in aiding those who are still around with
the workload of keeping it alive?
-David
On 30.05.23 14:20, Paul Smith wrote:
On Mon, 2023-05-29 at 06:06 +0200, David Deutsch wrote:
I hope I'm not breaking any etiquette rules with this, bu
14 matches
Mail list logo
