Anyone see the release info for Mozilla 1.4 Beta? It says: "As of Mozilla 1.4b, it is possible to build Mozilla for Win32 using GCC."
Here's the specific build instructions for Windows: http://www.mozilla.org/build/win32.html
It notes:
GCC for Win32 is available as part of the MinGW project. The following mingw packages are required for building: gcc >= 3.2.2 (20030208) binutils >= 2.13.90 (20030104) w32api >= 2.3 mingw-runtime >= 2.4
--------------- Brian Vincent Copper Mountain Telecom vincentb@coppercolorado.com
On Thu, 8 May 2003, Brian Vincent (C) wrote:
Anyone see the release info for Mozilla 1.4 Beta? It says: "As of Mozilla 1.4b, it is possible to build Mozilla for Win32 using GCC."
Yes, the 1.4 release will build on MinGW/Cygwin. With a bit of luck, we'll have a binutils release in a week or two, so we can remove some of the ugly, ugly hacks that were put it to work around windres problems that have since been fixed.
Some of this fixes will help a little with an eventual Wine port, but this one will be tough. We still need a lot of work on winegcc/winewrap to get this to work, let alone possible enhancements to gcc for -mthread support.
We are currently failing on simple things with winegcc. For example:
1. It seems that MinGW's gcc support both main() and WinMain() as entry points irregardless of the -mwindows flags. We don't. This results in configure tests. For example, we can't currently build wxWindows using their configure script because configure invokes winegcc with the -mwindows flag even though it builds simple console apps that have a simple main() function. This obviously works under MinGW. I have little knowledge about linking issues like this, how can we support that in wingcc/winewrap?
2. We need to add support for the -shared flag to winegcc. This is a big task, and we haven't even started to look at these issues.
3. I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?
"Dimitrie O. Paun" dimi@intelliware.ca writes:
- It seems that MinGW's gcc support both main() and WinMain() as entry points irregardless of the -mwindows flags. We don't. This results in configure tests. For example, we can't currently build wxWindows using their configure script because configure invokes winegcc with the -mwindows flag even though it builds simple console apps that have a simple main() function. This obviously works under MinGW. I have little knowledge about linking issues like this, how can we support that in wingcc/winewrap?
That should be fairly easy to do in winebuild. I'll have a look next time I find time to hack winebuild.
- I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?
I guess we can simply ignore that flag, but I haven't looked at that in detail.
On May 8, 2003 07:57 pm, Alexandre Julliard wrote:
That should be fairly easy to do in winebuild. I'll have a look next time I find time to hack winebuild.
Thanks, much appreciated. This one actually blocks proper Wine support in wxWindows, so it will be way cool to fix it.
- I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?
I guess we can simply ignore that flag, but I haven't looked at that in detail.
From the gcc 3.2.2 docu:
-mthreads Support thread-safe exception handling on Mingw32. Code that relies on thread-safe exception handling must compile and link all code with the -mthreads option. When compiling, -mthreads defines -D_MT; when linking, it links in a special thread helper library -lmingwthrd which cleans up per thread exception handling data.
Are we always thread safe? I'm not even sure what exception handling they refer to...
On May 8, 2003 07:57 pm, Alexandre Julliard wrote:
- I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?
I guess we can simply ignore that flag, but I haven't looked at that in detail.
Ignore it, or pass it along to gcc like we do with most other flags?
"Dimitrie O. Paun" dpaun@rogers.com writes:
Ignore it, or pass it along to gcc like we do with most other flags?
You can't pass it along since standard gcc doesn't have that flag.
On May 12, 2003 02:31 pm, Alexandre Julliard wrote:
You can't pass it along since standard gcc doesn't have that flag.
Thanks, it wasn't immediately evident from the documentation.
ChangeLog Ignore -mthreads, it's not needed in Unix.
Index: tools/winegcc.c =================================================================== RCS file: /var/cvs/wine/tools/winegcc.c,v retrieving revision 1.15 diff -u -r1.15 winegcc.c --- tools/winegcc.c 2 Apr 2003 22:36:29 -0000 1.15 +++ tools/winegcc.c 12 May 2003 22:13:59 -0000 @@ -310,6 +310,8 @@ ; /* ignore this option */ else if (strcmp("-mwindows", argv[j]) == 0) ; /* ignore this option */ + else if (strcmp("-mthreads", argv[j]) == 0) + ; /* ignore this option */ else if (strncmp("-Wl,", argv[j], 4) == 0) ; /* do not pass linking options to compiler */ else if (strcmp("-s", argv[j]) == 0)
-
Alexandre Julliard -
Brian Vincent (C) -
Dimitrie O. Paun -
Dimitrie O. Paun