September 2013 - Wine-commits

André Hentschel : winedev: Recommend MinGW-w64.
by Alexandre Julliard 03 Sep '13

03 Sep '13

Module: docs Branch: master Commit: affa3314584cbdc9010a770168810df7cfac19a3 URL: http://source.winehq.org/git/docs.git/?a=commit;h=affa3314584cbdc9010a77016… Author: André Hentschel <nerv(a)dawncrow.de> Date: Mon Sep 2 22:14:14 2013 +0200 winedev: Recommend MinGW-w64. --- en/winedev-testing.sgml | 22 +++++++++++----------- 1 files changed, 11 insertions(+), 11 deletions(-) diff --git a/en/winedev-testing.sgml b/en/winedev-testing.sgml index c6e00ab..f0643b2 100644 --- a/en/winedev-testing.sgml +++ b/en/winedev-testing.sgml @@ -181,11 +181,11 @@ <sect1 id="cross-compiling-tests"> - <title>Cross-compiling the tests with MinGW</title> + <title>Cross-compiling the tests with MinGW-w64</title> <sect2> - <title>Setup of the MinGW cross-compiling environment</title> + <title>Setup of the MinGW-w64 cross-compiling environment</title> <para> - Here are some instructions to setup MinGW on different Linux + Here are some instructions to setup MinGW-w64 on different Linux distributions and *BSD. </para> <sect3> @@ -195,7 +195,7 @@ The following step should probably work on any deb based system. </para> <para> - Run <userinput>apt-get install mingw32</userinput>. + Run <userinput>apt-get install mingw-w64</userinput>. </para> </sect3> <sect3> @@ -206,13 +206,13 @@ The following step should probably work on any rpm based system. </para> <para> - Run <userinput>yum install mingw32-gcc</userinput>. + Run <userinput>yum install mingw64-gcc</userinput>. </para> </sect3> <sect3> <title>*BSD</title> <para> - The *BSD systems have in their ports collection a port for the + The *BSD systems have in their ports collection only a port for the MinGW cross-compiling environment. Please see the documentation of your system about how to build and install a port. </para> @@ -341,13 +341,13 @@ Kit</ulink>. </itemizedlist> </sect2> <sect2> - <title>With MinGW</title> + <title>With MinGW-w64</title> <para> - Wine build system already has support for building tests with a MinGW - cross-compiler. See the section above called <quote>Setup of the MinGW + Wine build system already has support for building tests with a MinGW-w64 + cross-compiler. See the section above called <quote>Setup of the MinGW-w64 cross-compiling environment</quote> for instructions on how to set things up. - When you have a MinGW environment installed all you need to do is rerun - configure and it should detect the MinGW compiler and tools. Then run + When you have a MinGW-w64 environment installed all you need to do is rerun + configure and it should detect the MinGW-w64 compiler and tools. Then run <command>make crosstest</command> to start building the tests. </para> </sect2>

1 0

André Hentschel : winedev: Minor updates to the windowing chapter.
by Alexandre Julliard 03 Sep '13

03 Sep '13

