wine-devel August 2012

wine-devel@winehq.org

52 participants
118 discussions

Re: [3/4] gdiplus: Destination points passed to GdipDrawImagePointsRect should be in device units.
by Dmitry Timoshkov 08 Aug '12

08 Aug '12

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > + scale_x = units_scale(srcUnit, graphics->unit, graphics->xres); > + scale_y = units_scale(srcUnit, graphics->unit, graphics->yres); This depends on a not yet sent series which introduces units_scale(), please ignore for now, I'll resend it a bit later. -- Dmitry.

1 0

Cannot run wineinstall
by Carlos Tiba 07 Aug '12

07 Aug '12

It displays the message: " You are running wineinstall as root, this is not advisable. Please rerun as a user. Aborting. " However it is not possible to install anything on Ubuntu Linux if you-re not root. The command: $ sudo ./wineinstall does not run after passwd enter because of the message above. How is it possible? Thanks Carlos Tiba

2 1

Wine automated testing update
by Jeremy White 06 Aug '12

06 Aug '12

Hi Folks, At the last Wine conference, I volunteered to find a home for the WineTestBot that Ge's brother has been hosting, and to take over the Buildbot that Dan and Austin have been so diligently maintaining. This is an update on that project, mostly to help keep my procrastinating self moving it along. First, we have a lovely set of hardware; 4 servers, in a dedicated rack, with a dedicated static ip to the outside world. One server is the gateway, 2 are dedicated Linux test systems (with nice fast processor + gpus), and one is a beefy system capable of running many VMs. The plan was to move the existing VMWare based WineTestBot to this hardware and simply get the existing system up and running on the new hardware. Here we hit our first snag; the VMWare folks are not willing to provide a permanent license for VMWare to us. So, we've shifted gears, and are exploring whether something like qemu + kvm would be a sufficient alternate. I've done a little of this work, and Maarten is hopefully going to help me try converting the existing VMs to see if we can save any hassle by doing a conversion. In parallel, I learned a great deal about buildbot and the buildbot system that Dan has built. There are two especially valuable and useful functions provided by this buildbot: the first is essentially a patch watcher; a process that catches simple mistakes (e.g. build errors on different architectures, and so on). The second is more powerful and is encapsulated by the 'dotests.sh' shell script. The dotests.sh script does a good job of basically running make test and noticing any test failures outside of 'the usual ones'. There is an infrastructure for Buildbot is a good tool, and I invested a lot of energy into it (as have Dan and Austin). However, Alexandre has persuaded me that we should first explore integrating the dotest.sh functionality into the existing WineTestBot, as that would allow us to have a very simple clean web page, and would also allow us to integrate most cleanly with Alexandre's back end tools. Of course, WineTestBot is Perl code, and my Perl fu is low. So I have recently asked Francois to help with that effort as well. So the basic plan is as follows: 1. Test qemu/kvm with a few Windows versions to see if it'll work. 2. If so, modify WineTestBot to use qemu instead of vmware. (This is 'easy' because the WineTestBot code nicely isolates the VM functions, but 'hard', because VMWare provides some APIs that may have to be replicated). 3. Migrate WineTestBot to the new hardware stack 4. Write new code to run 'dotests.sh' as part of WineTestBot Cheers, Jeremy

9 11

Fwd: [GSoC Mentors] [Announce] GSoC 2012 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching
by Austin English 06 Aug '12

06 Aug '12

