Re: Handling '=' in a filename together with $(eval )

Alejandro Colomar <[email protected]> Thu, 13 Feb 2025 17:13:52 +0100

Newsgroups	gmane.comp.gnu.make.general
Message-ID	<rsbmyuy4gsttdmmzi7o3r64sly5ktd4y6spxnwyqdn4k6gdzqu@zbtu4kputths>

On Thu, Feb 13, 2025 at 10:35:32AM -0500, Paul Smith wrote:
> On Thu, 2025-02-13 at 10:33 -0500, Paul Smith wrote:
> > On Thu, 2025-02-13 at 16:24 +0100, Alejandro Colomar wrote:
> > > I'm aware of that trick.  However, I think it won't work for me,
> > > since I don't hardcode the filenames in the Makefile, but get them
> > > with
> > > 
> > >  $(shell find ...)
> > > 
> > > instead.
> > 
> > You can always use subst to handle this, like:
> > 
> >   $(subst =,$$(EQ),....)
> 
> This might require an extra eval, I'm not sure I didn't test it. 
> Basically, my opinion is still:
> 
> > Note I don't really recommend any of this.  With the current
> > limitations of make, as defined by POSIX, it's just very difficult to
> > use filenames that contain special characters.  I recommend a "just
> > don't do it" approach :).

Hi Paul,

I agree with your general opinion.  I'm going to try a few tricks with
the variable, and trying to get the number of expansions right, but if
not, I'll surrender.  I was trying to build a PDF book of the Unix V10
manual pages, which contain a weirdly named manual page: '=.1' (for the
command '=').  You can guess that's not nice with make(1).  :)

At least, that's only one manual page, and I could manually rename it to
'eq.1'.  That's going to result in a bit of weirdness, but let's blame
the authors of the page.  Long live the portable filename character set!
:-)

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>

signature.asc (application/pgp-signature, 833 B)