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

Wine, Mozilla & IE ?

by Juan Rey Saura

Hi ! I've read in the list there is a project about compiling Mozilla under Wine, I think it would be great. Several parts of wine need an IWebBrowser implemtation; CHM support, some applications... One implementation based on the khtml is in the works, but Mozilla does implement it yet ( see http://www.iol.ie/~locka/mozilla/mozilla.htm ). Could Mozilla, under Wine or maybe native version, be used as a replacement for the IE IWebBrowser implementation?

Jan. 10, 2003

Re: Re: html browser for wine (khtml)

by Mike Hearn

> As i know, khtml support most of the IE-isms (for compatibility, try to actve "IE support" in konqueror). > And for ActiveX, it must be simply supported by a khtml plugin (as crossover plugin do) If only it were that simple. Rather ironically the thing that led to me Wine in the first place was that I needed to use features of an ActiveX control that were only available under IE. Although it would also (in theory) work in Mozilla or Konq as well, in practice they didn't support rich enough plugin interfaces for host scripting merge (where the plugin hooks into the browsers script interpreter and partially merges them together). Hence I now sometimes need to use IE under Linux. There are lots of IEisms that I doubt Konq replicates. ActiveX controls are sometimes a lot more complex than just displaying some controls on a page, they can actually integrate with IE to quite an impressive extent. For instance: - DirectX filters - DHTML Behaviours - ActiveScript (needs a vbscript interpreter as well as a JS interpreter) - ActiveX data binding - .NET integration and so on. I expect upstream khtml could get 80% of the way there, but the remaining 20% would require tight integration with Wine and some extensive code changes. -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 10, 2003

Re: html browser for wine (khtml)

by Mike Hearn

> Well, last time the talking here was that due to QT license, KHTML couldn't be > used, and now with the Safari you don't need any QT (you can use other GUI > kits around)... Actually Ender was de-Qting KHTML at some point, are you still around Ender? I haven't seen the code but I expect you can forget about Safari - iirc it's been integrated with Quartz which is of course a proprietary Apple system only. Seeing as they were ranting about speed, I doubt they'll have imposed the overhead of a graphics layer abstraction system. About duplication - I think it's probably most likely that the best course would be to copy the KHTML source into the Wine tree, because I'd expect modifications would be needed in order to support all the IEisms that will crop up in regular usage of the WebBrowser control. KHTML out of the box won't, and never will support ActiveX, IE specific markup or any of the other proprietary stuff MS threw in for fun during the browser wars. The KDE team would rightly reject such patches from being integrated into upstream. I don't know how much progress Ender made, it might be worth emailing him to find out. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 10, 2003

Re: getting started

by Glen Kaukola