Module: docs Branch: master Commit: 75e9f01f05ea8c2bb2aecac46d0c41c6773ce645 URL: http://source.winehq.org/git/docs.git/?a=commit;h=75e9f01f05ea8c2bb2aecac46… Author: André Hentschel <nerv(a)dawncrow.de> Date: Mon Sep 2 22:15:18 2013 +0200 winedev: Minor updates to the windowing chapter. --- en/winedev-windowing.sgml | 29 +++++++++++++---------------- 1 files changed, 13 insertions(+), 16 deletions(-) diff --git a/en/winedev-windowing.sgml b/en/winedev-windowing.sgml index 6effe48..71738bc 100644 --- a/en/winedev-windowing.sgml +++ b/en/winedev-windowing.sgml @@ -1,22 +1,21 @@ <chapter> <title>Windowing system</title> <sect1> - <title>USER Module</title> + <title>USER32 Module</title> <para> - USER implements windowing and messaging subsystems. It also + USER32 implements windowing and messaging subsystems. It also contains code for common controls and for other miscellaneous stuff (rectangles, clipboard, WNet, etc). - Wine USER code is located in <filename class="directory">windows/</filename>, - <filename class="directory">controls/</filename>, and - <filename class="directory">misc/</filename> directories. + Wine USER32 code is located in the + <filename class="directory">dlls/user32/</filename> directory. </para> <sect2> <title>Windowing subsystem</title> - <para><filename>windows/win.c</filename></para> - <para><filename>windows/winpos.c</filename></para> + <para><filename>dlls/user32/win.c</filename></para> + <para><filename>dlls/user32/winpos.c</filename></para> <para> Windows are arranged into parent/child hierarchy with one common ancestor for all windows (desktop window). Each @@ -74,7 +73,7 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop. </para> <para> All these issues are dealt with (or supposed to be) in - <filename>windows/winpos.c</filename> with + <filename>dlls/user32/winpos.c</filename> with <function>SetWindowPos()</function> being the primary interface to the window manager. </para> @@ -91,11 +90,10 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop. <sect3> <title>Visible region, clipping region and update region</title> - - <para><filename>windows/dce.c</filename></para> - <para><filename>windows/winpos.c</filename></para> - <para><filename>windows/painting.c</filename></para> - + + <para><filename>dlls/user32/winpos.c</filename></para> + <para><filename>dlls/user32/painting.c</filename></para> + <screen> ________________________ |_________ | A and B are child windows of C @@ -199,8 +197,7 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop. <sect2> <title>Messaging subsystem</title> - <para><filename>windows/queue.c</filename></para> - <para><filename>windows/message.c</filename></para> + <para><filename>dlls/user32/message.c</filename></para> <para> Each Windows task/thread has its own message queue - this @@ -238,7 +235,7 @@ child1->popup->child2->child3->wnd1->child4->wnd2->desktop. messages, then for hardware messages, then it checks if the queue has the <quote>dirty window</quote> bit set, and, finally, it checks for expired timers. See - <filename>windows/message.c</filename>. + <filename>dlls/user32/message.c</filename>. </para> <para> From all these different types of messages, only posted

1 0

André Hentschel : winedev: Leave instructions up to the howto.
by Alexandre Julliard 03 Sep '13

03 Sep '13

Module: docs Branch: master Commit: bf8123ff496696c7312424f693791a80cf2430f5 URL: http://source.winehq.org/git/docs.git/?a=commit;h=bf8123ff496696c7312424f69… Author: André Hentschel <nerv(a)dawncrow.de> Date: Mon Sep 2 22:14:37 2013 +0200 winedev: Leave instructions up to the howto. --- en/winedev-testing.sgml | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/en/winedev-testing.sgml b/en/winedev-testing.sgml index f0643b2..9350f00 100644 --- a/en/winedev-testing.sgml +++ b/en/winedev-testing.sgml @@ -389,9 +389,8 @@ Kit</ulink>. </para></listitem> <listitem><para> If you want to use the Microsoft C++ Toolkit under Wine, - install it under Windows, then copy it to your fake C drive; - it'll work fine there. See <ulink url="http://kegel.com/wine/cl-howto.html">CL Howto</ulink> - for some tips on making it easy to use from the Linux command line. + see <ulink url="http://kegel.com/wine/cl-howto.html">CL Howto</ulink> + for some tips on making it easy to use it from the Linux command line. </para></listitem> </itemizedlist> </para>

1 0

André Hentschel : winedev: Use autoconf to update the configure script.
by Alexandre Julliard 03 Sep '13

03 Sep '13

Module: docs Branch: master Commit: 9f04b7eb676ecbba66648d128b81f7c553b79073 URL: http://source.winehq.org/git/docs.git/?a=commit;h=9f04b7eb676ecbba66648d128… Author: André Hentschel <nerv(a)dawncrow.de> Date: Tue Sep 3 00:11:54 2013 +0200 winedev: Use autoconf to update the configure script. --- en/winedev-coding.sgml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml index a805d24..abc7447 100644 --- a/en/winedev-coding.sgml +++ b/en/winedev-coding.sgml @@ -347,7 +347,7 @@ AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H)) (etc.) to <filename>include/config.h.in</filename>. </para> <para> - Finish up with <command>make configure</command> and + Finish up with <command>autoconf</command> and <command>./configure</command>. </para> </sect2> @@ -432,7 +432,7 @@ AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H)) </varlistentry> </variablelist> <para> - Finish up with <command>make configure</command> and + Finish up with <command>autoconf</command> and <command>./configure</command>. </para> </sect2>

