February 2002 - Wine-devel - list.winehq.org

RE: Wine compile on MSVC?
by Patrik Stridvall 07 Feb '02

07 Feb '02

> Is this correct that tests are made to compile Wine on MSVC? Only on a small scale, nothing really serious yet. > What good > is this for? I thought Wine should be an emulation of windows > code on a > Unix platform, what good is it to run Windows on Windows? > > Just being curious. :) Well. I qoute myself: "It would be quite nice to have all non core DLL compiling and working and with winetest ported. Then you could just run winetest through the debugger and be able to set breakpoint and step through the code in Visual Studio in order to get all to tests to run properly. :-)" Also note that this would make it possible to debug each dll in an enviroment where all other DLLs except the DLL tested were real Windows DLLs.

2 1

Wine compile on MSVC?
by Gerhard W. Gruber 07 Feb '02

07 Feb '02

Is this correct that tests are made to compile Wine on MSVC? What good is this for? I thought Wine should be an emulation of windows code on a Unix platform, what good is it to run Windows on Windows? Just being curious. :)

1 0

RE: Header files not present on Windows
by Patrik Stridvall 07 Feb '02

07 Feb '02

> >Eventually I guess that the non-core DLL:s never should call any > >non Windows functions at all and the core DLL:s are not really useful > >to compile and run under Windows anyway. > > Well I have only played with the shell32.dll and in any file > in there except > "shelllink.c" removing "unistd.h" entirely had no negative > effect whatsoever. > This means to me that it is not needed at all. The use of > fork(), execvp(), and > waitpid() in "shelllink.c" however seems to require the > "unistd.h" header. > > I'm not sure if shell32 should be considered a core DLL. It > seems to me > rather not. shell32 is not really a core DLL eventhough it is a borderline case since some functionallity might want to intergrate with the desktop. However, it definitly should compile under Windows at least with limited functionallity. > The desired operation could be possibly achieved > with the use > of Windows kernel functions as well. Possibly, but it looks a little Wine specific to me. I'm not 100% sure what the code does. Anyway, we could always choose to exclude that code on Windows. It would be useful to run test on the rest of the functionallity in any case.

1 0

(FWD) Announcing wineconf 2002
by Ove Kaaven 07 Feb '02

07 Feb '02

