wine-devel

wine-devel@winehq.org

3 participants
84400 discussions

audio.c fault reproduction
by Simon Britnell 20 Nov '01

20 Nov '01

I downloaded and ran the QuickTime installer and the Pajama Sam demo last PM. I have reproduced the problem with Pajama Sam (it seems that ends of samples are either not playing or being overwritten), but I can't get QuickTimePlayer.exe to do anything at all. I'll investigate the Pajama Sam problems over the remainder of the week. __________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1

2 1

RE: MIDL and COM
by Patrik Stridvall 20 Nov '01

20 Nov '01

> On 16 Nov 2001, Alexandre Julliard wrote: > > > Ove Kaaven <ovehk(a)ping.uio.no> writes: > > > > > But can the machine-generated sources that MIDL outputs > be put into the > > > official Wine source? > > > > I'd prefer not. If we want to use .idl files we'll have to come up > > with our own compiler, and then we can put the .idl source > in the tree > > and compile it at build time. > > Hmm. Even when using flex and bison, it sounds like a fair amount of > work... wonder who would volunteer? There already are a multitude of open souce (GPL and otherwise) CORBA .idl compilers. Of course Wine have probably slightly different requirements but I should guess that we could save 90% of the work compared to writing it from scratch. Alexandre: Is a GPL:ed (or possible different licenced) .idl compiler acceptable? > > > And how about source IDL files? Can we put into Wine IDL > extracted from > > > real Windoze .tlb files with a tool like oleview.exe, or > IDL parsed from > > > MIDL-generated Windows SDK .h files, like objidl.h, with a script? > > > > No, anything generated from a Windows file is copyrighted by > > Microsoft, so we cannot distribute it. We need to rewrite > these files > > from scratch, just like we do for the normal headers. > > Now where are all the usual non-lawyers on this list who > would argue that > API definitions, like prototypes in header files (which of > course IDL, as > a formalized API spec format, is all about), cannot be copyrighted? > Oh well... I'm here. :-) Well, I wouldn't really go quite that far. The API definitions in themselves can't be copyrighted, true. But a specific way of expressing them is, so compiling any Microsoft file will generate create a derived work copyrighted by Microsoft as the main rule. However it is not quite that easy, since only the specific expression is protected, the compilation result is only a derived work if it still contains any protected expression. In light of this you could argue that since, I presume, MIDL removes whitespace and commments which is IIRC the only really expression, since the rest the API defintions are just facts, that the MIDL compiled files just contains facts not any part of the protected expression. However that is a little thin line to walk, since there is quite of lack of real cases in the area, so I would recommend that we do as Alexandre suggest. Beside having the real .idl files in the Wine tree might be useful for other things as well.

1 0

Re: MIDL and COM
by Alexandre Julliard 20 Nov '01

20 Nov '01

Ove Kaaven <ovehk(a)ping.uio.no> writes: > Problem 1: MIDL-generated code. > midl.exe is Microsoft's IDL compiler, it reads .idl files which describe > RPC and COM interface, from which it generates .c files, .h files, and > typelibs. (It is possible to find copies of midl.exe floating on the net, > as some people have put together "COM kits" for Borland C++ that contains > midl.exe and some standard .idl files and put them on the web) > > But can the machine-generated sources that MIDL outputs be put into the > official Wine source? I'd prefer not. If we want to use .idl files we'll have to come up with our own compiler, and then we can put the .idl source in the tree and compile it at build time. > And how about source IDL files? Can we put into Wine IDL extracted from > real Windoze .tlb files with a tool like oleview.exe, or IDL parsed from > MIDL-generated Windows SDK .h files, like objidl.h, with a script? No, anything generated from a Windows file is copyrighted by Microsoft, so we cannot distribute it. We need to rewrite these files from scratch, just like we do for the normal headers. > Problem 2: RPCSS > rpcss.exe is the place that keeps track of which process owns which RPC > endpoints, exported COM objects, and object activation tables. > The IRunningObjectTable interface, for example, is managed by rpcss.exe, > and keeps track of certain kinds of COM objects on the computer, so that > other processes can connect to running COM objects. We probably don't want > Wine to have to run a separate process for this? If not, can we put this > kind of COM stuff into the wineserver? I'd prefer having a separate process, at least in the first stage. -- Alexandre Julliard julliard(a)winehq.com

2 1

audio.c regression on Nov. 10th
by Ori Pessach 19 Nov '01

