Hello: Who has the document about COM?? The websit has information about COM,But it isn't detailed. Thanks very much! ----- Original Message ----- From: wine-devel-request@winehq.com To: wine-devel@winehq.com Sent: Friday, January 03, 2003 10:03 AM Subject: wine-devel digest, Vol 1 #1558 - 19 msgs
Send wine-devel mailing list submissions to wine-devel@winehq.com
To subscribe or unsubscribe via the World Wide Web, visit http://www.winehq.com/mailman/listinfo/wine-devel or, via email, send a message with subject or body 'help' to wine-devel-request@winehq.com
You can reach the person managing the list at wine-devel-admin@winehq.com
When replying, please edit your Subject line so it is more specific than "Re: Contents of wine-devel digest..."
Today's Topics:
- Re: __WINE__ vs. __WINESRC__ (Dimitrie O. Paun)
- Re: argv[0] needs to be an absolute path (Dan Kegel)
- Re: tchar fixes: _tcs{dup,icmp} (Dimitrie O. Paun)
- Re: Fixing include quotes (was: Re: conformance test for
ShellExecute) (Alexandre Julliard)
- Re: tchar fixes: _tcs{dup,icmp} (Alexandre Julliard)
- Re: __WINE__ vs. __WINESRC__ (Alexandre Julliard)
- Re: Fixing include quotes (was: Re: conformance test for
ShellExecute) (Dimitrie O. Paun)
- Re: Make RECT === RECTL, fix compile warnings, use uniform format
(Alexandre Julliard)
- Re: Fixing include quotes (was: Re: conformance test for
ShellExecute) (Dan Kegel)
- Re: Fixing include quotes (was: Re: conformance test for
ShellExecute) (Dimitrie O. Paun)
- Fixing SUBLANG_NEUTRAL (was: Re: Fixing include quotes (was: Re: conformance test for ShellExecute)) (Shachar Shemesh)
- Re: Fixing SUBLANG_NEUTRAL (was: Re: Fixing include quotes (was: Re:
conformance test for ShellExecute)) (Dimitrie O. Paun)
- regression with CFLAGS=-g (Shachar Shemesh)
- wine.m4 install bug (Enrico Horn)
- Re: wine.m4 install bug (Alexandre Julliard)
- Avoid some tests (=?iso-8859-1?q?Sylvain=20Petreolle?=)
- Re: RFH: ICON statement (Dimitrie O. Paun)
- Re: wineboot - initial version
(=?iso-8859-1?q?Sylvain=20Petreolle?=)
--__--__--
Message: 1 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Alexandre Julliard julliard@winehq.com Subject: Re: __WINE__ vs. __WINESRC__ Date: Thu, 2 Jan 2003 12:02:35 -0500 Cc: Francois Gouget fgouget@free.fr, Wine Devel wine-devel@winehq.com
On January 2, 2003 12:30 pm, Alexandre Julliard wrote:
It doesn't really matter, just pick the one you prefer.
I know, but I was hoping people had better suggestions :) I like __WINESRC__ the best (but that doesn't mean much <g>), so unless people have a better idea, that's going to be it.
Sure, we can do the rename first.
Probably a script to do it would be best, no?
No, these should be removed. The same effect can be achieved by defining COM_NO_WINDOWS_H in the C files that use the include.
What about defining COM_NO_WINDOWS_H globally in Wine?
-- Dimi.
--__--__--
Message: 2 Date: Thu, 02 Jan 2003 10:27:43 -0800 From: Dan Kegel dank@kegel.com To: Sylvain Petreolle spetreolle@yahoo.fr CC: Wine Devel wine-devel@winehq.com Subject: Re: argv[0] needs to be an absolute path
"sometimes" == "if the program was invoked with a relative path"
BTW the one-line patch I submitted seems to just preserve the D: in the example I gave. This is good enough to make my test case work, but won't fix all uses, I think.
- Dan
Sylvain Petreolle wrote:
What do you mean by "sometimes" ?
outputs an absolute path on Windows, but sometimes outputs a relative path on Wine. This causes the commandline $ wine d:setup to fail to find its files properly if it uses the basename of argv[0]. One example of this is msvc4.0 (although it only tries this if an earlier method fails, so there's another bug lurking).
I am about to submit a one-line patch to fix this to wine-patches. (If I weren't a wimp, I'd figure out a way to submit a regression test, too, although it'd be a strange one; most of our tests don't need to invoke Wine itself from the Unix commandline!)
The same problem exists for programs launched from other wine programs, e.g. from inside wcmd. That's another code path, and I couldn't find a one-line fix for that one.
- Dan
-- Dan Kegel Linux User #78045 http://www.kegel.com
--__--__--
Message: 3 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Alexandre Julliard julliard@winehq.com Subject: Re: tchar fixes: _tcs{dup,icmp} Date: Thu, 2 Jan 2003 12:23:52 -0500 Cc: Francois Gouget fgouget@free.fr, wine-devel@winehq.com
On January 2, 2003 12:38 pm, Alexandre Julliard wrote:
tchar.h should not depend on msvcrt IMO, at least not in ASCII mode, so it should use the normal function names without underscores. It's not 100% compatible, but it should still do the right thing, both with and without msvcrt.
Sounds good. But since we are on the subject, here's another thing that's been troubling me: we have 3 flavors of the crt to worry about: glibc, msvcrt, and cygwin libc (let's call it cygcrt). To be honest, I haven't looked in detail at cygcrt but I guess it's a derivative of glibc (as it is used to port Unix stuff). However, it has stuff such as io.h which is not present in Unix, and is reminiscent of msvcrt.
When compiling stuff on Windows with gcc (mingw), it links by default with cygcrt if available. If the -mno-cygwin option is used, or cygwin is not available, it links against crtdll. Of course, the appropriate headers are used automatically.
For winegcc, I mapped the -mno-cygwin option to use msvcrt, otherwise we use the native glibc. This is the closest mapping I could find, and it works fairly well, with a few caveats such as the missing io.h in glibc.
Anyhow, and ideas on how to deal with all this?
-- Dimi.
--__--__--
Message: 4 To: "Patrik Stridvall" ps@leissner.se Cc: dpaun@rogers.com, wine-devel@winehq.com, "Dan Kegel"
Subject: Re: Fixing include quotes (was: Re: conformance test for
ShellExecute)
From: Alexandre Julliard julliard@winehq.com Date: 02 Jan 2003 10:31:37 -0800
"Patrik Stridvall" ps@leissner.se writes:
I think it is better than Alexandre runs winapi_cleanup --include-quotes himself if he thinks it does the correct things. If not please inform me what the problem is.
In my tree, the patch is over 800k.
I'm not sure there's much point in fixing all the C files. It works fine the way it is now, the only thing that we need the change is the exported headers.
-- Alexandre Julliard julliard@winehq.com
--__--__--
Message: 5 To: dpaun@rogers.com Cc: Francois Gouget fgouget@free.fr, wine-devel@winehq.com Subject: Re: tchar fixes: _tcs{dup,icmp} From: Alexandre Julliard julliard@winehq.com Date: 02 Jan 2003 10:46:35 -0800
"Dimitrie O. Paun" dpaun@rogers.com writes:
For winegcc, I mapped the -mno-cygwin option to use msvcrt, otherwise we use the native glibc. This is the closest mapping I could find, and it works fairly well, with a few caveats such as the missing io.h in glibc.
Anyhow, and ideas on how to deal with all this?
I don't think cygwin is really a big issue, it should be mostly Unix compatible, and it shouldn't be hard to work around the problems if any appear. I don't think we need any special infrastructure for that.
-- Alexandre Julliard julliard@winehq.com
--__--__--
Message: 6 To: dpaun@rogers.com Cc: Francois Gouget fgouget@free.fr, Wine Devel wine-devel@winehq.com Subject: Re: __WINE__ vs. __WINESRC__ From: Alexandre Julliard julliard@winehq.com Date: 02 Jan 2003 10:45:07 -0800
"Dimitrie O. Paun" dpaun@rogers.com writes:
Sure, we can do the rename first.
Probably a script to do it would be best, no?
I don't think there are that many, a patch would be fine.
No, these should be removed. The same effect can be achieved by defining COM_NO_WINDOWS_H in the C files that use the include.
What about defining COM_NO_WINDOWS_H globally in Wine?
That's a possibility too. I think I'd prefer to do it in the individual C files, but I haven't looked how many would need it, so maybe it's too much work (though Patrik can probably come up with a magic script to do it...)
-- Alexandre Julliard julliard@winehq.com
--__--__--
Message: 7 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Alexandre Julliard julliard@winehq.com, "Patrik Stridvall" ps@leissner.se Subject: Re: Fixing include quotes (was: Re: conformance test for
ShellExecute)
Date: Thu, 2 Jan 2003 12:41:34 -0500 Cc: wine-devel@winehq.com, "Dan Kegel" dank@kegel.com
On January 2, 2003 01:31 pm, Alexandre Julliard wrote:
I'm not sure there's much point in fixing all the C files. It works fine the way it is now, the only thing that we need the change is the exported headers.
Exported headers do need fixing, to avoid hard to detect errors. While the C files work the way they are now, they are confusing for newcomers. I think our current trend of doing things as standard as possible, is a Good Thing(TM). Trying to violate the Principle of Least Surprise as little as possible can only be good. Moreover, current source code is many times used as a template by other contributors, which provides even more incentive to have current code as good/clean as possible <g>.
Bottom line, since the change is free (the work is done by a script), and there is little chance of conflicts with other patches (it touches only the include statements), I think it's worth doing now.
-- Dimi.
--__--__--
Message: 8 To: dpaun@rogers.com Cc: Dan Kegel dank@kegel.com, Wine Devel wine-devel@winehq.com Subject: Re: Make RECT === RECTL, fix compile warnings, use uniform format From: Alexandre Julliard julliard@winehq.com Date: 02 Jan 2003 10:49:27 -0800
"Dimitrie O. Paun" dpaun@rogers.com writes:
As for the new debug* functions, most nontrivial ones are not that small. Do you want them defined as static inline in wine/debug.h, or exported from ntdll as the other ones? In fact, why not create a helper DLL (winedebug) that holds all of this, and that can be used on Windows as well, when we port most of our stuff over?
IMO this would be a mechanism to use only for trivial functions that can be put inline; more complex ones should be implemented in their respective dlls. We definitely don't want a big centralized module that dumps all known structures.
-- Alexandre Julliard julliard@winehq.com
--__--__--
Message: 9 Date: Thu, 02 Jan 2003 11:07:51 -0800 From: Dan Kegel dank@kegel.com To: dpaun@rogers.com CC: Alexandre Julliard julliard@winehq.com, Patrik Stridvall ps@leissner.se, wine-devel@winehq.com Subject: Re: Fixing include quotes (was: Re: conformance test for
ShellExecute)
Dimitrie O. Paun wrote:
Bottom line, since the change is free (the work is done by a script), and there is little chance of conflicts with other patches (it touches only the include statements), I think it's worth doing now.
There is one downside: it may make old patches harder to apply, and it may make it harder to sync with other trees (e.g. rewind).
On the other hand, encouraging people to use the tool to tidy up any files they're working on makes patches harder to read, as it mixes formatting changes with real changes.
Six of one, half dozen of another...
- Dan
-- Dan Kegel Linux User #78045 http://www.kegel.com
--__--__--
Message: 10 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Dan Kegel dank@kegel.com Subject: Re: Fixing include quotes (was: Re: conformance test for
ShellExecute)
Date: Thu, 2 Jan 2003 12:54:35 -0500 Cc: Alexandre Julliard julliard@winehq.com, Patrik Stridvall ps@leissner.se, wine-devel@winehq.com
On January 2, 2003 02:07 pm, Dan Kegel wrote:
There is one downside: it may make old patches harder to apply, and it may make it harder to sync with other trees (e.g. rewind).
In general yes, but I don't think it's a big problem in this particular case where _only_ #include statements are touched. These are seldomly changed anyway. As for other trees, all of Patrik work is BSD AFAIK, so everybody can run the script on their trees as well.
-- Dimi.
--__--__--
Message: 11 Date: Thu, 02 Jan 2003 23:05:42 +0200 From: Shachar Shemesh wine-devel@sun.consumer.org.il To: dpaun@rogers.com CC: Dan Kegel dank@kegel.com, Alexandre Julliard julliard@winehq.com, Patrik Stridvall ps@leissner.se, wine-devel@winehq.com Subject: Fixing SUBLANG_NEUTRAL (was: Re: Fixing include quotes (was: Re: conformance test for ShellExecute))
While we are on the subject of api_check and such, how about changing SUBLANG_NEUTRAL in all non-neutral languages to SUBLANG_DEFAULT, as it should be?
Sh.
Dimitrie O. Paun wrote:
On January 2, 2003 02:07 pm, Dan Kegel wrote:
There is one downside: it may make old patches harder to apply, and it may make it harder to sync with other trees (e.g. rewind).
In general yes, but I don't think it's a big problem in this particular case where _only_ #include statements are touched. These are seldomly changed anyway. As for other trees, all of Patrik work is BSD AFAIK, so everybody can run the script on their trees as well.
--__--__--
Message: 12 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Shachar Shemesh wine-devel@sun.consumer.org.il Subject: Re: Fixing SUBLANG_NEUTRAL (was: Re: Fixing include quotes (was:
Re: conformance test for ShellExecute))
Date: Thu, 2 Jan 2003 15:21:32 -0500 Cc: Dan Kegel dank@kegel.com, Alexandre Julliard julliard@winehq.com, Patrik Stridvall ps@leissner.se, wine-devel@winehq.com
On January 2, 2003 04:05 pm, Shachar Shemesh wrote:
While we are on the subject of api_check and such, how about changing SUBLANG_NEUTRAL in all non-neutral languages to SUBLANG_DEFAULT, as it should be?
Are you volunteering? :) If it's supposed to be this way, a patch would be most appreciated, me thinks <g>
-- Dimi.
--__--__--
Message: 13 Date: Fri, 03 Jan 2003 00:02:01 +0200 From: Shachar Shemesh wine-devel@sun.consumer.org.il To: Wine Devel wine-devel@winehq.org Subject: regression with CFLAGS=-g
Hi,
There is a regression when compiling wine with CFLAGS=-g. The latest CVS throws an unhandled exception when exiting notepad. When notepad is compiled with CFLAGS=-g -O2 (the defaults), there is no crash even if the rest of the libraries are compiled with -g. This also happens on Wine 20021216.
Any idea?
Shachar
--__--__--
Message: 14 From: Enrico Horn farmboy1@subdimension.com Reply-To: farmboy1@subdimension.com To: wine-devel@winehq.com Subject: wine.m4 install bug Date: Thu, 2 Jan 2003 23:25:35 +0100
Hi, When installing the wine.m4 macro file you cant just use the <prefix>/share/aclocal dir of wine as destination. You need to use the <prefix>/share/aclocal dir of automake as this is the only path where the m4 files will be found.
Ciao Enrico farmboy1@subdimension.com
--__--__--
Message: 15 To: farmboy1@subdimension.com Cc: wine-devel@winehq.com Subject: Re: wine.m4 install bug From: Alexandre Julliard julliard@winehq.com Date: 02 Jan 2003 16:07:28 -0800
Enrico Horn farmboy1@subdimension.com writes:
When installing the wine.m4 macro file you cant just use the <prefix>/share/aclocal dir of wine as destination. You need to use the <prefix>/share/aclocal dir of automake as this is the only path where the m4 files will be found.
No, Wine shouldn't install things outside of its own prefix. If you install Wine in a non-standard directory then you need to tell autoconf about it with the -I option.
-- Alexandre Julliard julliard@winehq.com
--__--__--
Message: 16 Date: Fri, 3 Jan 2003 01:39:58 +0100 (CET) From: =?iso-8859-1?q?Sylvain=20Petreolle?= spetreolle@yahoo.fr Subject: Avoid some tests To: wined wine-devel@winehq.com
Having problem with Nvidia driver when making tests, I disabled opengl. All tests pass.
If I reenable opengl, dsound test will fail (crash to debugger). I tried to touch dsound.ok, but test is launched after a 'make testclean' so it doesn't work as expected.
Do someone have tips ? Don't want to edit the Makefile by hand to avoid
this.
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus in Matrix, chapter 15.
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! Yahoo! Mail : http://fr.mail.yahoo.com
--__--__--
Message: 17 From: "Dimitrie O. Paun" dpaun@rogers.com Reply-To: dpaun@rogers.com Organization: DSSD Software Inc. To: Mehmet YASAR myasar@free.fr Subject: Re: RFH: ICON statement Date: Thu, 2 Jan 2003 19:02:55 -0500 Cc: Wine Devel wine-devel@winehq.com
On January 2, 2003 12:37 pm, Mehmet YASAR wrote:
I just tested icon ressource beginning with weird characters like "!icon" or "-icon" and that works (tested under VC++/sp5).
Cool, thanks. I've sent a patch in to support them. BTW, are these chars also accepted in filenames?
-- Dimi.
--__--__--
Message: 18 Date: Fri, 3 Jan 2003 03:01:28 +0100 (CET) From: =?iso-8859-1?q?Sylvain=20Petreolle?= spetreolle@yahoo.fr Subject: Re: wineboot - initial version To: wined wine-devel@winehq.com
Trying wineboot, I realize that it deletes wininit.ini. Real wininit.ini doesn't do this. It renames the file as wininit.bak. Could this updated or should I submit a small patch later ? (or do you disagree ?)
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus in Matrix, chapter 15.
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! Yahoo! Mail : http://fr.mail.yahoo.com
--__--__--
wine-devel mailing list - wine-devel@winehq.com http://www.winehq.com/mailman/listinfo/wine-devel
End of wine-devel Digest