From: Greg C. <chi...@mi...> - 2002-11-14 07:20:14
|
Luke Dunstan wrote: > > >From: Greg Chicares <chi...@mi...> > >Reply-To: mingw-users <min...@li...> > >To: mingw-users <min...@li...> > >Subject: Re: [Mingw-users] Configuring mingwDTK bison > >Date: Thu, 14 Nov 2002 00:55:35 -0500 > > > >Luke Dunstan wrote: > > > > > > ----- Original Message ----- > > > From: "Greg Chicares" <chi...@mi...> > > > To: "mingw-users" <min...@li...> > > > Sent: Thursday, November 14, 2002 3:32 AM > > > Subject: [Mingw-users] Configuring mingwDTK bison > > > > > > > Earnie Boyd wrote several months ago: > > > > > Subject: [Mingw-users] Re: Using MSYS/Mingw to port wine > > > > > Date: Tue, 28 May 2002 17:21:31 -0400 > > > > > > > > > > Steven Edwards wrote: > > > > > > > > > > > > I just copyed the /share/bison.simple and bison.hairy to /bin and > >it > > > > > > worked fine. Like I said nothing major. > > > > > > > > > > That's strange. Oh, probably not that strange, it has to do with > > > > > /mingw/share/... not being resolved within bison. I'll have to take > >a > > > > > look at the source for this. The other solution could have been > > > > > export BISON_SIMPLE=D:/mingw/share/bison.simple > > > > > export BISON_HAIRY=D:/mingw/share/bison.hairy > > > > > > > > Has the "/mingw/share/... not being resolved within bison" > > > > situation changed? > > > > > > > > I have: MSYS-1.0.8-i686-2002.06.25-1.exe > > > > latest snapshot is: MSYS-1.0.8-2002.09.07-1.exe > > > > > > > > Steven's fix works for me. I know I could set environment > > > > variables too. But I'm trying to write up procedures for > > > > others to use, and if this just works effortlessly in a > > > > later release with neither of those workarounds, then > > > > it's one less thing to document. > > > > > > The gnuwin32 port of bison has been patched to look for data files > >relative > > > to the bin directory, so using the binary distribution of that package > >is > > > probably the simplest solution. > > > >Doesn't the mingwDTK bison already look for data files > >in the bin directory, since, as Steven says, if you > >copy the files there it just works? > > By "relative to the bin directory", I mean it looks in the parent of the bin > directory for "share", etc. like Mingw GCC does (conceptually like > ${bin}/../share/bison/bison.simple). > > > > >Is there any plan to change mingwDTK bison so that > >either it looks in the directory where it puts the > >files, or puts the files in the directory it looks in? > > > > I guess it would be simple to repackage it with the data files in "bin", but > ideally it would use "share" to remain consistent with other Mingw and GNU > programs. I don't know what plans there are, but Manu and others have > started a "ports" module in Mingw CVS so I expect bison will be added at > some point. > > >I don't have anything against gnuwin32 or any other > >project, but I just prefer to use stuff from the > >mingw maintainers. Maybe it's a silly prejudice, > >and I wouldn't push it on anyone else, but I earn > >my living with these tools, I need to know and > >trust the people that maintain them, and I can > >only subscribe to so many mailing lists. > > Fair enough. Until something changes, could you just repackage mingwDTK and > distribute it with your software (assuming that is what you are writing the > instructions for)? Extra maintenance, I know... I'll give a URL for mingwDTK and add the environment variables Earnie suggested. I'm writing instructions for my own software, and I'm also trying to update the build procedures for wxWindows. Although not ideally elegant, this works and I can maintain it easily enough. |