This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: java parser intentionally in builddir?
- To: mrs at wrs dot com (Mike Stump)
- Subject: Re: java parser intentionally in builddir?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 22 Oct 1998 23:14:54 -0600
- cc: egcs at cygnus dot com, robertl at dgii dot com
- Reply-To: law at cygnus dot com
In message <199810192115.OAA26403@kankakee.wrs.com>you write:
> > Date: Fri, 16 Oct 1998 15:56:10 -0500
> > From: Robert Lipe <robertl@dgii.com>
>
> > The gcc/java Makefile.in is different than all the other languages
> > in that a prebuilt parser isn't in the srcdir and it looks like it's
> > intentionally build in the builddir.
>
> I like the idea of unifying the two to get all the benefits of both
> schemes, that way, we can forever get rid of the problem. Something like:
>
> parse.c: $(srcdir)/parse.y
> if [ -r $(srcdir)/parse.c -a
> $(srcdir)/parse.c -nt $(srcdir)/parse.y ]; then
> cp $(srcdir)/parse.c .
> else
> $(BISCON) ...
> fi
Or better yet, check for a reasonable version of bison and if found go ahead
and build the parser files in the build tree.
jeff