Re: MinGw port of gawkextlib

[Andrew J. Schorr]

Hi,

On Mon, May 16, 2022 at 07:20:40PM +0300, Eli Zaretskii wrote:
> It's your call which customizations to support, but in general, it
> isn't unthinkable for a user to set AWKLIBPATH in the environment as a
> means of organizing the extensions in some way that is meaningful for
> the user.

At the moment, only the select extension requires access to gawk bundled
extensions. So the risk is that a user installed the gawk time extension
in a nonstandard location, which would break just that one. I think it's
a small risk. The user would have to have installed gawk with "make install"
and then moved the time extension out of the directory where gawk's
"make install" deposited it.

> See above.  I could imagine someone trying to keep separate extensions
> that came from different sources or lend themselves to some other
> grouping.  Whether this is an important use case, I cannot tell.

I think it's a small risk for now. We can reassess if we get complaints.

> > I think this is all covered by the 'unset AWKLIBPATH'. I am able to
> > build successfully on linux with AWK as defined above. Are you able to
> > test with the attached patch to test.makefile?
> 
> Yes, the tests pass.

Thank you for testing this.

Were there other MinGW issues that we need to address besides getting
"make install" to put things in the right place and pulling in gawkextlib as
needed? I think a front-end "gawkext" script can handle those issues.

Thanks,
Andy