On Thu, Mar 20, 2003 at 04:53:22PM +0100, Leopold Toetsch wrote:
And of course there areflex/bisons for Win out there somewhere, if one wants actually change the .l/.y sources.
Could we bodge round this by adding a Configure.pl flag to suppress adding the rules to use bison (or add in more rules to defeat any make default rules, as I think perl5 does), and default this to suppress?
I don't have any indications till now, that this was the problem in the first place - error messages where not about trying to run bison or some such, but about wrongly? pulled in includes, which then choked somewhere.
The 3 or 4 people on this list who do want to edit those files are on-the-ball enough to remember to run Configure.pl in such a way to turn off the suppress.
Which is a major PITA during development. The current method is a compromise of course. But, when the timestamp of generated files is always after that of sources[1], and there is no over dependency[2] then on sources, the current procedure should be ok.
[1] is done by my check-in script or by $devoloper
[2] should easily be verified in the Makefile
I think that this would make life easier for everyone. (because it also saves the 3 or 4 people on the list having to read tedious e-mail messages from people about the subject)
I'm currently not sure, if there are 4 people around, that compile imcc on native windows :-) Anyway, the current problem is not that bison/flex got invoked (which isn't that problem either - every project has some prerequesits) but is somewhere else. If there is a better solution for solving the generated files problem (which AFAIK currently is not on the air) I'll all ok with it.
Nicholas Clark
leo
