This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: Uppercasing files
- To: tromey at redhat dot com
- Subject: Re: Uppercasing files
- From: Emiliano <emile at iris-advies dot com>
- Date: Wed, 31 Jan 2001 10:15:16 +0100
- CC: automake at gnu dot org
- List-Id: Discussion list for automake <automake.gnu.org><mailto:automake-request@gnu.org?subject=unsubscribe>
- References: <3A76B66C.CDA7BC98@iris-advies.com> <877l3ctkfi.fsf@creche.redhat.com>
Tom Tromey wrote:
>
> >>>>> "Emile" == Emiliano <emile@iris-advies.com> writes:
>
> Emile> I'm trying to create an automake file that has rules to
> Emile> uppercase files. For example I have something.ext and I want
> Emile> it to create a copy SOMETHING.EXT. I tried with this:
>
> Emile> pkgdata_DATA = SOMETHING.EXT OTHER.EXT
> Emile> CLEANFILES = $(pkgdata_DATA)
> Emile> %.EXT : %.ext
> Emile> cp -f $< `echo $< | tr a-z A-Z`
>
> Emile> but that doesn't work since no file SOMETHING.ext exists. How
> Emile> so I go about this?
>
> Write explicit rules.
>
> SOMETHING.EXT: something.ext
Yes, but I'd rather not if it can be avoided. There are quite a number
of them
and it impacts readability, plus there's more to keep consistent
manually (after
the uppercasing other ops are done on the files.
At the moment I've used a default rule, which works, but doesn't handle
dependancy:
.DEFAULT:
cp -f `echo $(basename $@) | tr [:upper:] [:lower:]`.m $(basename
$@).m
../mumps/mumps $(basename $@).m 2>&1
Emile