- Original Message -
From: "Dustin Navea" <[EMAIL PROTECTED]>
> --- Jon Brandenburg <[EMAIL PROTECTED]> wrote:
> > On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
> >
> > > and occurs 2-3 hours into the build. Thanks for any further
suggestions.
> >
> Well on my old 1.2 ghz athlon (when
On September 9, 2003 10:34 pm, Geoff Thorpe wrote:
> On the other hand, I *have* duplicated the interface
> verbatim in terms of using exactly the same element names, the same order
> of elements in the structures, etc.
This is fine, the element names, and order in the structure _are_
part of the
On September 9, 2003 02:32 pm, Richard Cohen wrote:
>
> OK, do you want to do it or shall I?
I'd appreciate if you can do it, I'm close to my bandwidth :)
> I think the second is cleaner - but it's not really a big deal, and as
> you say it will disappear, but probably not in time for 0.9
OK, no
On September 9, 2003 10:14 pm, Dimitrie O. Paun wrote:
> On September 9, 2003 08:40 pm, Geoff Thorpe wrote:
> > when adding missing functions and structure types to wine headers, to
> > what extent can we copy-n-paste structure definitions from the
> > documentation at msdn.microsoft.com web? IANAL
On September 9, 2003 08:46 pm, Kevin Groeneveld wrote:
> One question I have is how should the differences in Windows versions be
> handled? This question applies to both the wine implementation and the
> tests.
>
> One example is that BuildCommDCB in Windows 95 sets the DCBlength member
> of DCB
Le mar 09/09/2003 à 13:33, Shachar Shemesh a écrit :
> Yes. I posted the source for a small program that tests this. It's
> available at http://www.winehq.org/hypermail/wine-devel/2003/08/0175.html.
Thanks.
> There is one gotcha that still needs to be looked into. It appears that
> even when IC
On September 9, 2003 07:37 pm, Robert Shearman wrote:
> --- /dev/null Mon Jun 24 01:53:01 2002
> +++ wine/dlls/quartz/list.h Mon Sep 8 00:48:58 2003
The list.h stuff seems to be fairly popular, why not stick a
copy in wine/list.h?
--
Dimi.
On September 9, 2003 08:40 pm, Geoff Thorpe wrote:
> when adding missing functions and structure types to wine headers, to
> what extent can we copy-n-paste structure definitions from the
> documentation at msdn.microsoft.com web? IANAL.
I'd say none -- don't copy-n-paste, express it (type it) you
This first patch should not break the Unix build. This patch fixes building
most of the source files on MS_VC. I tested building under Mingw and we can
still build and link but one of you guys on *nix may want to double check.
After this patch you will still get the following errors with MS_VC and
--- Jon Brandenburg <[EMAIL PROTECTED]> wrote:
> On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
>
> > and occurs 2-3 hours into the build. Thanks for any further suggestions.
> >
>
> Speaking of compile times.. what are the average/min/max times for
> compiling the complete system? I was surpri
--- Rok Mandeljc <[EMAIL PROTECTED]> wrote:
> I've been thinking recently about resolution changes in wine/X. As I
> understand, this now works with UseXVidMode enabled, but I sometimes
> find it ugly; I run X at 1280x1024 and when I run game in 640x480
> (fullscreen), X switches resolution. But as
Jakob Eriksson wrote:
Could you also make test.c into a regression test for inclusion into Wine?
That is almost more important than the actual patch to Wine - if we have
the conformance test, it ensures changes to Wine in the future does not
destroy functionality.
I agree that this would be a good
Le mar 09/09/2003 à 13:47, Bill Medland a écrit :
> , except that rpm insists on the appropriate packages being installed before
> it will even install the wine. Personally my environment is for business
> computing. I only have a sound card because it is on the board; I don't have
> speakers.
Hi there,
Quick licensing/copyright question before I submit something I regret:
when adding missing functions and structure types to wine headers, to
what extent can we copy-n-paste structure definitions from the
documentation at msdn.microsoft.com web? IANAL.
Cheers,
Geoff
--
Geoff Thorpe
On Wed, 10 Sep 2003, Francois Gouget wrote:
> 1. keep the old default.dsl file which hard-codes the presentation in
> all the output files and makes it impossible for an end-user to modify
> it.
>
> 2. use the new default.dsl file which puts all the presentation aspects
> in the css file so tha
So which do you want:
1. keep the old default.dsl file which hard-codes the presentation in
all the output files and makes it impossible for an end-user to modify
it.
2. use the new default.dsl file which puts all the presentation aspects
in the css file so that the html files don't have a har
Hi there! I am trying to get up to speed on developing applications
using wine. The winelib-user documentation recommends getting started by
taking a look at the winemine (wine-xx/programs/winemine) code
packaged with the library.
I seem to be having different outcomes when I compile the co
Are we allowed to use that file all over wine? Having access to a global
shared linked list implementation would be handy.
On Tue, 2003-09-09 at 20:49, Alexandre Julliard wrote:
> Robert Shearman <[EMAIL PROTECTED]> writes:
>
> > +struct list * pFreeList;
> > +struct list * pUsedList;
>
On Tue, 9 Sep 2003, Igor Grahek wrote:
> Do you think something like this will do?
Yes, this looks much better.
> I also checked some other controls in comctl32 and every implementation
> is different. Usualy there is no hwndNotify and GetParent() is used in
> SendMessageW calls and all of these
On Tue, 9 Sep 2003, Francois Gouget wrote:
> I completely get the point. The whole point of CSS is to separate
> content from presentation!
Yes, it does (in a simple way, indeed), but this was not my point.
My point is that the way it's done it's up to the user. They should
decide if the they wan
On Tue, 9 Sep 2003, Dimitrie O. Paun wrote:
[...]
> I think you are missing the point of separating content from
> presentation.
I completely get the point. The whole point of CSS is to separate
content from presentation!
Do you actually know what CSS is?
I also take exception to your claim that
On Tue, 9 Sep 2003, Francois Gouget wrote:
> > So why is that a problem?
>
> You do not want the HTML docs generated by 'make html' to look good?
I don't care. In fact, the very purpose of using SGML in the first place
is so that we shouldn't need to care. The _fundamental_ principle is
separat
On Tue, 9 Sep 2003, Dimitrie O. Paun wrote:
> On Tue, 9 Sep 2003, Francois Gouget wrote:
>
> > By site-wide one I suppose you mean the one shipped with DocBook?
>
> yes
>
> > We cannot do that because the DocBook one:
> > 1. does not reference any css file
>
> So why is that a problem?
You do no
Do you think something like this will do?
--- patch begin ---
Index: dlls/comctl32/treeview.c
===
RCS file: /home/wine/wine/dlls/comctl32/treeview.c,v
retrieving revision 1.125
diff -u -r1.125 treeview.c
--- dlls/comctl32/
Robert Shearman <[EMAIL PROTECTED]> writes:
> +struct list * pFreeList;
> +struct list * pUsedList;
You are not using the list functions the right way; these should be a
struct list, not a struct list *. The rest of the code then gets a lot
cleaner, you don't need any special cases for em
On Tue, 9 Sep 2003, Francois Gouget wrote:
> By site-wide one I suppose you mean the one shipped with DocBook?
yes
> We cannot do that because the DocBook one:
> 1. does not reference any css file
So why is that a problem?
> 2. does not use the %use-id-as-filename% option which results in ug
On Tue, 9 Sep 2003, Richard Cohen wrote:
> ...rather than adding -L to both the DLLs and static libraries
> No functional changes.
I'm not sure this is correct, as the order of -L and -l may be
significant. That is to say, if I do
-LdirA -la -LdirB -lb
then the system will search for a only i
On Tue, 9 Sep 2003, Richard Cohen wrote:
> Slightly different from last time.
>
> > Default name that mingw uses is a.exe
> > This also stops winewrap from segfaulting when passed no arguments.
>
> Changelog
> Handle default linker output name (a.exe) in winewrap instead of
> winegcc
I'm
On Tue, 9 Sep 2003, Dimitrie O. Paun wrote:
> On Tue, 9 Sep 2003, Francois Gouget wrote:
[...]
> >Don't hardcode the look and feel in default.css. Use a css file
> > instead.
>
> For that, we should just completely remove documentation/default.dsl
> and use the site-wide one.
By site-wide one
Dimitrie O. Paun wrote:
>...
That's not a good strategy, we'll have to be in line with the gcc
people, and breaking compatibility like so is no good. Let's float
the question on their mailing list before we settle on something.
OK, do you want to do it or shall I?
In any case, we need to have our
David Laight <[EMAIL PROTECTED]> writes:
> #define LONG_LONG_MAX (~0ull)
That's ULONG_LONG_MAX, not LONG_LONG_MAX. And note that the 'll'
suffix is not portable.
--
Alexandre Julliard
[EMAIL PROTECTED]
Bill Medland wrote:
On September 9, 2003 10:18 am, Vincent Béron wrote:
The best way is, as Alexandre tries to go, run-time detection. Yes the
executables are bigger (more functionality), but there's not more
installation-time dependancies and it can use some more libs as they are
installed.
Vi
> -Original Message-
> From: Alexandre Julliard [mailto:[EMAIL PROTECTED]
> Sent: 09 September 2003 17:36
> To: Robert Shearman
> Cc: [EMAIL PROTECTED]
> Subject: Re: Using limits.h
>
> Well, long long itself is not very portable, and long long constants
> definitely aren't. What do you nee
> , except that rpm insists on the appropriate packages being installed before
> it will even install the wine. Personally my environment is for business
> computing. I only have a sound card because it is on the board; I don't have
> speakers. So I have no need for sound, scanner support, ca
On Tue, 9 Sep 2003, Francois Gouget wrote:
> * documentation/Makefile.in,
>documentation/default.dsl,
>documentation/winedoc.css
>
>Don't hardcode the look and feel in default.css. Use a css file
> instead.
For that, we should just completely remove documentation/default.dsl
and use
On Tue, 9 Sep 2003, Francois Gouget wrote:
> If the look and feel is set by default.dsl, then only users who have
> access to the Wine source and have DocBook installed on their system can
> change the look and feel. All other users must change each and every
> file manually (because default.dsl p
On September 9, 2003 10:18 am, Vincent Béron wrote:
> Le mar 09/09/2003 à 12:50, Keith Matthews a écrit :
> > On Tue, 09 Sep 2003 19:09:04 +0300
> >
snip
> > I think you should be considering multiple, alternative packages. Yes, I
> > know it is more work, but even the current packages have depende
Vincent Béron wrote:
Le mar 09/09/2003 à 12:09, Shachar Shemesh a écrit :
I (as well as many of the Israeli and Arab community) would much
appretiate if you could do the extra effort, as well as hear feedback.
Do you personnally use either RH8 or 9? Or is there a way for me
(without knowi
Le mar 09/09/2003 à 12:09, Shachar Shemesh a écrit :
> As all you have to do is have a local copy of the ICU library in order
> to get BiDi support in (and configure will autodetect it), I don't think
> having your RPMs compiled with BiDi support will hurt in any way. Your
> SRPMS will still be
Le mar 09/09/2003 à 12:50, Keith Matthews a écrit :
> On Tue, 09 Sep 2003 19:09:04 +0300
> Shachar Shemesh <[EMAIL PROTECTED]> wrote:
>
> >
> > >
> > >I am the RH package manager for Wine.
> > >My RPMS are indeed without BiDi support for now, as I was aiming for
> > >them to be rebuildable on any
Keith Matthews wrote:
On Tue, 09 Sep 2003 19:09:04 +0300
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
I am the RH package manager for Wine.
My RPMS are indeed without BiDi support for now, as I was aiming for
them to be rebuildable on any fully-updated (and nothing more) RH
box. Of course, I can
On Tue, 9 Sep 2003, Dimitrie O. Paun wrote:
[...]
> It's fine to use CSS for the .template ones that we're going to server
> from the site. However, for the HTML we package, we shouldn't IMO. If they
> need such thing, they would have a custom default.dsl or some such.
> That's the very point -- we
> Should I just use the constant that LONG_LONG_MAX equates to and put this
> into the source file then? Is this portable (i.e. is long long 64bits on all
> platforms) ?
#define LONG_LONG_MAX (~0ull)
David
--
David Laight: [EMAIL PROTECTED]
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> We have the following definition:
>
> /usr/local/include/wine/windows/winbase.h:#define STILL_ACTIVE
> STATUS_PENDING
>
> This fails to compile under visual-mingw. Is this how it is
> defined under the MS headers? Does this mean that any
On Tue, 09 Sep 2003 19:09:04 +0300
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
>
> >
> >I am the RH package manager for Wine.
> >My RPMS are indeed without BiDi support for now, as I was aiming for
> >them to be rebuildable on any fully-updated (and nothing more) RH
> >box. Of course, I can install
"Robert Shearman" <[EMAIL PROTECTED]> writes:
> Should I just use the constant that LONG_LONG_MAX equates to and put this
> into the source file then? Is this portable (i.e. is long long 64bits on all
> platforms) ?
Well, long long itself is not very portable, and long long constants
definitely a
A further problem with the Debian install is that winedefault.reg is
delivered packed (.gz). Perhaps as a further addition to regedit (or what
ever command line version is to be used) should be to unpack it as well as
read it - otherwise please can the Debian version be shipped ungziped.
David
Vincent Béron wrote:
Le mar 09/09/2003 à 10:14, Shachar Shemesh a écrit :
Ivan Leo Murray-Smith wrote:
The latest Wine
RPMs are compiled without BiDi support
the Red Hat rpms may be, but I can assure you that your help to get bidi into the
mdk rpms wasn't invane.
Gree
On 9 Sep 2003, Vincent Béron wrote:
> I am the RH package manager for Wine.
> My RPMS are indeed without BiDi support for now, as I was aiming for
> them to be rebuildable on any fully-updated (and nothing more) RH box.
Shouldn't the configure script take care of that?
--
Dimi.
No, but when I removed the line it worked fine. With it the hypermail
archives 404. It's odd.
On Tue, 2003-09-09 at 10:33, Dimitrie O. Paun wrote:
> On Tue, 9 Sep 2003, Jeremy Newman wrote:
>
> > Log message:
> > regex was causing hypermail archives to 404
>
> Do you know why?
--
Jeremy Ne
On September 9, 2003 07:24 am, Dimitrie O. Paun wrote:
> On Tue, 9 Sep 2003, Bill Medland wrote:
> > I have just installed Mandrake 9.1 and tried to build Wine. I am getting
> > an error when byacc runs in dlls/msi
> >
> > byacc: e - line 73 of "./sql.y", syntax error
> >
> > %pure-parser
> > ^
>
Le mar 09/09/2003 à 10:14, Shachar Shemesh a écrit :
> Ivan Leo Murray-Smith wrote:
>
> >>The latest Wine
> >>RPMs are compiled without BiDi support
> >>
> >>
> >the Red Hat rpms may be, but I can assure you that your help to get bidi into the
> >mdk rpms wasn't invane.
> >
> Greedy ol' me, t
On Tue, 9 Sep 2003, Jeremy Newman wrote:
> Log message:
> regex was causing hypermail archives to 404
Do you know why?
--
Dimi.
> -Original Message-
> From: Alexandre Julliard [mailto:[EMAIL PROTECTED]
> Sent: 09 September 2003 03:13
> To: Robert Shearman
> Cc: [EMAIL PROTECTED]
> Subject: Re: Using limits.h
>
> "Robert Shearman" <[EMAIL PROTECTED]> writes:
>
> > I'm trying to use the default limits.h installed on m
On Tue, 9 Sep 2003, Igor Grahek wrote:
> I'm pretty new at Wine patching and CreateWindowEx does some other
> parent checking so I didn't want to break anything else by fixing this
> one.
Yes, but this solution just looks to ugly to be propagated to the
other controls. Let's find a nice one that
On Tue, 9 Sep 2003, Bill Medland wrote:
>
> I have just installed Mandrake 9.1 and tried to build Wine. I am getting an
> error when byacc runs in dlls/msi
>
> byacc: e - line 73 of "./sql.y", syntax error
>
> %pure-parser
> ^
>
> Any idea what I am doing wrong or what I have failed to do?
I'm pretty new at Wine patching and CreateWindowEx does some other
parent checking so I didn't want to break anything else by fixing this
one.
Igor
> -Original Message-
> From: Dimitrie O. Paun [mailto:[EMAIL PROTECTED]
> Sent: September 8, 2003 11:52 PM
> To: [EMAIL PROTECTED]; Igor Gra
Ivan Leo Murray-Smith wrote:
The latest Wine
RPMs are compiled without BiDi support
the Red Hat rpms may be, but I can assure you that your help to get bidi into the
mdk rpms wasn't invane.
Greedy ol' me, trying to get them all :-)
Shachar
--
Shachar Shemesh
Open Source integra
Hi all
When i try to compile wineproc , i got the following error:
In file included from system.c:3:
../../include/psapi.h:25: parse error before "LPVOID"
../../include/psapi.h:25: warning: no semicolon at end of struct or union
(...)
and many ohter like this.
What did i do in the wrong way ?
>The latest Wine
>RPMs are compiled without BiDi support
the Red Hat rpms may be, but I can assure you that your help to get bidi into the
mdk rpms wasn't invane.
We have the following definition:
/usr/local/include/wine/windows/winbase.h:#define STILL_ACTIVE
STATUS_PENDING
This fails to compile under visual-mingw. Is this how it is
defined under the MS headers? Does this mean that any app
using STILL_ACTIVE must also include ntstatus.h?
--
D
Folks,
When compiling visual-mingw under Winelib, I get the following error:
In file included from /usr/local/include/wine/windows/ole2.h:27,
from /usr/local/include/wine/windows/shlobj.h:22,
from ../include/browsdlg.h:19,
from browsdlg.cpp:14:
/
On September 9, 2003 05:28 am, Francois Gouget wrote:
> * default.dsl specifies attributes that hard-code the coulor and style
> of various HTML elements. That's fine for standalone HTML files but it's
> wrong for a web site where such things should be specified by the
> cascading style sheets
It
Ivan Leo Murray-Smith wrote:
Could the Red Hat packager please take care of this
http://www.winehq.org/hypermail/wine-users/2003/09/0081.html
I don't know if it's a rpm packaging error or a problem with the users system
setup, but I suppose the creator of the rpm can solve the issue quite easily.
Alexandre Julliard wrote:
Eric Pouech <[EMAIL PROTECTED]> writes:
so the possible solutions are:
- As we compile Wine without the _UNICODE flag, we could change the
code as follows:
XXA => XX
XXW => (LPWSTR)XX
drawback: we'll have warnings if we need to compile with the _UNICODE
flag...
On Tue, 9 Sep 2003, Dimitrie O. Paun wrote:
> On September 8, 2003 01:23 pm, Francois Gouget wrote:
> > As far as I can see the differences between winehq.dsl and default .dsl
>
> Well, if we keep winehq.dsl, why do we need a perl script to patch
> the output? The HTML stuff should be generated wi
eric lin <[EMAIL PROTECTED]> wrote:
> Thanks your reply and point out. I will try to search web somewhere
>to get it for running my.exe file by wine. (or point me some place
>in web I can get it)
>
> or anyone have other alternative, please inform me.
Well if you have written that program an
67 matches
Mail list logo