19 Nov '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Despite my previous report on this, something did break in audio.c between November 9th and November 10th. I checked out a version from 11/09/2001, and it works. I updated just audio.c with -D 11/10/2001, and Humongous Entertainment games don't recognize the sound card anymore. There have been substantial changes to audio.c during those 24 hours - enough to confuse diff, as a matter of fact. I'll look into it, but I wanted to report this first. The reason I thought earlier that the problem went away was that I had a sticky date on audio.c that I wasn't aware of. Ori Pessach -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: http://www.oripessach.com iD8DBQE7+VXUzA/uWWyw6uQRAmkHAJ94A+IW82jXdhhLl6ODWaUs7I+SwACg16oT FIIymJ5xAP6eNc+5GlbQ3SU= =zHkd -----END PGP SIGNATURE----- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

2 1

Re: Patches for FreeBSD 5.x compilation
by Alexandre Julliard 19 Nov '01

19 Nov '01

Francois Gouget <fgouget(a)free.fr> writes: > I guess that one day Alexandre is going to argue that Linux should > stop polluting the namespace with 'struct user'... Well, struct user is the only reason for including sys/user.h, so I guess it can be considered acceptable; but anything else defined in there (like struct user_regs_struct on Linux) is namespace pollution too IMO. And if there comes a day when the server is managing users, the corresponding struct will definitely be named struct user, not struct wine_unique_prefix_0918274_user or whatever (and note that we don't really need user.h even on Linux, we could just as well hardcode the offset). -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Patches for FreeBSD 5.x compilation
by Alexandre Julliard 19 Nov '01

19 Nov '01

Steve Kargl <sgk(a)troutmask.apl.washington.edu> writes: > FreeBSD isn't polluting the namespace. <sys/user.h> is a > a non-standard header file. It's still made available to applications, and there is really no reason for exporting internal kernel names this way. At least it could be renamed or put inside #ifdef _KERNEL. The alternative is of course to avoid sys/user.h, or play with #defines on the Wine side; but prefixing our structures with wine_ is not a solution. -- Alexandre Julliard julliard(a)winehq.com

4 4

Re: Fix to audio.c 1.46 loop problem + choppy sound
by Michael Stefaniuc 19 Nov '01

19 Nov '01

On Fri, Nov 16, 2001 at 07:59:20PM -0800, Simon Britnell wrote: > This patch should fix a loop playing failure reported > by Eric and a problem with choppy sound I experienced > playing total annihilation Hmm ... this patch horrible breaks the sound in Quicktime. The sound is now (audio.c 1.47) practicaly nonexistand: every 5-7 seconds you hear something for about 1/2 seconds. Before that (audio.c 1.45,1.46) the sound was choppy and played at 4/5 of the normal speed whereas with audio.c 1.44 the sound plays perfect. I'm using Quicktime 5.02 standalone in the german version. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.de Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

1 0

Re: Patches for FreeBSD 5.x compilation
by Alexandre Julliard 19 Nov '01

19 Nov '01

Francois Gouget <fgouget(a)free.fr> writes: > Renaming struct thread it the right thing to do though. Why > doesn't changing thread to wine_thread in request.h work? No, the right thing is to fix the FreeBSD headers to stop polluting the namespace. struct thread is a perfectly valid identifier for an application to use (and we are certainly not the only application using it). -- Alexandre Julliard julliard(a)winehq.com

2 1

Kdevelop and Wine
by Chuck Fischer 19 Nov '01

19 Nov '01

Hello, I'm new to Linux, Kdevelop and Wine. I've been given the task of getting a Windows application to run on *nix. After some surfing I found KDevelop and Wine. I would like to use KDevelop to build my Windows app with WineLib. Can this be done? Has it been done? What do I need to do to get it to work? Also, are there any plans or thoughts about integrating WineLib with KDevelop? TIA, Chuck

2 1

Re: Build failure due to winsock.h changes, specifically htonl
by Gerald Pfeifer 19 Nov '01

19 Nov '01

On Thu, 15 Nov 2001, Francois Gouget wrote: > Yes. This one is actually simple to solve: do not include > 'winsock2.h'. AFAICT including 'winsock2.h' is not necessary since 1.66 > (2000/08/31) when get_socket_event and FD_MAX_EVENTS where removed. > I am working on the other compilation problems... I just performed a cvs update and now was able to again build Wine on FreeBSD 4.4 due to your latest changes. Thanks a lot! Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel