World Wine News

Hi folks,

Again, congrats to everybody for the 1.0 release!

Now that I'm starting to recover from the shock of having actually shipped 1.0, here are a few notes on future development:

1) Code freeze is over, patches are accepted again. If you sent patches and they didn't get applied during code freeze, please rebase them against 1.0 and resend them.

2) Development will continue as usual in the git "master" branch. The 1.1.x development releases will be made from that branch every other Friday.

3) There is now a git "stable" branch, where only important bug fixes will be committed. The 1.0.x maintenance releases will be made from that branch whenever enough changes have accumulated to justify a release.

The process I suggest for the 1.0.1 release is as follows:

- all bugs should be fixed in the master branch first - once a bug fix has been committed to master, the corresponding bug report should be marked fixed, with the sha1 of the commit fixing it - the bug report should then be put into the 1.0.1 milestone.

This will allow me to periodically query for 1.0.1 bugs that are fixed in master and cherry-pick the corresponding commits into the stable branch.

--
Alexandre Julliard

Hi Folks,

Thanks to the volunteer efforts of James Ramey (new guy in our office), we now have a great venue for WineConf 2008.

I've put together a page on it here:
WineConf2008

The key details are that it will be over the weekend of September 27 and 28, at a hotel in Bloomington, MN. I promise that it won't be mind numbingly cold, and I won't make any one traipse to see an ice palace this year *grin*.

In fact, it's a nice hotel, quite close to the airport, the Mall of America, a Wildlife refuge, and to a stop for our light rail system.

Additionally, I believe we will be able to offer fairly substantial travel sponsorships for people that find the cost of travel prohibitive. Email me privately if that would be a help.

And for those Europeans that hate US policies, I'll point out two things:

• January 20, 2009 is fast approaching.
• 1 Euro gets you $1.60, which is a whole lot of cheap beer

At any rate, if you're interested in coming to WineConf this year, please visit the Wiki and sign up for the WineConf mailing list:
http://www.winehq.org/mailman/listinfo/wineconf
We generally use that list for minutiae to avoid spamming the broader mailing list.

Hope to see you in September!

Cheers,

Jeremy

Hi students,

As you might know it's time for midterm evaluations. Unfortunately for some students I haven't seen the progress they made, and I highly encourage all students to send their patches early and often, even if it's not yet finished.

Also, I would like to hear from all students now a reflection. What went well, and what didn't, and what did you accomplish so far? :-)

Cheers, Maarten.

I've been cleaning my patches, thanks to the infinite patience of Kai, and I'm starting to send them right now. However my progress can be tracked in http://repo.or.cz/w/wine/gsoc_dplay.git

The main problem so far was to adapt my work flow to an style I've never worked with, and to realize I still have too much to learn :P

My first milestone is mostly accomplished: most tests are done, but the implementation is less improved than I expected. I only committed some trivial patches, but at least I started understanding what is done and what has to be done (which should have been done when writing my application and schedule, but, well.) I'm facing some problems understanding the current dplay codebase, but it's probably I feel overwhelmed all this new COM platform, unknown to me, and with some effort it's not so complex.

Summing up, I still have to (stop slacking and) study a lot before doing anything really productive.

Regards
Ismael

So far I've accomplished a great amount of text handling functions (FontFamilies, FontCollections, and StringFormat) (which I need to clean up before sending) in GDI+, and I expect to have those finished by next week (putting me a week behind where I want to be), but I'm also working on GpRegion handling now (as oddly enough, a few StringFormat functions need it).

For what hasn't gone so well, I still need work on focusing on _one_or_two_ sub-projects at once (mild ADD at work) - as a bunch of half finished projects don't help too much. The other is sticking closer to test-driven development. I've often found myself caught up on why my code doesn't make some app work, and it becomes clear once a simple testcase is written (or at least clear what isn't the problem).

This has been a very rewarding and empowering experience, and I look forward to contributing to Wine after Summer of Code is finished.

My project so far has gone fairly well, and I'd say I'm currently just a little ahead of schedule, which I'm pleased about. The first part of the project was to get the Control Panel working in the shell namespace, and it turned out that a lot of the work had already been done, it just wasn't glued together properly. It took me a little while to figure out what needed doing, but I managed to work it out and it made it into Wine 1.1. :-) I'm now moving onto developing some new control panel applets, and looking at ways to improve winecfg. I've been working on an Add/Remove Programs applet for the past week or so, which is now more or less complete, and will likely be submitted to wine-patches soon. I'm also thinking about what I'm going to do with winecfg, with my thinking that the bits that are not configurable on a per-application basis (desktop appearance and sound, mainly) can be moved into/reimplemented in new control panels. So that'll be my main focus over the next few weeks.

