|
From: Eli Z. <el...@gn...> - 2014-10-06 16:28:34
|
> Date: Mon, 06 Oct 2014 17:40:35 +0200 (CEST) > Cc: min...@li... > From: Werner LEMBERG <wl...@gn...> > > > > AFAIK, the MinGW project never offered a MinGW port of bison. > > >From the README in > > https://sourceforge.net/projects/mingw/files/MSYS/Extension/bison/bison-2.4.2-1/ > > The packages within the MSYS/Extension directory are supported by > the MinGW team, and provide useful facilities not required for a > basic MSYS installation. > > This is what I would like to have updated. That's an MSYS Bison, not a MinGW (a.k.a. "native") Bison. I don't see why would you need an MSYS Bison, unless you are building the MSYS toolchain. > I suspect that with `MinGW port' you mean a bison executable to be > run outside of the msys environment. Not "outside of MSYS environment", but rather an executable that doesn't use any of the MSYS DLLs, including msys-1.0.dll, the Cygwin DLL in disguise. IOW, I mean a native Windows application that uses the native Windows runtime, and nothing else. > As mentioned earlier, I don't really need this since I configure and > compile my package within an msys shell. That's a serious confusion, but I won't explain why unless you ask me to. If you are happy running MSYS Bison, it's fine by me. |