Re: Conditional broken line in recipe

On 2023-09-03 14:38, Paul Smith wrote: > On Sun, 2023-09-03 at 13:14 +0200, Alejandro Colomar wrote: >>> You need to put the ifdef outside the recipe: >> >> That would hurt readability a little bit. > > IMO a make preprocessor statement inside a recipe is a

Re: Conditional broken line in recipe

Hi Paul, On 2023-09-03 04:09, Paul Smith wrote: > On Sun, 2023-09-03 at 01:03 +0200, Alejandro Colomar wrote: >> I was also wondering... is ONESHELL significant for performance?  >> Does the reduction in number of shells speed up things? > > It might increase performance but

Re: Conditional broken line in recipe

Hi Paul, On 2023-09-03 04:06, Paul Smith wrote: > On Sun, 2023-09-03 at 01:00 +0200, Alejandro Colomar wrote: >> Is something like this possible? >> >> target: >> foo \ >> ifeq (...) >> | bar \ >> endif >> | baz >

Re: Conditional broken line in recipe

On 2023-09-03 14:57, Alejandro Colomar wrote: > On 2023-09-03 14:38, Paul Smith wrote: >> On Sun, 2023-09-03 at 13:14 +0200, Alejandro Colomar wrote: >>>> You need to put the ifdef outside the recipe: >>> >>> That would hurt readability a little bit. >>

Re: Conditional broken line in recipe

On 2023-09-03 13:11, Alejandro Colomar wrote: > Hi Paul, > > On 2023-09-03 04:09, Paul Smith wrote: >> On Sun, 2023-09-03 at 01:03 +0200, Alejandro Colomar wrote: >>> I was also wondering... is ONESHELL significant for performance?  >>> Does the reduction in

Re: Conditional broken line in recipe

On 2023-09-03 01:00, Alejandro Colomar wrote: > Hi! > > Is something like this possible? > > target: > foo \ > ifeq (...) > | bar \ > endif > | baz > > > I imagine I could get something similar, if I I used .ONESHELL:, but I > want

Conditional broken line in recipe

Hi! Is something like this possible? target: foo \ ifeq (...) | bar \ endif | baz I imagine I could get something similar, if I I used .ONESHELL:, but I want to avoid it, as I'd need to redesign most of the rules. .ONESHELL: target: foo | ifeq (...) bar

Empty double-colon rule for optimizing make

Hi Dmitry! You recommended some time ago Adding a double colon rule targeting the Makefiles for optimizing make and having smaller debug logs. I think it would be good to document that usage in . Cheers, Alex --

Re: Empty double-colon rule for optimizing make

On Sun, Oct 29, 2023 at 10:16:17PM -0400, Dmitry Goncharov wrote: > On Sun, Oct 29, 2023 at 8:19 PM Alejandro Colomar wrote: > > > > Hi Dmitry! > > > > You recommended some time ago Adding a double colon rule targeting the > > Makefiles for optimizing make and ha

-Orecurse in combination with pipes

Hi! I'm trying to add a prefix to every line from a recursive make(1), so that I know what's going on, but it breaks -Orecurse. $ cat Makefile .PHONY: all f b foo bar all: f b; f: $(info MAKEfoo) @$(MAKE) foo | sed 's,^,MAKEfoo:,' b: $(info MAKEbar)

Re: -Orecurse in combination with pipes

On Tue, Feb 20, 2024 at 12:37:25AM +0100, Alejandro Colomar wrote: > Do you know if there's a way to achieve something like this thing > without breaking -Orecurse? Hmm, I got it. A variable, of course! $ cat Makefile .PHONY: all f b foo bar all: f b; f: $(info MAKE

make-rc: A parallel (as in make(1)) alternative to sysv-rc

t about the outcome I had: I booted with this configuration, and I first got into single-user mode, which I don't yet understand why it happened (there's probably something I didn't get right, but no real blocking problem, I guess). But then, after the typical type password or ^D to continue, I pressed ^D, and I got a shiny XFCE GUI completely wirking. Not bad for this prototype, I'd say. I'd like some help to polish this, if you may. Happy new year! Alex -- Alejandro Colomar Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/