Dimitrie O. Paun wrote:
> On December 31, 2002 01:52 pm, Manu wrote: > > -mno-cygwin don't have much sense, since Visual-MinGW is built with > > MinGW, under Windows, not Cygwin. > > Yes, I know, but -mno-cygwin should be a noop in that case. And if > someone has cygwin installed, it will ensure that Visual-MinGW is > not linked against the cygwin libs. I think we are in agreement here > that Visual-MinGW should not depend on cygwin, no? If so, it makes > sense to make this explicit with -mno-cygwin. If MinGW doesn't complain, I agree. > > > -- Do not use -pedantic, the code does not compile with gcc 3.2 > > > on Linux with that flag. > > > -- Do not use -fvtable-thunks, it is deprecated in gcc 3.2 -fvtable-thunks is problematic. I use gcc version 2.95.3-6 (mingw special), (faster, smaller binaries) -fvtable-thunks is required with gcc 2, but gcc 3 outputs a warning. Any workaround? > > > Please apply this patch with 'patch -p1 < winelib.diff'. > > > > Apparently, the patch refuses to be applied, probably due to > > the fact that I changed a few things in makefiles formating. > > OK, I can create a new patch for you. > > > BTW, makefiles are generated by Visual-MinGW, so I > > suggest to add dedicated makefiles for Winelib. > > eg: "makefile.wine". > > I can certainly do that, but then they will drift appart. > The ideal situation is to support both mingw and wine out > of the same makefile, so that everything "just works". > If makefile is generated by Visual-MinGW, I think it's worth > modifying Visual-MinGW so that it generates the right makefile > for both mingw and wine, don't you think so? Visual-MinGW generates the right makefile indeed, from user parameters in the ".prj" file. There is three possibilities: - makefile.wine - configure.in/Makefile.am > configure script. - modifying params in ".prj" files. I will change the parameters in ".prj" files, then generated makefiles should work for both MinGW and Wine. Though, I don't have a solution for -fvtable-thunks. About configuration files, I started a new project called MSYS Here, which is a MSYS loader. With it, MSYS can be launched from Windows Explorer, the same way than the "DOS Prompt Here" power toy. The sources are in the MinGW CVS: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mingw/utils/msys-here/ I'll have to write configuration files for it, as well as for WinUI, which both Visual-MinGW and MSYS Here use. I'm not an Autotools guru, but if it works, I'll also commit configuration files to visual-mingw/winui. Then, I'll maybe write configuration files for Visual-MinGW as well. Currently, I'm not very good with Auto-stuff :( Manu.