Announcing WineConf 2009
Dear Wine developers, You may recall that I volunteered to help host WineConf in the Netherlands in 2007 when, after a vote, an offer by Dan Kegel to host at Google's offices in Zurich won the bid. Last year WineConf went across the pond to Minnesota, so it seems natural that this year's WineConf will be hosted in the country with the highest number of Wine developers per capita ;-) At Twente University Campus to be precise, near the city of Enschede: http://maps.google.com/maps/ms?ie=UTF8hl=enmsa=0msid=104770595427636833911.00044a70a58a75a8aaa2ell=52.240573,6.852207spn=0.0226,0.057764z=15 From November 6-8 (Friday to Sunday). I chose this place because of its good facilities and relatively low costs; we want to make the conference accessible for as many developers as possible. Directions, agenda, etc. will be made available on this page: http://wiki.winehq.org/WineConf Please e-mail me at winec...@meelstraat.net if you intend to come, so we can make a better estimation of the number of attendees. See you there! -Hans
Re: PowerPC MacOSX work...
On May 28, 2009, at 01:49 AM, Ben Klein wrote: So you also know you can't run x86 apps on PPC platforms without emulation, just like you can't run z80 code on x86 without emulation. Also, where is this PPC code in Wine exactly? What source file exactly? Files containing PPC specific related code: tools/relay.c lib/wine/port.c lib/port/interlocked.c dlls/ntdll/signal_powerpc.c server/context_powerpc.c iirc: include/ntdll.h Next contain code Macintosh/MacOSX/Darwin specific PPC/x86 generic dlls/winecoreaudio/* dlls/kernel32/locale.c dlls/ntdll/cdrom.c I am sure there are other files with PPC parts too. Winelib would be good if you had the source code for your Win32/Win16 apps and wanted to produce PPC binaries of them. Sounds like that's not what you're trying to do though. The particular program I wish to run is close source.
DIB engine
Question on this debate: Has AJ documented anywhere what the architectural issues are so they can be addressed? I have not seen this in the thread and was just wondering. If we have them documented then its a relatively easy task to address each of them. Yes it may be a hack but you would be surprised at how much of Windows is a hack internally. Do we even have an architectural document or guidelines to reference? Chris
Re: DIB engine
On Fri, May 29, 2009 at 10:10 AM, chris ahrendt celtich...@yahoo.com wrote: Question on this debate: Has AJ documented anywhere what the architectural issues are so they can be addressed? I have not seen this in the thread and was just wondering. If we have them documented then its a relatively easy task to address each of them. Yes it may be a hack but you would be surprised at how much of Windows is a hack internally. Do we even have an architectural document or guidelines to reference? If you read the entire thread, you'll see that the DIB design is not a puzzle that can be carved out and dropped in. The DIB engine must be designed from scratch. Designing the DIB architecture is half of the work itself, since that involves planning a lot of the code/testing, etc. He pointed out a few things he didn't like about Massimo's design, but not a full 'here's the spec, do this exactly'. For more details, read the full thread and past discussions. -- -Austin
Re: DIB engine
On 05/29/2009 11:14 AM, Austin English wrote: On Fri, May 29, 2009 at 10:10 AM, chris ahrendtceltich...@yahoo.com wrote: Question on this debate: Has AJ documented anywhere what the architectural issues are so they can be addressed? I have not seen this in the thread and was just wondering. If we have them documented then its a relatively easy task to address each of them. Yes it may be a hack but you would be surprised at how much of Windows is a hack internally. Do we even have an architectural document or guidelines to reference? If you read the entire thread, you'll see that the DIB design is not a puzzle that can be carved out and dropped in. The DIB engine must be designed from scratch. Designing the DIB architecture is half of the work itself, since that involves planning a lot of the code/testing, etc. He pointed out a few things he didn't like about Massimo's design, but not a full 'here's the spec, do this exactly'. For more details, read the full thread and past discussions. -- -Austin Right Austin, I have... thats why I asked the question why not sit down and say here is what we want from the DIB engine here is the Spec do this .. I have seen the here is what I don't like. But nothing showing what exactly is needed. This would be the first step in resolving this circular argument / discussion which is what I am trying to facilitate =D. Until that is done all we can do is have this same circular argument / discussion =D chris
Re: DIB engine
On Fri, May 29, 2009 at 10:50 AM, chris ahrendt celtich...@yahoo.com wrote: Right Austin, I have... thats why I asked the question why not sit down and say here is what we want from the DIB engine here is the Spec do this .. I have seen the here is what I don't like. But nothing showing what exactly is needed. This would be the first step in resolving this circular argument / discussion which is what I am trying to facilitate =D. Until that is done all we can do is have this same circular argument / discussion =D As was said in the other thread, just designing it alone would take a few months work. AJ is really busy with other things, and a few months work is both a lot of money and a lot of wasted productivity. No one is stepping up to sponsor the work, so it's a bit hard for him to take that on. -- -Austin
Re: DIB engine
2009/5/29 Austin English austinengl...@gmail.com: On Fri, May 29, 2009 at 10:50 AM, chris ahrendt celtich...@yahoo.com wrote: Right Austin, I have... thats why I asked the question why not sit down and say here is what we want from the DIB engine here is the Spec do this .. I have seen the here is what I don't like. But nothing showing what exactly is needed. This would be the first step in resolving this circular argument / discussion which is what I am trying to facilitate =D. Until that is done all we can do is have this same circular argument / discussion =D As was said in the other thread, just designing it alone would take a few months work. AJ is really busy with other things, and a few months work is both a lot of money and a lot of wasted productivity. No one is stepping up to sponsor the work, so it's a bit hard for him to take that on. -- -Austin Heh, I wonder if someone should approach Autodesk and say, Give us sponsorship and we'll get Autocad running on Linux they surely have deep pockets :) Luke. P.S. Must learn to reply to all, sorry Austin
Re: DIB engine
As was said in the other thread, just designing it alone would take a few months work. AJ is really busy with other things, and a few months work is both a lot of money and a lot of wasted productivity. No one is stepping up to sponsor the work, so it's a bit hard for him to take that on. Who is asking AJ to do all of the work. Huw Davies and Max have worked out what is needed to get this into Wine. All we need is guidance on what is acceptable and how we should proceed. This seems to be a serious shortcoming on AJs part. Without this, any further work would be futile and could end up being very frustrating. I've seen this from Huw and it is starting to come from Max. AJ needs to get some time together and write up what is and is not acceptable as far as code style, fashion and what he expects out of the development efforts for the DIB engine. Making a statement after months of work is IHMO very unacceptable. Also, I don't see this as circular, but the 'snake' of getting AJ to accept code into the codebase is. Very respectfully submitted, James McKenzie
Re: DIB engine
Luke: Heh, I wonder if someone should approach Autodesk and say, Give us sponsorship and we'll get Autocad running on Linux they surely have deep pockets :) If Autodesk were interested in making AutoCad work with Linux, they would make a native version, not try to get it working with Wine. Sorry, but them's the facts. Now, if you were to speak up with your wallet and donate to the effort, that is a vastly different story. Sadly, we are on our own to get AutoCad fully working with Wine. I don't expect any assistance from AutoDesk nor any of the major Linux players. James McKenzie
Time to remove obsolete platforms HP, SGI, and DEC?
The only use of these platforms was three mistaken bug reports that probably wanted PC. I don't see any reason to keep these old system types around any more. OK to remove? (Suggested in http://bugs.winehq.org/show_bug.cgi?id=13363 )
Re: Time to remove obsolete platforms HP, SGI, and DEC?
The only use of these platforms was three mistaken bug reports that probably wanted PC. I don't see any reason to keep these old system types around any more. OK to remove? (Suggested in http://bugs.winehq.org/show_bug.cgi?id=13363 ) Please. --Juan
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 11:43 AM, Juan Lang juan.l...@gmail.com wrote: The only use of these platforms was three mistaken bug reports that probably wanted PC. I don't see any reason to keep these old system types around any more. OK to remove? (Suggested in http://bugs.winehq.org/show_bug.cgi?id=13363 ) Please. --Juan I don't suppose you've changed your mind on also removing the obsolete OS's (BSDI, AIX, IRIX, HP-UX, SunOS, OS/2, Mac OS X 10.3)? -- -Austin
Re: Time to remove obsolete platforms HP, SGI, and DEC?
I don't suppose you've changed your mind on also removing the obsolete OS's (BSDI, AIX, IRIX, HP-UX, SunOS, OS/2, Mac OS X 10.3)? Did he say he wasn't for it? I didn't catch that. Dan, here's a vote for removing those. I can't comment on all of them, but SunOS has been obsolete for a decade, OS/2 nearly as long. --Juan
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 11:58 AM, Juan Lang juan.l...@gmail.com wrote: I don't suppose you've changed your mind on also removing the obsolete OS's (BSDI, AIX, IRIX, HP-UX, SunOS, OS/2, Mac OS X 10.3)? Did he say he wasn't for it? I didn't catch that. Dan, here's a vote for removing those. I can't comment on all of them, but SunOS has been obsolete for a decade, OS/2 nearly as long. It was in a thread a few months ago: http://www.winehq.org/pipermail/wine-devel/2008-November/070494.html He removed several, but those few I mentioned are still there. -- -Austin
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 9:58 AM, Juan Lang juan.l...@gmail.com wrote: I don't suppose you've changed your mind on also removing the obsolete OS's (BSDI, AIX, IRIX, HP-UX, SunOS, OS/2, Mac OS X 10.3)? Did he say he wasn't for it? I didn't catch that. Dan, here's a vote for removing those. I can't comment on all of them, but SunOS has been obsolete for a decade, OS/2 nearly as long. He's referring to an old discussion we had. I'm ok with deleting any that have zero valid instances in the bug tracker and are obsolete. All the SunOS instances should really be Solaris, I think. So IRIX, SunOS, and OS/2 can go now. We do have one (abandoned but recent) real bug against HP-UX and HP, so maybe it's not quite time to delete those (but we should rename HP as HP-PA to keep people with HP PCs from choosing it). Why do we have versions on Mac OS X? How about we combine them all? - Dan
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 12:02 PM, Dan Kegel d...@kegel.com wrote: On Fri, May 29, 2009 at 9:58 AM, Juan Lang juan.l...@gmail.com wrote: I don't suppose you've changed your mind on also removing the obsolete OS's (BSDI, AIX, IRIX, HP-UX, SunOS, OS/2, Mac OS X 10.3)? Did he say he wasn't for it? I didn't catch that. Dan, here's a vote for removing those. I can't comment on all of them, but SunOS has been obsolete for a decade, OS/2 nearly as long. He's referring to an old discussion we had. I'm ok with deleting any that have zero valid instances in the bug tracker and are obsolete. All the SunOS instances should really be Solaris, I think. Yes, they should be. They're all mine, I've moved them. So IRIX, SunOS, and OS/2 can go now. We do have one (abandoned but recent) real bug against HP-UX and HP, so maybe it's not quite time to delete those (but we should rename HP as HP-PA to keep people with HP PCs from choosing it). If it's worth keeping an extra platform/OS for one bug, I suppose. Could simply set it to 'other'. Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. Some bugs will only show up in Tiger, because Leopard has them fixed on Apple's end. (Someone correct me if I'm wrong here, this is based off of what I've seen on wine-users). -- -Austin
Re: Time to remove obsolete platforms HP, SGI, and DEC?
Austin English austinengl...@gmail.com wrote: Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. Some bugs will only show up in Tiger, because Leopard has them fixed on Apple's end. (Someone correct me if I'm wrong here, this is based off of what I've seen on wine-users). By that logic we neeed to have all versions of Ubuntu, Fedora, etc. listed as well. -- Dmitry.
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 12:14 PM, Dmitry Timoshkov dmi...@codeweavers.com wrote: Austin English austinengl...@gmail.com wrote: Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. Some bugs will only show up in Tiger, because Leopard has them fixed on Apple's end. (Someone correct me if I'm wrong here, this is based off of what I've seen on wine-users). By that logic we neeed to have all versions of Ubuntu, Fedora, etc. listed as well. I'd say the analogy is closer to having Linux 2.4/2.6, but I get your point. I'm fine with combining those. -- -Austin
Re: Time to remove obsolete platforms HP, SGI, and DEC?
Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. Some bugs will only show up in Tiger, because Leopard has them fixed on Apple's end. (Someone correct me if I'm wrong here, this is based off of what I've seen on wine-users). Very much correct. MacOSX 10.5.7 with XQuartz 2.3.3 or higher correctly utilize all OpenGL features present in Wine. MacOSX 10.4.x or MacOSX 10.5.6 or MacOSX 10.5.7 without XQuartz 2.3.3 applied will not. Since I am running MacOSX 10.5.7 with XQuartz 2.3.3.2 applied, I do not know the status of backporting the fixes to the 10.4 (Tiger) baseline or even if it is possible. As far as OS/2 goes, it is still a viable operating system, but I think, for Wine purposes, it should be dropped as an available OS for bugzilla and for the AppDB. James McKenzie
Re: DIB engine
As was said in the other thread, just designing it alone would take a few months work. AJ is really busy with other things, and a few months work is both a lot of money and a lot of wasted productivity. No one is stepping up to sponsor the work, so it's a bit hard for him to take that on. Who is asking AJ to do all of the work. Huw Davies and Max have worked out what is needed to get this into Wine. All we need is guidance on what is acceptable and how we should proceed. This seems to be a serious shortcoming on AJs part. Without this, any further work would be futile and could end up being very frustrating. I've seen this from Huw and it is starting to come from Max. AJ needs to get some time together and write up what is and is not acceptable as far as code style, fashion and what he expects out of the development efforts for the DIB engine. Making a statement after months of work is IHMO very unacceptable. Also, I don't see this as circular, but the 'snake' of getting AJ to accept code into the codebase is. This is where I figured I'd wake up and chime in a bit. None of you all know me I suppose but I've been primarily just listening in on this list for the better part of two years now. :) My ears perked up when the two words DIB and spec were put together in the same sentence. One frustration I encountered when wanting to contribute to wine a little over two years ago was that nobody seemed to be able to say Hey, this is what we are missing/need, here are the specs, go implement. Essentially, that's how I work and how I work well. Trying to fix random bugs in random applications in a codebase completely unfamiliar to me seemed to be rather futile so at that point in time I abandoned those efforts and just stuck to using wine. =P So that said, I've got a decent amount of experiences dealing with graphics, including full 24/32-bit color on embedded devices. Considering the environment, performance has always been a priority as well. Plus, I also really like working with graphics related code. So from where I'm standing right now, this seems to be right in my neighbourhood. So if anyone can drop a full spec into my lap which outlines everything I need to write and where (given I adhere to things as I should of course) I won't have any issues getting that accepted later on, I'd be more than willing to take on something like this. Thanks, Stephan
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On May 29, 2009, at 12:18 PM, Austin English wrote: On Fri, May 29, 2009 at 12:14 PM, Dmitry Timoshkov dmi...@codeweavers.com wrote: Austin English austinengl...@gmail.com wrote: Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. Some bugs will only show up in Tiger, because Leopard has them fixed on Apple's end. (Someone correct me if I'm wrong here, this is based off of what I've seen on wine-users). By that logic we neeed to have all versions of Ubuntu, Fedora, etc. listed as well. I'd say the analogy is closer to having Linux 2.4/2.6, but I get your point. I'm fine with combining those. One big difference is that upgrading from Tiger to Leopard costs money, unlike upgrading Linux. So, it's not as simple to just tell a user to upgrade to fix their problem. (I don't interact with Bugzilla much, so I'm not weighing in on what suits the needs of bug wranglers. Just raising a point.) -Ken
Re: Announcing WineConf 2009
On Fri, May 29, 2009 at 2:52 AM, Hans Leidekker h...@codeweavers.com wrote: Dear Wine developers, You may recall that I volunteered to help host WineConf in the Netherlands in 2007 when, after a vote, an offer by Dan Kegel to host at Google's offices in Zurich won the bid. Last year WineConf went across the pond to Minnesota, so it seems natural that this year's WineConf will be hosted in the country with the highest number of Wine developers per capita ;-) At Twente University Campus to be precise, near the city of Enschede: http://maps.google.com/maps/ms?ie=UTF8hl=enmsa=0msid=104770595427636833911.00044a70a58a75a8aaa2ell=52.240573,6.852207spn=0.0226,0.057764z=15 From November 6-8 (Friday to Sunday). I chose this place because of its good facilities and relatively low costs; we want to make the conference accessible for as many developers as possible. Directions, agenda, etc. will be made available on this page: http://wiki.winehq.org/WineConf Please e-mail me at winec...@meelstraat.net if you intend to come, so we can make a better estimation of the number of attendees. See you there! -Hans What is the status of the Wine Party Fund this year, to help with the cost of transportation/lodging? I remember quite a bit of it was used up last year... -- -Austin
Re: Announcing WineConf 2009
On Fri, May 29, 2009 at 5:17 PM, Austin English austinengl...@gmail.com wrote: What is the status of the Wine Party Fund this year, to help with the cost of transportation/lodging? I remember quite a bit of it was used up last year... This also provides a good time for us to publicly seek donations. -- Steven Edwards There is one thing stronger than all the armies in the world, and that is an idea whose time has come. - Victor Hugo
Re: Announcing WineConf 2009
On Fri, May 29, 2009 at 11:26 PM, Steven Edwards winehac...@gmail.com wrote: On Fri, May 29, 2009 at 5:17 PM, Austin English austinengl...@gmail.com wrote: What is the status of the Wine Party Fund this year, to help with the cost of transportation/lodging? I remember quite a bit of it was used up last year... This also provides a good time for us to publicly seek donations. -- Steven Edwards There is one thing stronger than all the armies in the world, and that is an idea whose time has come. - Victor Hugo Yep and we might also want donations for some other things e.g. DIB engine and other things (it shouldn't bite with CW). Further remember as of Wineconf 2008 it is not Wine Party Fund but Wine Development Fund but it was discussed on saturday morning ;) Roderick
Re: Announcing WineConf 2009
On Fri, May 29, 2009 at 4:26 PM, Steven Edwards winehac...@gmail.com wrote: On Fri, May 29, 2009 at 5:17 PM, Austin English austinengl...@gmail.com wrote: What is the status of the Wine Party Fund this year, to help with the cost of transportation/lodging? I remember quite a bit of it was used up last year... This also provides a good time for us to publicly seek donations. On a related note, I noticed when installing TortiseSVN on windows, that the installer has a donation button. Well, two actually, one with installing files on the progress screen, and one at the final 'finish' screen, asking for a donation. When you click it, it goes to http://tortoisesvn.tigris.org/donate.html. So, two things: A) We really need a donation page. Currently, the donate button on http://www.winehq.org redirects you to paypal, without sending you to a WineHQ page first explaining what the donation is for, saying thanks, etc. It's a bit hard/tacky to send a donation request out if we don't have a page to send them to, other than paypal. B) We could add a button to winecfg for donating (under the 'Name'/'Company' fields in the 'About' tab). It's unobtrusive, non-invasive, and gives quite a bit of exposure (curious users check out all the tabs and would see it). The donate tab may be a bit controversial, and I'm not proposing putting it in without gathering some opinions first. But I do think it's a really neat idea. There are often times I want to donate to a project, but I'm lazy and don't want to search through the site to find it. A button making it easier for me to do so = $ in their pocket. -- -Austin
Re: DIB engine
On 05/29/2009 12:28 PM, James Mckenzie wrote: As was said in the other thread, just designing it alone would take a few months work. AJ is really busy with other things, and a few months work is both a lot of money and a lot of wasted productivity. No one is stepping up to sponsor the work, so it's a bit hard for him to take that on. Who is asking AJ to do all of the work. Huw Davies and Max have worked out what is needed to get this into Wine. All we need is guidance on what is acceptable and how we should proceed. This seems to be a serious shortcoming on AJs part. Without this, any further work would be futile and could end up being very frustrating. I've seen this from Huw and it is starting to come from Max. AJ needs to get some time together and write up what is and is not acceptable as far as code style, fashion and what he expects out of the development efforts for the DIB engine. Making a statement after months of work is IHMO very unacceptable. Also, I don't see this as circular, but the 'snake' of getting AJ to accept code into the codebase is. Very respectfully submitted, James McKenzie Agreed James, this is the exact point I am getting at I guess... what exactly is acceptable and what is not... It seems we have a working solution for DIB. I do not think that it would take that long for AJ to sit down and say here.. this is what I want or this is what is acceptable then its up to the development people to come back and say ok here is our solution and then rectify the delta's in between. If Huw and Max have a solution then what is the delta? Chris
Re: Time to remove obsolete platforms HP, SGI, and DEC?
On Fri, May 29, 2009 at 10:51 AM, James Mckenzie jjmckenzi...@earthlink.net wrote: Why do we have versions on Mac OS X? How about we combine them all? It can make a big difference in the bug. The X.org version in OS X (partially?) depends on what OS X version you have. ... As far as OS/2 goes, it is still a viable operating system, but I think, for Wine purposes, it should be dropped as an available OS for bugzilla and for the AppDB. OK. Last time we looked at this, their bodies hadn't quite decomposed enough, but now they're most sincerely dead. I've simplified our bug OS and System fields accordingly. Of MacOSX, I removed 10.0 and 10.1. There were some real 10.2 bugs, so it's probably not appropriate to remove that one (yet...). - Dan
Re: DIB engine
2009/5/30 chris ahrendt celtich...@yahoo.com: Question on this debate: Has AJ documented anywhere what the architectural issues are so they can be addressed? This did not need a new thread. You should have posted it on the existing one. I have not seen this in the thread and was just wondering. If we have them documented then its a relatively easy task to address each of them. Yes it may be a hack but you would be surprised at how much of Windows is a hack internally. You would be surprised at how much of Wine is NOT a hack internally. Wine doesn't do hacks, hence AJ's reluctance to include the current DIB proposal in Wine (to make it correct later will require a lot of hacking, as Max has objected). Do we even have an architectural document or guidelines to reference? This was also raised on the existing thread. No. This is a problem. The best we have so far is DIB engine should be integrated into GDI32. This is not a problem, because both Max and AJ share this goal, but if I understand correctly, Max doesn't want to invest the effort (which is a lot) until the current design is validated by inclusion into upstream source. This leads me to my second point. 2009/5/30Z Stephan Rose ker...@somrek.net: My ears perked up when the two words DIB and spec were put together in the same sentence. One frustration I encountered when wanting to contribute to wine a little over two years ago was that nobody seemed to be able to say Hey, this is what we are missing/need, here are the specs, go implement. Essentially, that's how I work and how I work well. Trying to fix random bugs in random applications in a codebase completely unfamiliar to me seemed to be rather futile so at that point in time I abandoned those efforts and just stuck to using wine. =P So that said, I've got a decent amount of experiences dealing with graphics, including full 24/32-bit color on embedded devices. Considering the environment, performance has always been a priority as well. Plus, I also really like working with graphics related code. So from where I'm standing right now, this seems to be right in my neighbourhood. So if anyone can drop a full spec into my lap which outlines everything I need to write and where (given I adhere to things as I should of course) I won't have any issues getting that accepted later on, I'd be more than willing to take on something like this. Welcome aboard! I suggest that if you'd like to help out with the DIB engine (with the goal of getting it included to Wine upstream source), that you take a look at the code on bugzilla page #421 and talk to Massimo about how you might adapt it for integration into GDI32.
Re: DIB engine
Stephan Rose ker...@somrek.net wrote: So if anyone can drop a full spec into my lap which outlines everything I need to write and where (given I adhere to things as I should of course) I won't have any issues getting that accepted later on, I'd be more than willing to take on something like this. Anyone needing a full spec can start here: http://msdn.microsoft.com/en-us/library/dd183562(VS.85).aspx If that's not enough just do it the way most of us are doing it every day: 1. write a test case 2. make the test pass under Wine -- Dmitry.
Re: d3d10: Improve parse_fx10.
Rico Schüller kgbric...@web.de wrote: -/* version info? */ -skip_dword_unknown(ptr, 2); +/* Compiled target version (e.g. fx_4_0=0xfeff1001, fx_4_1=0xfeff1011). */ +read_dword(ptr, e-version); +TRACE(Target: %#x\n, e-version); 0xfeff/0xfffe is a unicode byte order mark, could it serve the same purpose here? -- Dmitry.