1 0

André Hentschel : winedev: Don' t recommend a preprocessor check to comment out code.
by Alexandre Julliard 03 Sep '13

03 Sep '13

Module: docs Branch: master Commit: 81555011154280813636d684211e515547f07440 URL: http://source.winehq.org/git/docs.git/?a=commit;h=81555011154280813636d6842… Author: André Hentschel <nerv(a)dawncrow.de> Date: Tue Sep 3 00:12:20 2013 +0200 winedev: Don't recommend a preprocessor check to comment out code. --- en/winedev-coding.sgml | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml index abc7447..dc865b1 100644 --- a/en/winedev-coding.sgml +++ b/en/winedev-coding.sgml @@ -100,21 +100,20 @@ <listitem> <para> Commenting out a block of code is usually done by - enclosing it in <command>#if 0 ... #endif</command> - statements. For example. + using <command>if (0)</command>. For example: </para> <screen> /* note about reason for commenting block */ -#if 0 +if (0) { code code /* comments */ code -#endif +} </screen> <para> The reason for using this method is that it does not require that you edit comments that may be inside the - block of code. + block of code and it makes sure the code gets maintained. </para> </listitem> <listitem>

1 0

André Hentschel : Use protocol relative urls in the theme
by Jeremy Newman 03 Sep '13

03 Sep '13

Module: website Branch: master Commit: ef8cfbe0c92cd930f0ed05a053aa44fa5293c174 URL: http://source.winehq.org/git/website.git/?a=commit;h=ef8cfbe0c92cd930f0ed05… Author: André Hentschel <nerv(a)dawncrow.de> Date: Mon Sep 2 20:39:38 2013 +0200 Use protocol relative urls in the theme --- templates/de/global/404.template | 2 +- templates/de/global/themes/winehq/content.template | 8 ++++---- .../de/global/themes/winehq/content_nobox.template | 8 ++++---- templates/en/global/404.template | 2 +- templates/en/global/themes/winehq/content.template | 8 ++++---- .../en/global/themes/winehq/content_nobox.template | 8 ++++---- templates/es/global/404.template | 2 +- templates/fr/global/404.template | 2 +- templates/fr/global/themes/winehq/content.template | 8 ++++---- .../fr/global/themes/winehq/content_nobox.template | 8 ++++---- templates/he/global/404.template | 2 +- templates/he/global/themes/winehq/content.template | 8 ++++---- .../he/global/themes/winehq/content_nobox.template | 8 ++++---- templates/tr/global/404.template | 2 +- templates/tr/global/themes/winehq/content.template | 8 ++++---- .../tr/global/themes/winehq/content_nobox.template | 8 ++++---- templates/zh-cn/global/404.template | 2 +- 17 files changed, 47 insertions(+), 47 deletions(-) Diff: http://source.winehq.org/git/website.git/?a=commitdiff;h=ef8cfbe0c92cd930f0…

1 0

André Hentschel : Wine 1.7.1 freigegeben
by Jeremy Newman 03 Sep '13

03 Sep '13

Module: website Branch: master Commit: e797247bec1af5e146447c9133114158c77c4ea8 URL: http://source.winehq.org/git/website.git/?a=commit;h=e797247bec1af5e146447c… Author: André Hentschel <nerv(a)dawncrow.de> Date: Fri Aug 30 20:44:03 2013 +0200 Wine 1.7.1 freigegeben --- news/de/2013083001.xml | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/news/de/2013083001.xml b/news/de/2013083001.xml new file mode 100644 index 0000000..68a90b1 --- /dev/null +++ b/news/de/2013083001.xml @@ -0,0 +1,18 @@ +<news> +<date>30. August 2013</date> +<title>Wine 1.7.1 freigegeben</title> +<body> + Die Entwicklungsversion 1.7.1 von Wine ist jetzt verfügbar. + <a href="{$root}/announce/1.7.1">Neuerungen (en)</a> in dieser Version: +<ul> + <li>Unterstützung für "keyed event" Objekte.</li> + <li>Unterstützung für den "init once" Synchronisationsmechanismus.</li> + <li>Activation Context Unterstützung für DLLs, Typelibs und COM Klassen.</li> + <li>Das Laden von 32-Bit Typelibs wird unter 64-Bit unterstützt.</li> + <li>Verschiedene Mac Treiber Fehlerbehebungen.</li> + <li>Einige Fehlerbehebungen für die seriellen Schnittstellen.</li> + <li>Verschiedene Fehlerbehebungen.</li> +</ul> +Der Quellcode ist jetzt <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.1.tar.bz2">verfügbar</a>. +Binärpakete werden gerade erstellt und stehen bald auf den jeweiligen <a href="{$root}/download">Downloadseiten</a> zur Verfügung. +</body></news>

