[bug #63537] Regression in switches that can be flipped back and forth.

Update of bug #63537 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #63484] make 4.4 incorrectly thinks target does not exist

Update of bug #63484 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #63516] `include` of absolute path prepends path with `./`

Update of bug #63516 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #63510] Confusing "update target 'foo' due to: target does not exist" message

Update of bug #63510 (project make): Item Group:None => Enhancement Status:None => Fixed Assigned to:None => psmith Open/Closed:

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 1:54 PM Alejandro Colomar wrote: > That would render the $(includedir) variable unusable for use within the > Makefile (for example, within targets that install the header files). We can introduce another variable, e.g. myincludedir and initialize it with the expanded

Re: [doc] MAKEOVERRIDES is undocumented

Hi Paul, On 12/19/22 20:48, Paul Smith wrote: On Mon, 2022-12-19 at 17:25 +0100, Alejandro Colomar wrote: And another variable (and this one is not mentioned at all in the manual): MAKEFLAGS. Maybe I misunderstood, but MAKEFLAGS is discussed extensively in the manual. Yeah, maybe I wrote

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, 2022-12-19 at 17:25 +0100, Alejandro Colomar wrote: > And another variable (and this one is not mentioned at all in the > manual): MAKEFLAGS. Maybe I misunderstood, but MAKEFLAGS is discussed extensively in the manual.

Re: [doc] MAKEOVERRIDES is undocumented

Hi Dmitry, On 12/19/22 20:35, Dmitry Goncharov wrote: On Mon, Dec 19, 2022 at 2:33 PM Jeffrey Walton wrote: Yep, that's why we track both includedir and pc_includedir. You don't have to resort to if statements to initialize either of the variables. regards, Dmitry Let me try to explain:

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 2:33 PM Jeffrey Walton wrote: > Yep, that's why we track both includedir and pc_includedir. You don't have to resort to if statements to initialize either of the variables. regards, Dmitry

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 1:53 PM Alejandro Colomar wrote: > > On 12/19/22 19:18, Dmitry Goncharov wrote: > > On Mon, Dec 19, 2022 at 11:24 AM Jeffrey Walton wrote: > >> For the *.pc file, we need '$(prefix)' to survive unexpanded. > > > > What about > > includedir:=$${prefix}/include > >

Re: [doc] MAKEOVERRIDES is undocumented

Hi Dmitry, On 12/19/22 19:18, Dmitry Goncharov wrote: On Mon, Dec 19, 2022 at 11:24 AM Jeffrey Walton wrote: For the *.pc file, we need '$(prefix)' to survive unexpanded. What about includedir:=$${prefix}/include myconfig.pc:; @echo 'includedir=$(includedir)' >> myconfig.pc ? That would

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 11:24 AM Jeffrey Walton wrote: > For the *.pc file, we need '$(prefix)' to survive unexpanded. What about includedir:=$${prefix}/include myconfig.pc:; @echo 'includedir=$(includedir)' >> myconfig.pc ? regards, Dmitry

Re: [doc] MAKEOVERRIDES is undocumented

Hi Paul, On 12/19/22 17:22, Paul Smith wrote: On Mon, 2022-12-19 at 10:57 -0500, Jeffrey Walton wrote:    ifeq ($(includedir),) includedir := $(prefix)/include PC_INCLUDEDIR = $${prefix}/include    else PC_INCLUDEDIR = $(includedir)    endif Maybe I'm misunderstanding

Re: [doc] MAKEOVERRIDES is undocumented

Hi Paul, On 12/19/22 17:16, Paul Smith wrote: On Mon, 2022-12-19 at 16:45 +0100, Alejandro Colomar wrote: I had to search some related things in stackoverflow to find this.  I think you should document this (and a few others) in 'Other Special Variables'

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 11:22 AM Paul Smith wrote: > > On Mon, 2022-12-19 at 10:57 -0500, Jeffrey Walton wrote: > >ifeq ($(includedir),) > > includedir := $(prefix)/include > > PC_INCLUDEDIR = $${prefix}/include > >else > > PC_INCLUDEDIR = $(includedir) > >endif > >

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, 2022-12-19 at 10:57 -0500, Jeffrey Walton wrote: >    ifeq ($(includedir),) > includedir := $(prefix)/include > PC_INCLUDEDIR = $${prefix}/include >    else > PC_INCLUDEDIR = $(includedir) >    endif Maybe I'm misunderstanding some subtlety here but why not just:

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, 2022-12-19 at 16:45 +0100, Alejandro Colomar wrote: > I had to search some related things in stackoverflow to find this.  I > think you should document this (and a few others) in 'Other Special > Variables' > . I

Re: [doc] MAKEOVERRIDES is undocumented

Hi Jeffrey, On 12/19/22 16:57, Jeffrey Walton wrote: On Mon, Dec 19, 2022 at 10:45 AM Alejandro Colomar wrote: I needed to use MAKEOVERRIDES for updating a pkgconf (.pc) file. I want it to have the correct directory variables as used when building/installing the library, so if the user

Re: [doc] MAKEOVERRIDES is undocumented

On Mon, Dec 19, 2022 at 10:45 AM Alejandro Colomar wrote: > > I needed to use MAKEOVERRIDES for updating a pkgconf (.pc) file. I want it to > have the correct directory variables as used when building/installing the > library, so if the user specifies 'includedir=/foo/bar' in the command line,

[doc] MAKEOVERRIDES is undocumented

Hi! I needed to use MAKEOVERRIDES for updating a pkgconf (.pc) file. I want it to have the correct directory variables as used when building/installing the library, so if the user specifies 'includedir=/foo/bar' in the command line, the .pc file should be updated with that info. The rule I