The biggest challenge for me now is probably working out a "work plan", and making sure I set targets for myself, to ensure I can try to get as much done and use my time efficiently. Other than that, I've learned a lot about the general process of Wine development, and have quite enjoyed things so far.

The majority of my code can be found at http://repo.or.cz/w/wine/gsoc_cpanel.git.

Cheers,

I've been working on two parts of my MSXML projects:
1) Fixing bugs
That went well. I have fixed Photoshop CS3 installer as well as other bugs. I have patches for bugs 5565, 8945, 9349, 9604, 10802, 11301, 11376, 12521, 14386, 14260 and 5074. I have also investigated most of bugs in msxml3 component.
2) Implementing SAX reader.
I have started working on it and written some code, but it still needs more work.
I have also done some work towards asynchronous reading.

The hardest thing for me was debugging Photoshop CS3 installer. It was easy to find missing APIs that I had to implement, but the last problem was very hard to find (and it's that more satisfaction from fixing it:-) ).

Regards,
Piotr

As a continuation from the question on making the FAH GPU2 Nvidia client run, we have gotten past the detecting the card as we changed Wine's generic output to look like an Nvidia card thanks to a few of you. Now comes the hard part. Even when using the cudart.dll file it does not work. We get an cudastream error about it not being implemented. It then repeats these 5 lines until the client is stopped.

Reading file work/wudata_07.tpr, VERSION 3.1.4 (single precision)
Reading file work/wudata_07.tpr, VERSION 3.1.4 (single precision)
Reading sasa-enabled ir 0 0
Initializing Nvidia gpu library
cudaMalloc CUDAStream::Allocate failed feature is not yet implemented

Martijn Berger said here (http://www.winehq.org/pipermail/wine-devel/2008-July/067063.html) that all that should need to be done is right a wrapper to translate the calls from cudart.dll to libcuda.so.2.0. I suppose the place to start would be to download the SDK's and see how much documentation is available on both the Linux and Windows calls.

From reading the programing guide and reference manual it seems that most of the function are the same as expected between Windows and Linux, in fact the reference manual doesn't differentiate between the two.

http://developer.download.nvidia.com/compute/cuda/2.0-Beta2/docs/Programming_Guide_2.0beta2.pdf br /> http://developer.download.nvidia.com/compute/cuda/2.0-Beta2/docs/CudaRefMan_2.0beta2.pdf br />

Is it possible to just symbolicly link the cudart.dll file to the libcudart.so file? If they are expecting mostly the same function calls should this not work? They are going to test this now and see.

I believe the main problem is just that cudart.dll is driving to access the windows nvidia driver where this is none, but libcudart.so knows how to access the Linux driver.

Well at least it compiled, but it isn't working. We are still getting the message that the function isn't implemented.

Initializing Nvidia gpu library
cudaMalloc CUDAStream::Allocate failed feature is not yet implemented

Now both cudamalloc and all four cuda stream's, cudaStreamCreate, Destroy, Query and Synchronize were implemented. I thought maybe it was because in the spec file I had the cudaStream's as pointers (ptr) so I switched them to long but ti didn't make a difference. Originally the argument was "stream" but I can't get any argument but ptr and long to pass the winegcc for spec files.

http://shelnutt.twomurs.com/patches/cuda/cuda.dll.spec

Does wine need to somehow be made aware of the presence of the cudart.dll.so file? We tried putting it in both the system32 and the lib folder but it seems also that maybe WINE needs to be made aware of it?

http://www.kegel.com/wine/valgrind/logs/2008-07-11-10.09-count-by-file.txt shows that 54 tests have some valgrind error (not counting leaks). Some of those are false positives, e.g. anything with NtFsControlFile can probably be ignored [and soon will be]. http://www.kegel.com/wine/valgrind/logs/2008-07-11-10.09-count-by-error.txt shows that there are about 188 different errors. However, many of those are related; if for instance the bug in PrimaryBufferImpl_GetVolume is fixed, it will clear up 32 of them. A lot of the patches I had been carrying (http://www.kegel.com/wine/valgrind/logs/2008-07-04-patches/) might be useful for somebody looking at doing real fixes.

I have returned to "just catch regressions" mode rather than doing a full frontal assault on Valgrind errors for now. Though my continuous build-and-test results are online for anyone who wants to continue the full frontal assault... But anyone who does better have really good tests and/or reputation, or Alexandre won't accept the patch.