1 0

Frédéric Delanoy : French translation for release 1.7.1
by Jeremy Newman 03 Sep '13

03 Sep '13

Module: website Branch: master Commit: cda0a006ad78ccf66fb5ab28caaf9da718e051ab URL: http://source.winehq.org/git/website.git/?a=commit;h=cda0a006ad78ccf66fb5ab… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Fri Aug 30 21:48:40 2013 +0200 French translation for release 1.7.1 --- news/fr/2013083001.xml | 17 +++++++++++++++++ 1 files changed, 17 insertions(+), 0 deletions(-) diff --git a/news/fr/2013083001.xml b/news/fr/2013083001.xml new file mode 100644 index 0000000..6ad45fd --- /dev/null +++ b/news/fr/2013083001.xml @@ -0,0 +1,17 @@ +<news> +<date>30 août 2013</date> +<title>Sortie de Wine 1.7.1</title> +<body> + La version de développement 1.7.1 de Wine est disponible. + <a href="{$root}/announce/1.7.1">Nouveautés</a> de cette version : +<ul> + <li>Prise en charge des objets de type « keyed event ».</li> + <li>Prise en charge du mécanisme de synchronisation de type « initialisation unique ».</li> + <li>Prise en charge du contexte d'activation pour les DLL, bibliothèques de types et classes COM.</li> + <li>Prise en charge du chargement des bibliothèques de types 32 bits sur les systèmes 64 bits.</li> + <li>Divers correctifs pour le pilote Mac.</li> + <li>Quelques correctifs pour les périphériques série.</li> + <li>Diverses corrections de bogues.</li> +</ul> +Le <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.1.tar.bz2">code source</a> est disponible dès à présent. Les paquets binaires sont en cours de construction, et apparaîtront sous peu sur leurs <a href="{$root}/download">sites de téléchargement</a> respectifs. +</body></news>

1 0

Łukasz Wojniłowicz : Polish translation for release 1.7.1
by Jeremy Newman 03 Sep '13

03 Sep '13

Module: website Branch: master Commit: dc0a446a2868126ba9081c78c355c20f6406f9e6 URL: http://source.winehq.org/git/website.git/?a=commit;h=dc0a446a2868126ba9081c… Author: Łukasz Wojniłowicz <lukasz.wojnilowicz(a)gmail.com> Date: Sat Aug 31 06:56:33 2013 +0200 Polish translation for release 1.7.1 --- news/pl/2013083001.xml | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/news/pl/2013083001.xml b/news/pl/2013083001.xml new file mode 100644 index 0000000..36f70f6 --- /dev/null +++ b/news/pl/2013083001.xml @@ -0,0 +1,18 @@ +<news> +<date>Sierpień 30, 2013</date> +<title>Wydano Wine 1.7.1</title> +<body> + Wydanie rozwojowe Wine 1.7.1 jest już dostępne. + <a href="{$root}/announce/1.7.1">Co nowego</a> w tym wydaniu: +<ul> + <li>Wsparcie dla obiektów kluczowych zdarzeń.</li> + <li>Wsparcie dla mechanizmu synchronizacji "init once".</li> + <li>Wsparcie aktywacji kontekstu dla bibliotek DLL, bibliotek typów, i klas COM.</li> + <li>Wsparcie dla wczytywania bibliotek typów 32-bitowych na 64-bitach.</li> + <li>Rozmaite poprawki w sterowniku Mac.</li> + <li>Kilka poprawek dla urządzeń na port szeregowy.</li> + <li>Rozmaite poprawki błędów.</li> +</ul> +Źródło jest <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.1.tar.bz2">już dostępne</a>. +Paczki binarne są w trakcie budowy i ukażą się wkrótce w przeznaczonych dla nich <a href="{$root}/download">pobieralniach</a>. +</body></news>

