From: Earnie B. <ear...@ya...> - 2002-03-06 22:58:32
|
First, let me point you to http://www.mingw.org/msys.shtml. Laszlo Vecsey wrote: > > I successfully compiled tcl8.4a3 with mingw invoked from a cygwin-bash setup > with the paths set appropriately to the mingw gcc.exe but my question is > about whether __try and __except could be successfully defined as asm > functions and work just the same from a cygwin gcc based compile > with -mno-cygwin. > MinGW now has it's own shell environment named MSYS. The -mno-cygwin variant is limited to the Cygwin gcc and questions concerning the Cygwin gcc need to be asked on the Cygwin list. > I have to admit I really like the setup.exe and online install that cygnus > offers for the cygwin/bash environment and the tcl case with the __try and > __excepts are really the only case I can think of that requires the real > mingw gcc, at least for my own development stuff. > This may simply be a case of two files of the same name (excpt.h) in two different directories (mingw32 and w32api). Now, which version do you have in your MinGW directories the mingw32 version or the w32api version. My guess is the w32api version since you did build the win32 version of tcl but the result may not be what you expect. Note, SEH is currently non-functioning in all versions of GCC. I've heard that the ReactOS team is working on an implementation for some future release of GCC. > Is it possible for the mingw community to use the cygnus setup at least as a > means to redistribute our portion of the files, regardless of whether its > merged with the main cygwin gcc? It just seems to me theres a huge > convenience of having that available so that a machine can be effortless > setup with just a click or two, and it would certainly help promote the > environment further to the point where it could be recommended as a good way > for anyone to just grab a project, compile, and change something. > I've thought about it, but I'll probably work something else out. I don't have the same control of the ftp directory layout from SourceForge so it would be more difficult to control. I am working on a different angle with a more Win32ish install. > Besides the __try/__excepts that I ran into with tcl the only other time I > had to use the real mingw gcc was for compiling binutils for an hc11 > microcontroller cross-compiler. I can't recall what the exact problem was > with the cygwin version but I ended up just following the README's for the > cross-compiler to the letter and it specified mingw native and thankfully > finally worked. > Your point here for MinGW is what? > And on a similar line of thought the gcc I compiled was 3.0.3 and I had > heard beforehand and noticed first hand how much faster the compiles took > place.. because of the lack of invoking external programs for linking and > whatnot as the previous gcc's do. > Your point here for MinGW is what? > Is it just a case of no one getting around to put together a distribution > package or is there another reason its not part of the cygwin setup or the > mingw site? And again if we could lobby for a place and checkbox in the > cygnus setup I think it would be very beneficial ;) > I'm working on a more complete distribution with a setup utility. I will have it ready before the end of my year. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |