2 Dec
2004
2 Dec
'04
6:13 a.m.
Hi
I am not against making bison a requirement (especially since it is
Free Software and easily obtainable with no license issues), but since
so many devs are against it, perhaps we should not.
I recommend a compromise where the generated file is used by the build
and included in CVS. However, the original bison file should also be
present. There should be a readme file in the vacinity explaining
things - and the generated file should include a warning that it is
generated and by what.
Then those that want to make changes to the generated file can
download Bison and do so; committing both the new source/Bison file
and the generated file. Those not wanting a complex build process can
just ignore it and never worry about unless they want to make changes
to that generated file.
I feel that this is a good compromise.. comments?
Cheers
Jason
On Wed, 1 Dec 2004 18:03:02 -0800 (PST), Steven Edwards
<steven_ed4153(a)yahoo.com> wrote:
Flex and Bison are industry standards. Here is a build
that I know works because I used it on
Windows for my Wine porting. Just because the Mingw people are pointing to a old broken
build is
not our problem.