Hi Nick, Jan, all,
nick> I think all that should be needed is to list the .l (or .y) file in
_SOURCES normally
Thanks much. I was thinking I should avoid that since the .[ly] are not
ultimate sources, but if it works, fine with me.
jan>
BUILT_SOURCES = foo.y
foo.y: foo.cweb
On Tuesday 2021-09-21 22:32, Karl Berry wrote:
>Thanks much. I was thinking I should avoid that since the .[ly] are not
>ultimate sources, but if it works, fine with me.
>
>jan>
>BUILT_SOURCES = foo.y
>foo.y: foo.cweb
>somecommands
>
>That would be sensible, but I failed
Redoing the tests with 1.16g I now have 9 failed tests, the
testsuite.log is attached.
Thanks much for giving it a whirl right away.
But are those failures anything new?
FAIL: t/fn99subdir
FAIL: t/lex-clean-cxx
FAIL: t/lex-depend-cxx
FAIL: t/test-extensions-empty
FAIL: t/subpkg
FAIL:
Suppose I want to generate a lex or yacc input file from another file,
e.g., a CWEB literate program. Is there a way to tell Automake about
this so that the ultimately-generated parser/lexer [.ch] files are saved
in srcdir, as happens when [.ly] are direct sources, listed in *_SOURCES?
I should
On Tuesday 2021-09-21 19:02, Karl Berry wrote:
>Suppose I want to generate a lex or yacc input file from another file,
>e.g., a CWEB literate program. Is there a way to tell Automake about
>this so that the ultimately-generated parser/lexer [.ch] files are saved
>in srcdir, as happens when [.ly]
On 21/09/2021, Karl Berry wrote:
> Suppose I want to generate a lex or yacc input file from another file,
> e.g., a CWEB literate program. Is there a way to tell Automake about
> this so that the ultimately-generated parser/lexer [.ch] files are saved
> in srcdir, as happens when [.ly] are direct
