Stepan Kasal wrote:
> If the bison-runtime contains only the .mo file, then many distributors
> will forget to set the dependency.
> But if we change bison so that it installs a shared library which will
> eventually be used bu the applications, then the dependency will be
> discovered automatically.
But then the application's Makefile needs changes: -lbison. This is an
annoyance, because
- "bison -y" is no longer equivalent to YACC, [since YACC doesn't
create a dependency to a library],
- so far, libbison would contain nothing of real use.
Can we imagine a way to hint distributors to add the dependency to
bison-runtime without changing the application's Makefile?
Bruno