Dimitrie O. Paun wrote: > Compiling stuff with visual studio is a first step. But it should be > very simple to do a Makefile for the examples, how many files do you > have in one example? > > Here is an example Makefile that you can use under mingw: > (let me know if it doesn't work, I just typed it inline here, no testing) Well I know at least the basics of Makefiles already, on linux anyhow. I'm thinking I can easily come up with one for each of the sample programs in my books. I guess I was confused by the suggestion to use the Makefiles from my book, thinking that there would be something special about them. I'm not very familiar with windows development, so it's an honest mistake. It seems studio doesn't even use makefiles though. By the way, I feel terrible about it, hehe, but I went out and got visual c++. So I guess I'll be testing any executables I produce with it as well as going the other route with mingw. So now unless I have any unforseen problems, you probably won't hear from me for a while until I find something that doesn't work. Thanks for taking the time to help me get started.

Jan. 10, 2003

Re: [Fwd: Re: getting started]

by Dan Kegel

Glen Kaukola wrote: > Well I've gotten MinGW and sorta learned my way around it. But now, my > problem is that neither of my windows programming books has makefiles of > any sort. All they have is C++ code. So maybe I should go with my > original plan of compiling stuff with visual studio and seeing if it > runs under wine. Or do you have any other suggestions? Your plan's fine -- but you should also go ahead and learn Make, and test the code in the books using MinGW and Makefiles. Knowledge is power. - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com

Jan. 10, 2003

Expected name, id, length or ordinal error

by John Westerman

Hi Everybody, I'm currently trying to compile the basic Win32 "Hello world" project that VC6 generates for you using Wine. Currently I'm running winemaker like this: winemaker --nomfc -I/usr/local/wine/include -L/usr/local/wine/lib -ikernel32.lib -iuser32.lib -igdi32.lib -iwinspool.lib -icomdlg32.lib -iadvapi32.lib -ishell32.lib -iole32.lib -ioleaut32.lib -iuuid.lib -iodbc32.lib -iodbccp32.lib /home/john/hello I've also added the header files that would have been found in the StdAfx.h to my main.cpp. This is because Winemaker wouldn't build with StdAfx.h in the directory, so I deleted it. This is the error I now get when I run make ./hellotest.spec:8: Expected name, id, length or ordinal My hellotest.spec looks like this: name hellotest type win32 mode guiexe init WinMain rsrc hellotest.res import kernel32.lib import user32.lib <- line of failure Any Ideas? Thanks in Advance, John Westerman

Jan. 10, 2003

Re: prevent dereferencing null

by Marcus Meissner

On Thu, Jan 09, 2003 at 05:45:00PM -0800, Bill Medland wrote: > On January 9, 2003 03:12 pm, Dimitrie O. Paun wrote: > > On January 9, 2003 07:08 pm, Bill Medland wrote: > > > + if (!tpinfo->chanbuf) { > > > + ERR("tpinfo has no Rpc Channel Buffer\n"); > > > + return 0; > > > + } > > > > Is this expected behaviour? If so, there's no need for the ERR msg. > > If not, there's no need for the test, we need to fix the root cause... > You are, of course, quite correct. > I don't know what the expected behaviour is; all I know is that dereferncing > the null pointer isn't. > If someone actually understands all that proxy stuff then maybe they can do > something about it. > If not then I guess it is destined to languish unfixed. I vaguely remember this happening for inter-thread COM, I did not come around to debug it yet. "return E_FAIL;" might be more appropriate too. Ciao, Marcus

Jan. 10, 2003

[Fwd: Re: getting started]

by Glen Kaukola

Dimitrie O. Paun wrote: > Compiling under the SDK using MS tools gives us little value. We already > know that works. If you don't want to spend the cash on MSVC (and not make > MS any richer :)), and are willing to invest some time into it, I suggest > the following path: > 1. Get the latest mingw 2.0 distribution from http://www.mingw.org > 2. Modify the makefiles that come in the book to work with GNU make, > and the mingw tool chain. Make sure you use forward slashes (/)! :) > 3. Build on Windows with your newly created Makefiles, and verify > that everthing runs under Windows just fine. > 4. If you feel like it, document what steps you took to convert the > makefiles. Maybe we'll put that on the Winelib page, to help > others in the future. > 5. Take the exact same Makefiles you used under Windows, change > 3 lines in them (CC=winegcc, CXX=wineg++, WINDRES=wrc), and > try to compile under Linux. Use the latest Wine tree, and > you should have native Linux apps. If you get errors in this > step, they are Wine error, please report them, and let's try > to fix them. This is the real value of this exercise. > 6. Once everything builds, run the apps, and make sure they run fine. > If they have problems, and you feel brave, let the debugging begin! > > Welcome to the team! > Well I've gotten MinGW and sorta learned my way around it. But now, my problem is that neither of my windows programming books has makefiles of any sort. All they have is C++ code. So maybe I should go with my original plan of compiling stuff with visual studio and seeing if it runs under wine. Or do you have any other suggestions?

Jan. 10, 2003

Re: Expected name, id, length or ordinal error

by Dimitrie O. Paun

On January 10, 2003 02:12 am, John Westerman wrote: > My hellotest.spec looks like this: > > name hellotest > > type win32 > > mode guiexe > > init WinMain > > rsrc hellotest.res > > > > import kernel32.lib > > import user32.lib <- line of failure None of this stuff resides in the .spec file anymore! I'm not sure if winemaker is update to generate spec files according to the latest and greatest. What version are you using BTW? You should be using HEAD, if you can work with CVS. -- Dimi.

Jan. 10, 2003

Re: PATCH - Define needed flags when building for Mingw

by Steven Edwards

--- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > On January 10, 2003 12:01 am, Steven Edwards wrote: > > + CFLAGS="=$CFLAGS -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK" ; > > Why do you need these defines? In particular, isn't the compiler > defining __MINGW__ and _WINDOWS? I started using them a while back on one of the mingw releases and have just always kept them out of habit. I thought it was supposed to define them but around the mingw-gcc 2.95.3 release It didnt do one of them (_WINDOWS) I think. When I first started wine development and was playing with the stuff Patrik did for MS_VC anything that both MS_VC and Mingw could use I always #ifdef'd as _WINDOWS. I guess I should have checked to see if this was still needed so yeah its way wrong. BRAIN FART. Anyway disregard this anyway because I forgot to test this patch after my ./configure was done. Now I'm ending up with gcc -c -I. -I. -I../include -I../include =-g -O2 -Wall -mpreferred-stack-bounda ry=2 -gstabs+ -D__MINGW__ -D_WINDOWS -DWINE_NOWINSOCK -D__WINESRC__ -D_REENTRAN T -o cptable.o cptable.c gcc.exe: cannot specify -o with -c or -S and multiple compilations I really only need a patch that adds "-DWINE_NOWINSOCK" to the CFLAGS if Mingw isnt broken. If I need anything else it can be added later. Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Jan. 10, 2003