As winecfg gets better and better I think it's time to consider making
it actually change the config file. I made a patch for it, but it's a
work in progress, and not ready for general use. I don't expect you to
commit it, so I sent it here for discussion.
I don't think that this needs a complex m
This patch adds GetScrollBarInfo to user32.spec, but adds no
implementation...
Here's a temporary fix for those wondering why the CVS won't compile
until the rest of Vitaly's scrollbar patch is committed.
Mike
Alexandre Julliard wrote:
ChangeSet ID: 15265
CVSROOT:/opt/cvs-commit
Modul
On Fri, Jan 07, 2005 at 10:46:51PM +0100, Tobias Burnus wrote:
> Hello,
>
> Crestez Leonard wrote:
> >+if [ -z $WINEPREFIX ]
> >+then
> While my bash accepts this, Tru64 UNIX's POSIX shell does not.
> Please use "$WINEPREFIX" instead.
And while you are at it, you could also replace those [ ] used
Hello,
Crestez Leonard wrote:
+if [ -z $WINEPREFIX ]
+then
While my bash accepts this, Tru64 UNIX's POSIX shell does not.
Please use "$WINEPREFIX" instead.
Tobias
Eric Pouech wrote:
Could you give any hints as to how to configure GDB with 'stabs in
PE' support? The only reference I could find in the GDB documentation
is:
"6.4.5 PE
Windows 95 and NT use the PE (/Portable Executable/) format for their
executables. PE is basically COFF with additional heade
Bryce McKinlay a écrit :
Eric Pouech wrote:
Bryce McKinlay a écrit :
I'm trying to debug a windows .exe built with mingw using wine, but
winedbg seems to have problems reading stabs from the mingw-built
binary. My goal is to be able to debug a cross-compiled, native Java
(GCJ) application, but e
Juan Lang wrote:
Style point: (*pointer).whatever is written a bit more easily as
pointer->whatever. That'd make your new patch a good bit more readable.
--Juan
__
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/
On January 7, 2005 09:04 am, Mike Hearn wrote:
> On Fri, 07 Jan 2005 08:46:25 -0800, Juan Lang wrote:
> > Style point: (*pointer).whatever is written a bit more easily as
> > pointer->whatever. That'd make your new patch a good bit more readable.
>
> Are they even equivalent? My impression was th
On Fri, 07 Jan 2005 08:46:25 -0800, Juan Lang wrote:
> Style point: (*pointer).whatever is written a bit more easily as
> pointer->whatever. That'd make your new patch a good bit more readable.
Are they even equivalent? My impression was that (*pointer).whatever would
make a temporary copy on th
Vitaly Lipatov <[EMAIL PROTECTED]> writes:
> --- scroll.c 8 Dec 2004 18:06:15 - 1.3
> +++ dlls/user/scroll.c4 Jan 2005 14:27:08 -
> @@ -27,7 +27,7 @@
> * the specification mentioned above.
> * If you discover missing features, or bugs, please note them below.
> *
> - *
Style point: (*pointer).whatever is written a bit more easily as
pointer->whatever. That'd make your new patch a good bit more readable.
--Juan
__
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/
> This can't do everything. It protects against return-to-libc style
> attacks but there are other stack based attacks that it doesn't work for
> (if I remember correctly).
I.e. for C++ apps you could instead change the implicit this argument of the
caller, for example, to point to a made-up inst
Crestez and I talked about this patch on #winehackers, and there are a few
things that need to be changed (let's ignore the formatting changes here):
- There was code to avoid a crash when the desktop value read from the
registry doesn't have an x in it for some reason (yes this does happen)
b
Rob Shearman wrote:
Dripple wrote:
Hi all,
I'm a newbie in wine using and wine developpement. I just need
information about comctl32.dll and commctrl.dll.
I'm trying to have this app
(http://appdb.winehq.org/appview.php?appId=1485&versionId=2451) working.
In fact, it works. But only using native co
Dripple wrote:
Hi all,
I'm a newbie in wine using and wine developpement. I just need
information about comctl32.dll and commctrl.dll.
I'm trying to have this app
(http://appdb.winehq.org/appview.php?appId=1485&versionId=2451) working.
In fact, it works. But only using native comctl32.dll, which re
Hi all,
I'm a newbie in wine using and wine developpement. I just need
information about comctl32.dll and commctrl.dll.
I'm trying to have this app
(http://appdb.winehq.org/appview.php?appId=1485&versionId=2451) working.
In fact, it works. But only using native comctl32.dll, which requires
native c
> Actually, we shouldn't be generating assembly code on the fly. If you
> have more than say 16 proxies in a process then it is actually cheaper
> in terms of memory usage and cache locality to have a set of compiled
> entry points that can be shared by all proxies. It is even better if you
> c
Hi all,
I'm a newbie in wine using and wine developpement. I just need
information about comctl32.dll and commctrl.dll.
I'm trying to have this app
(http://appdb.winehq.org/appview.php?appId=1485&versionId=2451) working.
In fact, it works. But only using native comctl32.dll, which requires
nat
The addition of tools/widl/write_msft.c added the following four warnings,
basically doubling the number of warnings we are getting with GCC 3.4.
write_msft.c:582: warning: `ctl2_alloc_importinfo' defined but not used
write_msft.c:620: warning: `ctl2_alloc_importfile' defined but not used
write_ms
On Fri, 2005-01-07 at 13:46 +0100, [EMAIL PROTECTED] wrote:
> i totally agree with you on this one ;-), but the feasibility of this
> depends on how dynamic these proxies have to be, i.e., is enough
> information known at compile/link time to create them in a read-only
> section or not.
The thunks
On 6 Jan 2005, Alexandre Julliard wrote:
> I'm not sure I follow you, if your .so files have been built correctly
> they shouldn't contain undefined references to Windows APIs. Could you
> please show an example of the situation that causes a problem?
On Thu, 6 Jan 2005, Dimitrie O. Paun wrote:
21 matches
Mail list logo
