January 2003 - Wine-Devel - list.winehq.org

Re: [RFC] io.h & friends

by Francois Gouget

On Thu, 9 Jan 2003, Dimitrie O. Paun wrote: [...] > Remember, __UNIX__ is always defined when compiling in Wine, so > we can never include io.h. Which begs the question: why do we have > it in msvcrt in the first place? :) Because it's part of the Visual C++ headers for the msvcrt library. Visual C++ applications, and there's a lot of them on the Windows platform, will just do: #include <io.h> and thus if we want them to compile with Winelib we need to provide an io.h header. Note: even if you don't have Visual C++, you can find this header in the MS SDK src/crt directory (with all the other msvcrt headers). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Hiroshima '45 - Czernobyl '86 - Windows '95

Jan. 9, 2003

Re: [RFC] io.h & friends

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > On my system (RH 8.0), /usr/include/sys/unistd.h simply does > > #include <unistd.h> > > so it works perfectly with this addition. But is this standard? > Should we just add a similar file to include/msvcrt/sys and be > done with it? Yes, that's probably safer, and it shouldn't break anything. -- Alexandre Julliard julliard(a)winehq.com

Jan. 9, 2003

Re: wrc: -v, -h, -w, -O res16

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > Collapse -w16 into -O as res16. -w16 can apply to all modes, not only .res, so you would need to support 'asm16' and 'hdr16' too. It seems cleaner to keep it as a separate option. -- Alexandre Julliard julliard(a)winehq.com

Jan. 9, 2003

Re: Small fixes for my previous patch

by Dimitrie O. Paun

On January 9, 2003 03:09 pm, Rok Mandeljc wrote: > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> Can you, pretty please, turn off HTML mail? <shrug/> -- Dimi.

Jan. 9, 2003

Re: [RFC] io.h & friends

by Dimitrie O. Paun

On January 9, 2003 02:26 pm, Francois Gouget wrote: > > Which begs the question: why do we have > > it in msvcrt in the first place? :) > > Because it's part of the Visual C++ headers for the msvcrt library. I was just _kidding_ :) Notice the smiley ... -- Dimi.

Jan. 9, 2003

Re: html browser for wine (khtml)

by Marcus Meissner

On Thu, Jan 09, 2003 at 11:21:18AM -0500, Dimitrie O. Paun wrote: > On January 9, 2003 12:14 pm, Alexandre Julliard wrote: > > I'd prefer to avoid C++, but if there's no other choice then of course > > we'll have to do it. I'm still hoping that we can find a way to avoid > > duplicating all that code inside Wine, C++ or not. > > Well, it seems the only worthy alternatives are Mozilla and KHTML, and > they are both written in C++. I am 100% with you on the non-duplicating > bit: even if we get something in the tree, it's not going to be maintained, > and it will bitrot to fast for words. It would be a huge addition and > burden to maintain for the Wine project. > > Galeon does not include Mozilla -- it uses it. There's got to be a way to > use KHTML in a similar manner. Even my first hand approximation (using > the Win32 build of Mozilla) seems like a better option than duplicating > code. If we get that working, I'm sure we can work with the Mozilla team > to find a way of embedding the Linux version. Heck, Galeon does it! Actually there already was a Konqueror / WINE integration already, called reaktivate. It replaced urlmon and provided a IWebBrowser interface. Ciao, Marcus

Jan. 9, 2003

Re: [RFC] io.h & friends

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > Remember, __UNIX__ is always defined when compiling in Wine, so > we can never include io.h. Which begs the question: why do we have > it in msvcrt in the first place? :) Because not all apps are cygwin apps, and pure Windows apps are of course not going to test for __UNIX__. > I'd like to be able to compile an app with _and_ without the > msvcrt runtime, by adding/removing the -mno-cygwin switch. You can do that just fine with my solution, all we need is a trivial unistd.h in the msvcrt headers. Plus this way you also have a chance to build the app under normal Unix, where you will never have io.h. > A include/cygwin would solve this nicely, we can simply stick in there > all the cygwin extensions (like io.h, and others), and in msvcrt we can > put the mingw extensions (such as unistd.h). The two includes will be > mutually exclusive, and you can choose between them with the -mno-cygwin > switch, the same as you do on Windows. I don't think that's necessary, and we can't go around creating a new include hierarchy for every single Windows compiler out there, not to mention keeping track of all changes to the includes of all these compilers to replicate them in our environment. We need to define a portable solution that has a reasonable chance of working in all cases, even including cases that don't exist today. If it requires tweaking broken apps a bit that's acceptable. -- Alexandre Julliard julliard(a)winehq.com

Jan. 9, 2003

Re: html browser for wine (khtml)

by Dimitrie O. Paun

On January 9, 2003 01:46 pm, Marcus Meissner wrote: > Actually there already was a Konqueror / WINE integration already, called > reaktivate. It replaced urlmon and provided a IWebBrowser interface. Sweet! This is exactly what I was hoping for. [...searching for it...] Here's the original announcement: http://dot.kde.org/994747675/ But this seems to be going what cxplugin does. We need the complement of that, don't we? -- Dimi.

Jan. 9, 2003

Re: [RFC] io.h & friends

by Dimitrie O. Paun

On January 9, 2003 12:54 pm, Alexandre Julliard wrote: > You can do that just fine with my solution, all we need is a trivial > unistd.h in the msvcrt headers. Plus this way you also have a chance > to build the app under normal Unix, where you will never have io.h. OK, cool. What about this patch? On my system (RH 8.0), /usr/include/sys/unistd.h simply does #include <unistd.h> so it works perfectly with this addition. But is this standard? Should we just add a similar file to include/msvcrt/sys and be done with it? ChangeLog Add a unistd.h file for mingw/Unix compatibility. Index: include/Makefile.in =================================================================== RCS file: /var/cvs/wine/include/Makefile.in,v retrieving revision 1.79 diff -u -r1.79 Makefile.in --- include/Makefile.in 9 Jan 2003 01:09:16 -0000 1.79 +++ include/Makefile.in 9 Jan 2003 17:20:17 -0000 @@ -196,6 +196,7 @@ msvcrt/sys/types.h \ msvcrt/sys/utime.h \ msvcrt/time.h \ + msvcrt/unistd.h \ msvcrt/wchar.h \ msvcrt/wctype.h --- /dev/null 2002-08-30 19:31:37.000000000 -0400 +++ include/msvcrt/unistd.h 2003-01-09 12:18:20.000000000 -0500 @@ -0,0 +1,2 @@ +#include <io.h> +#include <process.h> -- Dimi.

Jan. 9, 2003

Re: html browser for wine (khtml)

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > I'm not saying it's an unreasonable request. All I'm saying is that it would > be a change in policy to accept C++ code in Wine. So you need to take it up > with Alexandre :) I'd prefer to avoid C++, but if there's no other choice then of course we'll have to do it. I'm still hoping that we can find a way to avoid duplicating all that code inside Wine, C++ or not. -- Alexandre Julliard julliard(a)winehq.com

Jan. 9, 2003