1 0

Frédéric Delanoy : winedbg: Fix manpage formatting.
by Alexandre Julliard 02 Sep '13

02 Sep '13

Module: wine Branch: master Commit: 7a12ebca0e899031ea92e122d0effc161859302e URL: http://source.winehq.org/git/wine.git/?a=commit;h=7a12ebca0e899031ea92e122d… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Mon Sep 2 11:09:00 2013 +0200 winedbg: Fix manpage formatting. --- programs/winedbg/winedbg.man.in | 56 ++++++++++++++------------------------ 1 files changed, 21 insertions(+), 35 deletions(-) diff --git a/programs/winedbg/winedbg.man.in b/programs/winedbg/winedbg.man.in index 758aa7d..9e1731a 100644 --- a/programs/winedbg/winedbg.man.in +++ b/programs/winedbg/winedbg.man.in @@ -2,32 +2,18 @@ .SH NAME winedbg \- Wine debugger .SH SYNOPSIS -.BR "winedbg " -.RI "[" " options " "] [" -.BI "program name" -.RI "[ program arguments ] |" -.BI "pid" -.RI "]" -.PP -.BR "winedbg " -.BI "--gdb" -.RI "[" " options " "] [" -.BI "program name" -.RI "[ program arguments ] |" -.BI "pid" -.RI "]" -.PP -.BR "winedbg " -.BI "--auto " -.BI "pid" -.PP -.BR "winedbg " -.BI "--minidump " -.RI "[ file.mdmp ]" -.BI "pid" -.PP -.BR "winedbg" -.BI "file.mdmp" +.B winedbg +.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " pid " ]" +.PP +.B winedbg --gdb +.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " pid " ]" +.PP +.BI "winedbg --auto " pid +.PP +.B winedbg --minidump +.RI "[ " file.mdmp " ] " pid +.PP +.BI "winedbg " file.mdmp .SH DESCRIPTION .B winedbg is a debugger for Wine. It allows: @@ -93,15 +79,15 @@ Unix console for textual display. .PP In all modes, the rest of the command line, when passed, is used to identify which programs, if any, has to debugged: -.IP \fBprogram\ name\fR +.IP \fIprogram_name\fR This is the name of an executable to start for a debugging session. \fBwinedbg\fR will actually create a process with this -executable. If \fBprograms arguments\fR are also given, they will be +executable. If \fIprograms_arguments\fR are also given, they will be used as arguments for creating the process to be debugged. -.IP \fBpid\fR -\fBwinedbg\fR will attach to the process which pid is \fBpid\fR (pids -refer to Win32 pids, not Unix pids). Use the \fIinfo proc\fR -\fBwinedbg\fR command to list running processes and their Win32 pids. +.IP \fIpid\fR +\fBwinedbg\fR will attach to the process which pid is \fIpid\fR (pids +refer to Win32 pids, not Unix pids). Use the \fBinfo proc\fR command +within \fBwinedbg\fR to list running processes and their Win32 pids. .IP \fBdefault\fR If nothing is specified, you will enter the debugger without any run nor attached process. You'll have to do the job yourself. @@ -333,9 +319,9 @@ use. Pick up the one you want from its number. .PP \fIMisc.\fR .PP -.IP \fBminidump\ file.mdmp\fR +.BI "minidump " file.mdmp saves the debugging context of the debuggee into a minidump file called -file.mdmp +\fIfile.mdmp\fR. .PP \fIInformation on Wine internals\fR .IP \fBinfo\ class\fR @@ -406,7 +392,7 @@ Since no user input is possible, no commands are available. .SH ENVIRONMENT .IP \fBWINE_GDB\fR When used in \fBgdb\fR proxy mode, \fBWINE_GDB\fR specifies the name -(and the path) of the executable to be used for \fBgdb\fR. \fB"gdb"\fR +(and the path) of the executable to be used for \fBgdb\fR. "gdb" is used by default. .SH AUTHORS The first version was written by Eric Youngdale.

1 0