I have the following in my Makefile.am, and automake is not using the rule to
build the executable.
tableopts_nr%.c: tableopts.l4
$(FLEX) -P $(subst -,_,$(*F)) $* -o $@ $<
tableopts_nr%.$(OBJEXT): tableopts_nr%.c
$(COMPILE) -c -o $@ $<
tableopts_nr%.tableopts$(EXEEXT): tableopts
00, Gavin Smith
wrote:
> On Mon, Jul 14, 2014 at 6:49 PM, Will Estes wrote:
> > I have the following in my Makefile.am, and automake is not using the rule
> > to build the executable.
> >
> > tableopts_nr%.c: tableopts.l4
> > $(FLEX) -P $(subst -,_,$(*F)) $
it and have not been able to come up
with a solution. At most, I'm able to not include some generated header files,
which then really confuses the test suite in the generated tar ball.
What other information / examples can I provide to make this clear?
Thanks!
--Will
--
Will Estes
westes...@gmail.com
Yeah, I'll work up a small example because the entire test suite is large and
there's a lot of stuff that follows the same pattern.
On Thursday, 12 November 2015, 1:55 pm -0500, Nick Bowler
wrote:
> Hello,
>
> On 2015-11-12, Will Estes wrote:
> > The flex program
On Thursday, 12 November 2015, 1:55 pm -0500, Nick Bowler
wrote:
> Hello,
>
> On 2015-11-12, Will Estes wrote:
> > The flex program includes a test suite to enable testing of the version of
> > flex built in the flex tree. From a distributed tar ball (made with &q
On Thursday, 12 November 2015, 9:41 pm +, Gavin Smith
wrote:
> On 12 November 2015 at 19:19, Will Estes wrote:
> > and Makefile.am:
> >
> > check_PROGRAMS = test
> >
> > test_SOURCES = test.l
> > nodist_test_SOURCES = test.c
> >
> > I
iven that I'm ok with the build and then delete that
happens.
>
> Cheers,
> Nick
>
--
Will Estes
westes...@gmail.com
lly, consider whether you want to distribute the generated parser
> sources. That way your users don't need these tools installed just to
> build your package.
>
> [1]
> https://www.gnu.org/software/automake/manual/automake.html#Multiple-Outputs
>
> Cheers,
> Nick
>
--
Will Estes
westes...@gmail.com
an see from flex's pull requests, we're gearing up for a release and
we're working out how to make releasing flex easier in the future to solve the
frequency of release problem.
--
Will Estes
westes...@gmail.com