I received this today... it seems Lindows seem to want to host a Wine conference. I noticed that they misspelled Alexandre's name and email address, though they claim to work with him. Since this is supposed to be an open conference anyway, and it's not a secret (most of the mail is just a straight dump of the webpage they link to anyway), I decided to forward it to wine-devel (but without the HTML). ---------- Forwarded message ---------- Date: Tue, 5 Feb 2002 14:21:18 -0800 From: Cheryl Schwarzman <cheryl(a)lindows.com> To: uczekalla(a)codeweavers.com, andi(a)rhlx01.fht-esslingen.de, andrew(a)transgaming.com, aric(a)codeweavers.com, bon(a)elektron.ikp.physik.tu-darmstadt.de, brianv(a)ski-copper.com, dimi(a)cs.toronto.edu, dmitry(a)codeweavers.com, ekohl(a)codeweavers.com, eric.pouech(a)wanadoo.fr, fgouget(a)free.fr, franciosj(a)macadamian.com, galberte(a)neo.lrun.com, gav(a)transgaming.com, gerard.patel(a)asi.fr, hdavies(a)codeweavers.com, james(a)macadamian.com, jasonfilby(a)yahoo.com, jefft(a)xandros.com, juilliard(a)codeweavers.com, jwhite(a)codeweavers.com, lionel.ulmer(a)free.fr, marcus(a)jet.franken.de, mike_mccormack(a)start.com.au, ovek(a)transgaming.com, ps(a)leissner.se, ridgway(a)winehq.com, sanderv(a)xs4all.nl, tephane(a)macadamian.com Subject: Announcing wineconf 2002 Announcing wineconf 2002 We believe 2002 is the year WINE really breaks through to have a major impact on computing. Many of you have had the vision and dedication long before Lindows.com was around. And it's all of you who deserve the credit. As a small token of our gratitude, we want to do our best to host the first conference dedicated to WINE called wineconf. As the host, Lindows.com will pay the cost of putting on the conference including venue, food and other necessary arrangements. The agenda and speakers will be the members of the WINE community. It will be a two day event on Friday and Saturday where new ideas can be shared, new connections made, and you can hear from the best and brightest pushing the WINE initiative forward. We have dubbed the event wineconf and it will be open to all who wish to attend. We don't expect a large crowd given the highly technical focus. Working with lead WINE mind, Alexandre Juilliard, we have come up with a list of people whose historic contributions to WINE deserve extra recognition. To this group, we're making a special offer by picking up their airfare to and from San Diego for this event. This is Lindows.com way of thanking those who have made contributions in the past to get WINE to the level it is at. We will notify you personally, if you are in this list. If you are not on this list, you are still welcome to attend with no registration fee, but you will be responsible for your own transportation. Hotel costs will range from $75-125 per night. The agenda will be sent out several weeks before the conference outlining the topics and speakers. We will be working with attendees and speakers to ensure we touch all the areas of interest. wineconf will be held in San Diego, CA on March 15th-16th, 2002. We selected San Diego for two primary reasons. First, because it's our home town we can keep the costs down on the venue, transportation, computer facilities, etc. Like all startups (that weren't born in 1999!), we have a finite budget we're trying to stretch as far as possible. Secondly, since WINE is a worldwide effort there's no ideally centralized location, so we selected a place that should be nice and warm in March. (San Diego is 25 minutes south of LA by plane or 1.5 hours by car.) The specific agenda will be forthcoming as we work with WINE contributors to get their input and guidance. You can register online by going here: www.lindows.com/wineconf We hope you can make it! Registration Form: First Name: Last Name: Email: Company: Address: City: State: Zip: Country: Phone: Topics You Would Like To See Discussed: Speakers You Would Like To Hear From: ------------------------------------------------------------------------ Optional Part (for those we will be paying for air transportation) Because of your past contributions to WINE, Lindows.com is offering to arrange and pay for airfare from a nearby major metropolitan area to San Diego for you to attend wineconf 2002. This offer is non-transferable. Your flight would depart on Thursday, March 14th and return on Sunday, March 17th. To qualify, by February 13th, 2002, you must: 1. Register online at http://lindows.com/wineconf (enter your name for the "Invitation Code"). 2. Send an email to cheryl(a)lindows.com with the below cancellation payment information. You will need to agree that if you do not attend that you will pay for all costs incurred by Lindows.com related to airfare arrangements. Your credit card will ONLY be billed if you do not attend after saying that you will. Hope to see you in San Diego! ------------------------------------------------------------------------ NOTE: In addition to registering at http://lindows.com/wineconf, we must receive the below information no later than February 13th, 2002 (e-mail this to cheryl(a)lindows.com) After that date, this offer is no longer valid. I agree to attend wineconf 2002 March 14-15th in San Diego and understand that Lindows.com will be paying for my airfare. If I do not attend, I understand that I will have to pay for the costs incurred in the scheduling of this airfare. <"yes I agree." and your name here> Exact name on passport or ID: <put your name here> Nearest Major Airport: <put your city and country here> Credit Card Type: <card type> Credit Card Number: <card number> Credit Card Expiration Date: <exp date> Please remember to travel with picture ID, passport and VISA if required. Further information can be found here http://www.lindows.com/wineconf

7 7

RE: Header files not present on Windows
by Rolf Kalbermatter 07 Feb '02

07 Feb '02

Patrik Stridvall <ps(a)leissner.se> writes: >> Patrik Stridvall <ps(a)leissner.se> writes: >> >> > Hmm. I'm note sure I like making unistd.h >> > an optional header but then few part of >> > Wine should include it anyway so perhaps >> > it doesn't matter. >> >> The question is whether you can build without it. If the needed >> definitions are provided by other includes then it's fine to make it >> optional; but if the code doesn't compile without it then there's no >> point in having a check. > >Yes and in many cases it did work without unistd.h, but maybe that >is because it really wasn't needed at all. > >In some case it might have worked because some of the functions in >unistd.h is defined else where in Windows and in some case we might >get it to work by including needed files. > >Of course in such cases we probably should fix Wine and >include that other header exclusively instead of unistd.h. > >Anyway, I just experimented a little trying to get Wine to compile >under Windows. I'm not really sure exacly what to do. > >Eventually I guess that the non-core DLL:s never should call any >non Windows functions at all and the core DLL:s are not really useful >to compile and run under Windows anyway. Well I have only played with the shell32.dll and in any file in there except "shelllink.c" removing "unistd.h" entirely had no negative effect whatsoever. This means to me that it is not needed at all. The use of fork(), execvp(), and waitpid() in "shelllink.c" however seems to require the "unistd.h" header. I'm not sure if shell32 should be considered a core DLL. It seems to me rather not. The desired operation could be possibly achieved with the use of Windows kernel functions as well. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citeng.com Netherlands mailto:rolf.kalbermatter(a)citeng.com

1 0

Date format
by info2000＠telecable.es 07 Feb '02

07 Feb '02

Hello, IŽm running a windows aplication made on Builder C, and when I execute de program with Wine, I receive an error message, reference to the date format, I get the year correctly, but the rest of date content is ="0", for example 01 January 2002 at 13:20:15 is= 17/20/02 00:00:00 can you help me to fixing this problem? thanks from spain. Jose. --------------------------------------------- Este mensaje fue enviado utilizando el servicio de correo-web de: http://www.telecable.es

2 1

RE: Some more MSVC fixes
by Roger Fujii 07 Feb '02

07 Feb '02

From: Patrik Stridvall <ps(a)leissner.se> wrote: > > Dimitrie O. Paun wrote: > > > On Wed, 6 Feb 2002, Steven Edwards wrote: > > > > > > Any other interesting compilers? Maybe the Solaris one? What about > > > headers? We already have 4 * 4 * 3 = 48 combinations. > > I tried briefly with the Solaris compiler, but there seemed > > to be enough problems that I gave up. I really don't remember what they > > were. > Well, the older versions for one doesn't support __stdcall. > I'm don't know about the newer. well, the current version doesn't seem to run under solx86 even with the gcc. Not certain what changed. Trying to figure it out right now (if only cvs.winehq.org would let me in...) > > It is probably a moot point now, since Sun has announced that there > > will be no Solaris 9 X86. > AFAIK they have only said that Solaris 9 SPARC will be released > before Solaris 9 X86. Of course it is not a good sign if you > read between the lines but still. well, technically, they said that x86 development work has stopped, but they can change their minds. Effectively, they "laid off" solx86, but added "we may ask you back..." Not promising at all.... -r

1 0

RE: Some more MSVC fixes
by Patrik Stridvall 07 Feb '02

07 Feb '02

> Dimitrie O. Paun wrote: > > On Wed, 6 Feb 2002, Steven Edwards wrote: > > > > Any other interesting compilers? Maybe the Solaris one? What about > > headers? We already have 4 * 4 * 3 = 48 combinations. > > I tried briefly with the Solaris compiler, but there seemed > to be enough > problems that I gave up. I really don't remember what they > were. Well, the older versions for one doesn't support __stdcall. I'm don't know about the newer. > It is > probably a moot point now, since Sun has announced that there > will be no > Solaris 9 X86. AFAIK they have only said that Solaris 9 SPARC will be released before Solaris 9 X86. Of course it is not a good sign if you read between the lines but still.

1 0

Re: X connection to :0.0 broken (explicit kill or server shutdown).
by Sylvain Petreolle 06 Feb '02

06 Feb '02

Bonjour, Je rencontre un problème persistant avec wineconsole. Dès qu'il est chargé le système ralentit et wine grandit en mémoire jusqu'à saturation de la mémoire swap.(256M ram physique + 208M swap) Le message "fixme:bitmap:CreateCompatibleBitmap got bad width 1939840 or height 2457900" me fait penser que wineconsole se configure mal. Y a t il un moyen de spécifier une taille de fenêtre ? En regardant le code source (registry.c) jai essayé de mettre la proprété WindowSize à une valeur très petite, mais le lancement en mode debugmsg +reg montre que les valeurs sont ignorées par le programme. Comme vous etes en partie l'auteur de ce programme, je pense trouver un peu de répondant... --- Sylvain Petreolle <spetreolle(a)yahoo.fr> a écrit : > Hi, > > Using wineconsole to try a command line program > like ftp.exe (runs fine whithout wineconsole), > it appears that wineconsole slowdowns the system > and use incredible amounts of memory. > > These are the messages that appear on the wine > command > line : > > fixme:bitmap:CreateCompatibleBitmap got bad width > 1939840 or height 2457900, please look for reason > fixme:console:SetConsoleCtrlHandler (0x1001dc5,1) - > no > error checking or testing yet > fixme:bitmap:CreateCompatibleBitmap got bad width > 1939840 or height 2457900, please look for reason > > then i got the shell prompt, look like the process > had > end up. > (the processes didn't end up of course). > i must kill the processes (the 2 windows desktops > displayed are complete empty and > do not close when asked to close) > > Running it with --debugmsg +relay, I saw that wine > took a long time when running x11drv.SelectObject. > and the last line in the debug text is > X connection to :0.0 broken (explicit kill or server > shutdown). > (this is before I do killall wineconsole wine). > > > > ___________________________________________________________ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et > en français ! > Yahoo! Mail : http://fr.mail.yahoo.fr > ATTACHMENT part 2 application/x-bzip2 name=wineconsole_debug.log.bz2 ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.fr

1 0

Re: Some more MSVC fixes
by Dimitrie O. Paun 06 Feb '02

06 Feb '02

On Tue, 5 Feb 2002, Patrik Stridvall wrote: > I have finally tried to compile Wine with MSVC. > Eventhough I had to do some hack on the whole > it compiled quite well. Great. On a slightly related note, is it possible that we compile Wine with the MS headers? What would it take to do that? If we could, we would have one more degree of freedom: Platform Compilers BinFmt Headers -------- --------- ------ ------- Linux gcc ELF Wine *BSD MSVC PE MS Solaris Borland ReactOS(?) Cygwin Esentially, most of the above possible cobinations should work (except, of course Windows-base compilers and ELF). If we get this level of portability, would be nice to set an automatic compile farm which tries all the possible combinations, and reports problems early, so they get fixed. -- Dimi.

3 3