---------- Forwarded message ---------- From: Carol Smith <carols(a)google.com> Date: Mon, Aug 6, 2012 at 12:33 PM Subject: [GSoC Mentors] [Announce] GSoC 2012 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching To: Google Summer of Code Mentors List <google-summer-of-code-mentors-list(a)googlegroups.com> Hi there, This is a friendly reminder that Monday, 13 August is our soft "pencils down" date. We suggest that students have completed their projects by this date and spend a week writing documentation and wrapping up their projects. We require that students stop all coding on 20 August. Monday, 20 August at 19:00 UTC is also when final evaluations open. Please consider this your reminder to submit your final evaluation by 24 August at 19:00 UTC so that you don't delay your students' final payments or possibly jeopardize your organization's attendance at the mentor summit. I have updated the code submission guidelines [0] and posted it on Melange for your reference. Code submission begins once students have received a passing grade on their final evaluations (after 24 August). The deadline is 14 September. One question students ask a lot is what portion of their code to submit if they made changes to an existing code base or their code interacts a lot with a system they didn't write. The answer is: use your best discretion. Have them submit the code that makes the most sense from a user's perspective. If students need help with code submission they should contact the Melange team at melange-soc-dev(a)googlegroups.com. I have posted the questions for the final evaluations below as well for your reference. [0] - http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20… Cheers, Carol ---------------- How would you rate the student’s performance on his/her project since the midterm evaluations? It has improved since the midterm It has stayed the same since the midterm It has gotten worse since the midterm Considering your student’s original project proposal, how closely does the project produced reflect the project proposed? It’s almost exactly the same - there have been very few changes to the project It’s similar - there have been some changes over the course of the summer It’s different - we changed the goals or scope of the project It’s different - the student diverged from the project plan How much time have you spent on Google Summer of Code since the midterm evaluations (again, take into consideration both time mentoring the student and working on the program as a whole)? 10-15 hours per week 15-20 hours per week 20-25 hours per week 25-30 hours per week 30-35 hours per week 35-40 hours per week 40+ hours per week How does this amount of time spent on the program compare to before the midterms? It’s less than before the midterms It’s about the same It’s more than before the midterms How would you rate your student’s performance overall? Excellent - amongst the best performers I’ve ever worked with Strong, solid performance Okay Poor How would you rate your experience with the program overall? Excellent - one of the best programs I’ve ever participated in Very good Okay Poor Did you have a co-mentor in the program this year? If so, would you consider this a help or a hindrance? Why? What one thing would you tell mentors for your organization to do in the future to help the students’ experience with the program? What was the most rewarding and/or difficult part of the program for you this year? Anything else you’d like to tell us? -- You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group. To post to this group, send email to google-summer-of-code-mentors-list(a)googlegroups.com. To unsubscribe from this group, send email to google-summer-of-code-mentors-list+unsubscribe(a)googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-summer-of-code-mentors-list?hl=en. -- -Austin

1 0

GSoC mentor summit 2012
by Owen Rudge 06 Aug '12

06 Aug '12

It looks like the GSoC mentor summit for 2012 has been announced. Are any of the mentors this year interested in attending? It's happening on the 20th/21st October in Mountain View. Details are on the GSoC mentor wiki: http://gsoc-wiki.osuosl.org/index.php/2012 Cheers, -- Owen Rudge http://www.owenrudge.net/

6 10

Re: [1/4] dwrite: Added IDWriteFont stub
by Dmitry Timoshkov 06 Aug '12

06 Aug '12

Nikolay Sivov <nsivov(a)codeweavers.com> wrote: > +static IDWriteFontVtbl dwritefontvtbl = { > + dwritefont_QueryInterface, > + dwritefont_AddRef, > + dwritefont_Release, Vtables should be 'const' (here and in other places). -- Dmitry.

1 0

Re: winex11.drv: xrandr1.2 don't assume CRTC 0 is active
by Henri Verbeet 01 Aug '12

01 Aug '12

On 30 July 2012 22:05, <siro(a)das-labor.org> wrote: > As far as I understood CRTC 0 is disabled, because it is only capable of > generating analog video signals. I'm using a HDMI monitor, which is > controlled by CRTC 1. To use multihead (not clone), you have to connect a > analog (VGA) and digital monitor (in my case). Each monitor will use one > CRTC and each CRTC will show a different part of the same screen. With this > in mind every active CRTC should be listed as "native Windows monitor". Mostly for reference, what driver are you using? Have you explicitly configured a primary display at all (either through the xorg.conf "Primary" option for the monitor, or with the xrandr utility), or is it just picking up the first display connector and incorrectly assuming it's connected?

2 2

Wiki seems to be down.
by Scott Ritchie 01 Aug '12

01 Aug '12

Thank you :)

1 0

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 August 2012