On Thu, 14 Nov 2024 at 06:45, Chet Ramey wrote:
> On 11/12/24 8:17 PM, Grisha Levit wrote:
> > I'm not sure if this is the most idiomatic way to write the rule, but
> > if a libintl.h is generated, it needs to make it into the installed
> > headers directory to allow loadables to build.
>
AFAIK
On 11/13/24 4:25 PM, Grisha Levit wrote:
On Wed, Nov 13, 2024 at 3:45 PM Chet Ramey wrote:
On 11/12/24 8:17 PM, Grisha Levit wrote:
I'm not sure if this is the most idiomatic way to write the rule, but
if a libintl.h is generated, it needs to make it into the installed
headers directory to al
On Wed, Nov 13, 2024 at 3:45 PM Chet Ramey wrote:
>
> On 11/12/24 8:17 PM, Grisha Levit wrote:
> > I'm not sure if this is the most idiomatic way to write the rule, but
> > if a libintl.h is generated, it needs to make it into the installed
> > headers directory to allow loadables to build.
>
> I
On 11/12/24 8:17 PM, Grisha Levit wrote:
I'm not sure if this is the most idiomatic way to write the rule, but
if a libintl.h is generated, it needs to make it into the installed
headers directory to allow loadables to build.
I assume you mean third-party loadables, right? None of the examples
I'm not sure if this is the most idiomatic way to write the rule, but
if a libintl.h is generated, it needs to make it into the installed
headers directory to allow loadables to build.
---
Makefile.in | 4
1 file changed, 4 insertions(+)
diff --git a/Makefile.in b/Makefile.in
index 00db8cbb.
