This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: [MAD SCIENCE EXPERIMENT]: Replace some libtool functionalitywith handcoded C
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: tromey at redhat dot com
- Cc: zack at codesourcery dot com, gnustuff at thisiscool dot com, libtool at gnu dot org,java-patches at gcc dot gnu dot org, automake at gnu dot org
- Date: 10 Dec 2003 13:09:40 -0200
- Subject: Re: [MAD SCIENCE EXPERIMENT]: Replace some libtool functionalitywith handcoded C
- Organization: GCC Team, Red Hat
- References: <SMJTOMLIYV5Y54YWEBC0XWMK21YS87.3fcdb2c3@d7500><orhe0h5bgv.fsf@livre.redhat.lsd.ic.unicamp.br><87ptexucat.fsf@fleche.redhat.com>
On Dec 9, 2003, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Alexandre" == Alexandre Oliva <aoliva@redhat.com> writes:
Alexandre> the *_OBJECT definitions assume the absence of shell-active
Alexandre> characters in filenames, which is probably a safe
Alexandre> assumption for Makefiles.
> It isn't unreasonable for a Java .class file's name to contain "$".
Oh, but if you look closely at the macros I posted, you'll notice that
this doesn't matter all that much. As long as the automake- or
hand-generated definition of ofile doesn't contain shell-active
characters (and IIRC automake already takes care of turning them into
underscores), you're fine.
And then, if it does, we need an additional variable set by the rule
preamble that sets a shell-safe version of ofile. The point here is
to avoid the overhead of having to run ofile through sed to protect it
at build time, when we can do it at Makefile-generation time.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer