quite exactly the same job that needs to be done
It's the same job, but lex and yacc are not at all the "same" as vala.
They are fundamental Unix utilities that have been around
forever. Whereas vala is a relatively recent invention, far less
ubiquitous. So I see no reason to treat them the
Am 24.10.2020 um 17:53 schrieb Karl Berry:
The obvious canonical examples would have to be lex and yacc. They
generate .c and .h files into the blddir, and automake has built-in
mechanisms to include the generated sources into the tarball.
No argument there, but vala is so much
The obvious canonical examples would have to be lex and yacc. They
generate .c and .h files into the blddir, and automake has built-in
mechanisms to include the generated sources into the tarball.
No argument there, but vala is so much newer than lex and yacc,
especially in terms
Am 24.10.2020 um 01:14 schrieb Reuben Thomas via Bug reports for Automake:
Unlike include files, you can't simply tell cc to
look in two places for the file it is to compile, so some other solution
is needed.
Actually the traditional VPATH mechanism does not distinguish types of
files at
I've had a look at the patch now, and found and fixed one bug.
However, an issue comes up for VPATH builds that needs a more thorough fix:
C files generated from Vala sources are shipped by "make dist" and hence
end up in srcdir, but in a VPATH build with a Vala compiler, they will be
in
