wine-commits July 2013

wine-commits@winehq.org

2 participants
447 discussions

Alexandre Julliard : Release 1.6.
by Alexandre Julliard 18 Jul '13

18 Jul '13

Module: wine Branch: master Commit: 50dc4cd636cc88031e0a49697ccc9f03b398e449 URL: http://source.winehq.org/git/wine.git/?a=commit;h=50dc4cd636cc88031e0a49697… Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Jul 18 19:57:36 2013 +0200 Release 1.6. --- ANNOUNCE | 698 +++++++++++++++++++++++++++++++++++++------------------------ VERSION | 2 +- configure | 18 +- 3 files changed, 433 insertions(+), 285 deletions(-) Diff: http://source.winehq.org/git/wine.git/?a=commitdiff;h=50dc4cd636cc88031e0a4…

1 0

Julian Rüger : winemaker: Update German translation of manpage.
by Alexandre Julliard 18 Jul '13

18 Jul '13

Module: wine Branch: master Commit: 166c79f25586e20d929f8a0d547a7285da9853a1 URL: http://source.winehq.org/git/wine.git/?a=commit;h=166c79f25586e20d929f8a0d5… Author: Julian Rüger <jr98(a)gmx.net> Date: Thu Jul 18 03:04:32 2013 +0200 winemaker: Update German translation of manpage. --- tools/winemaker.de.man.in | 216 ++++++++++++++++++++++++--------------------- 1 files changed, 116 insertions(+), 100 deletions(-) Diff: http://source.winehq.org/git/wine.git/?a=commitdiff;h=166c79f25586e20d929f8…

1 0

Frédéric Delanoy : winemaker: Update French translation of manpage.
by Alexandre Julliard 18 Jul '13

18 Jul '13

Module: wine Branch: master Commit: ee18a8b6cd767f683720f06d97a09773dcd7b505 URL: http://source.winehq.org/git/wine.git/?a=commit;h=ee18a8b6cd767f683720f06d9… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 23:43:39 2013 +0200 winemaker: Update French translation of manpage. --- tools/winemaker.fr.man.in | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/winemaker.fr.man.in b/tools/winemaker.fr.man.in index 6a1ce72..b126b8d 100644 --- a/tools/winemaker.fr.man.in +++ b/tools/winemaker.fr.man.in @@ -1,4 +1,3 @@ -.\" -*- nroff -*- .TH WINEMAKER 1 "jan 2012" "@PACKAGE_STRING@" "Manuel des développeurs de Wine" .SH NOM winemaker \- générer une infrastructure de construction pour la compilation de programmes Windows sur UNIX @@ -152,7 +151,7 @@ Spécifier que les cibles n'utilisent pas les MFC. Cette option empêche l'utilisation des bibliothèques MFC même si .B winemaker rencontre des fichiers « stdafx.cpp » ou « stdafx.h » qui activeraient -les MFC automatiquement en temps normal si ni --nomfc ni --mfc n'était +les MFC automatiquement en temps normal si ni \fB--nomfc\fR ni \fB--mfc\fR n'était spécifiée. .TP .BI -D macro "\fR[=\fIdéfn\fR]" @@ -177,7 +176,8 @@ Ajouter la bibliothèque spécifiée à la liste globale de bibliothèques à ut .TP .B --nodlls Ne pas utiliser l'ensemble standard de bibliothèques Winelib pour les imports, -c.-à-d. que toute DLL utilisée par votre code doit être explicitement spécifiée à l'aide d'options -i. +c.-à-d. que toute DLL utilisée par votre code doit être explicitement spécifiée à l'aide d'options +\fB-i\fR. L'ensemble standard de bibliothèques est\ : odbc32.dll, odbccp32.dll, ole32.dll, oleaut32.dll et winspool.drv. .TP @@ -193,7 +193,7 @@ demandera de confirmer la liste de cibles pour chaque répertoire, et ensuite de fournir des options spécifiques de répertoire et/ou de cible. .TP .BR --single-target " nom" -Spécifier qu'il n'y a qu'une seule cible, appelée « nom ». +Spécifier qu'il n'y a qu'une seule cible, appelée \fInom\fR. .TP .B --generated-files Générer le Makefile. Comportement par défaut.

1 0

Frédéric Delanoy : readme: Update French translation.
by Alexandre Julliard 18 Jul '13

18 Jul '13

Module: wine Branch: master Commit: 8852770348698d429d216323c71614654eaa90de URL: http://source.winehq.org/git/wine.git/?a=commit;h=8852770348698d429d216323c… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Thu Jul 18 00:57:26 2013 +0200 readme: Update French translation. --- documentation/README.fr | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/documentation/README.fr b/documentation/README.fr index bc2bee8..0d0c2ef 100644 --- a/documentation/README.fr +++ b/documentation/README.fr @@ -58,6 +58,7 @@ Informations NetBSD : Informations Mac OS X : Xcode 2.4 ou ultérieur est nécessaire pour compiler Wine sous x86. + Le pilote Mac requiert OS X 10.6 ou ultérieur et ne pourra être construit sous 10.5. Systèmes de fichiers pris en charge :

1 0

Frédéric Delanoy : widl: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: 267422101ad7cf45a32c2bf135e7d9b076b9ed37 URL: http://source.winehq.org/git/wine.git/?a=commit;h=267422101ad7cf45a32c2bf13… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:23 2013 +0200 widl: Fix manpage formatting. --- tools/widl/widl.man.in | 25 ++++++++++++------------- 1 files changed, 12 insertions(+), 13 deletions(-) diff --git a/tools/widl/widl.man.in b/tools/widl/widl.man.in index 82396ad..7e9b9fe 100644 --- a/tools/widl/widl.man.in +++ b/tools/widl/widl.man.in @@ -1,18 +1,17 @@ -.\" -*- nroff -*- .TH WIDL 1 "October 2007" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME widl \- Wine Interface Definition Language (IDL) compiler .SH SYNOPSIS .B widl -[\fIoptions\fR] \fIinfile\fR.idl +[\fIoptions\fR] \fIIDL_file\fR .br .B widl -[\fIoptions\fR] \fB--dlldata-only\fR \fIname1\fR [\fIname2\fR ...] +[\fIoptions\fR] \fB--dlldata-only\fR \fIname1\fR [\fIname2\fR...] .SH DESCRIPTION When no options are used the program will generate a header file, and possibly client and server stubs, proxy and dlldata files, a typelib, and a UUID file, depending on the contents of the IDL file. If any of the options \fB-c\fR, -\fB-h\fR, \fB-p\fR, \fB-s\fR, \fB-t\fR, \fB-u\fR, or \fB--local-stubs\fR are given, +\fB-h\fR, \fB-p\fR, \fB-s\fR, \fB-t\fR, \fB-u\fR or \fB--local-stubs\fR is given, .B widl will only generate the requested files, and no others. When run with \fB--dlldata-only\fR, widl will only generate a dlldata file, and it will @@ -35,10 +34,10 @@ Print version number and exit. Set the name of the output file. When generating multiple output files, this sets only the base name of the file; the respective output files are then named \fIname\fR.h, \fIname\fR_p.c, etc. -.IP "\fB-b \fIcpu-manufacturer[-kernel]-os\fR" +.IP "\fB-b \fIcpu-manufacturer\fR[\fB-\fIkernel\fR]\fB-\fIos\fR" Set the target architecture when cross-compiling. The target specification is in the standard autoconf format as returned by -config.sub. +\fBconfig.sub\fR. .PP .B Header options: .IP "\fB-h\fR" @@ -52,7 +51,7 @@ Generate a type library. The default output filename is \fIinfile\fB.tlb\fR. If the output file name ends in \fB.res\fR, a binary resource file containing the type library is generated instead. .IP "\fB-m32, -m64\fR" -Generate a Win32, respectively Win64, type library. +Generate a Win32 or Win64 type library respectively. .PP .B UUID file options: .IP "\fB-u\fR" @@ -78,8 +77,8 @@ Prefix to put on the name of server stubs. .IP "\fB-s\fR" Generate a server stub file. The default output filename is \fIinfile\fB_s.c\fR. -.IP "\fB--win32, --win64\fR" -Only generate 32-bit, respectively 64-bit code (the default is to +.IP "\fB--win32\fR, \fB--win64\fR" +Only generate 32-bit or 64-bit code respectively (the default is to generate both 32-bit and 64-bit versions into the same destination file). .PP @@ -90,7 +89,7 @@ Generate a registration script. The default output filename is binary resource file containing the script is generated instead. .PP .B Dlldata file options: -.IP "\fB--dlldata-only\fI name1 [name2...]" +.IP "\fB--dlldata-only\fI name1 \fR[\fIname2\fR...]" Regenerate the dlldata file from scratch using the specified proxy names. The default output filename is \fBdlldata.c\fR. .PP @@ -98,7 +97,7 @@ names. The default output filename is \fBdlldata.c\fR. .IP "\fB-I \fIpath\fR" Add a header search directory to path. Multiple search directories are allowed. -.IP "\fB-D \fIid\fR[=\fIval\fR]" +.IP "\fB-D \fIid\fR[\f\fB=\fIval\fR]" Define preprocessor macro \fIid\fR with value \fIval\fR. .IP "\fB-E\fR" Preprocess only. @@ -111,7 +110,7 @@ Enable pedantic warnings. .IP "\fB-d \fIn\fR" Set debug level to the non negative integer \fIn\fR. If prefixed with \fB0x\fR, it will be interpreted as an hexadecimal -number. For the meaning of values, see the \fBDebug\fR section. +number. For the meaning of values, see the \fBDEBUG\fR section. .PP .B Miscellaneous options: .IP "\fB-app_config\fR" @@ -135,7 +134,7 @@ Bugs can be reported on the .UE . .SH AUTHORS .B widl -was originally written by Ove Kaaven. It has been improved by Rob Shearman, +was originally written by Ove Kåven. It has been improved by Rob Shearman, Dan Hipschman, and others. For a complete list, see the git commit logs. This man page was originally written by Hannu Valtonen and then updated by Dan Hipschman.

1 0

Frédéric Delanoy : winedump: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: 621dc412477629cf7f5bcf347b7475e24e1640de URL: http://source.winehq.org/git/wine.git/?a=commit;h=621dc412477629cf7f5bcf347… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:22 2013 +0200 winedump: Fix manpage formatting. --- tools/winedump/winedump.man.in | 89 ++++++++++++++++++++-------------------- 1 files changed, 44 insertions(+), 45 deletions(-) diff --git a/tools/winedump/winedump.man.in b/tools/winedump/winedump.man.in index bae18cc..085e0fd 100644 --- a/tools/winedump/winedump.man.in +++ b/tools/winedump/winedump.man.in @@ -1,14 +1,13 @@ -.\" -*- nroff -*- .TH WINEDUMP 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME winedump \- A Wine DLL tool .SH SYNOPSIS .BR "winedump " [ "-h " "| " -.BI "sym " "<sym> " +.BI "sym " sym | -.BI "spec " "<dll> " +.BI "spec " dll | -.BI "dump " "<file>" +.BI "dump " file .RI "] [" "mode_options" ] .SH DESCRIPTION .B winedump @@ -21,7 +20,7 @@ B: Compiling a Win32 application with Winelib that uses x86 DLLs For both tasks in order to be able to link to the Win functions some glue code is needed. This 'glue' comes in the form of a \fI.spec\fR file. The \fI.spec\fR file, along with some dummy code, is used to create a -Wine .so corresponding to the Windows DLL. The \fBwinebuild\fR program +Wine \fI.so\fR corresponding to the Windows DLL. The \fBwinebuild\fR program can then resolve calls made to DLL functions. .PP Creating a \fI.spec\fR file is a labour intensive task during which it is @@ -30,7 +29,7 @@ and create the majority of the support code needed for your DLL. In addition you can have \fBwinedump\fR create code to help you re-implement a DLL, by providing tracing of calls to the DLL, and (in some cases) automatically determining the parameters, calling conventions, and -return values of the DLL's functions. +return values of the DLL functions. .PP Another use for this tool is to display (dump) information about a 32bit DLL or PE format image file. When used in this way \fBwinedump\fR functions @@ -41,7 +40,7 @@ Finally \fBwinedump\fR can be also used to demangle C++ symbols. .SH MODES .B winedump can be used in several different modes. The first argument to the -program determines the mode winedump will run in. +program determines the mode \fBwinedump\fR will run in. .IP \fB-h\fR Help mode. Basic usage help is printed. @@ -61,9 +60,9 @@ No options are used. The program prints the help info and than exits. .PP .B Dump mode: -.IP \fI<file>\fR -Dumps the content of the file named \fI<file>\fR. Various file -formats are supported (PE, NE, LE, Minidumps, .lnk). +.IP \fIfile\fR +Dumps the contents of \fIfile\fR. Various file formats are supported +(PE, NE, LE, Minidumps, .lnk). .IP \fB-C\fR Turns on symbol demangling. .IP \fB-f\fR @@ -81,33 +80,33 @@ implemented. Dumps everything. This command prints all available information (including all available directories - see \fB-j\fR option) about the file. You may -wish to pipe the output through more/less or into a file, since +wish to pipe the output through \fBmore\fR/\fBless\fR or into a file, since a lot of output will be produced. .IP \fB-G\fR Dumps contents of debug section if any (for now, only stabs information is supported). .PP .B Spec mode: -.IP \fI<dll>\fR -Use dll for input file and generate implementation code. +.IP \fIdll\fR +Use \fIdll\fR for input file and generate implementation code. .IP "\fB-I \fIdir\fR" -Look for prototypes in '\fIdir\fR' (implies \fB-c\fR). In the case of +Look for prototypes in \fIdir\fR (implies \fB-c\fR). In the case of Windows DLLs, this could be either the standard include directory from your compiler, or a SDK include directory. If you have a text document with prototypes (such as documentation) that can be used also, however you may need to delete some non-code lines to ensure that prototypes are parsed correctly. -The '\fIdir\fR' argument can also be a file specification (e.g. -"include/*"). If it contains wildcards you must quote it to +The \fIdir\fR argument can also be a file specification (e.g. +\fIinclude/*\fR). If it contains wildcards you must quote it to prevent the shell from expanding it. -If you have no prototypes, specify /dev/null for '\fIdir\fR'. -Winedump may still be able to generate some working stub +If you have no prototypes, specify \fI/dev/null\fR as \fIdir\fR. +\fBwinedump\fR may still be able to generate some working stub code for you. .IP \fB-c\fR Generate skeleton code (requires \fB-I\fR). -This option tells winedump to create function stubs for each -function in the DLL. As winedump reads each exported symbol +This option tells \fBwinedump\fR to create function stubs for each +function in the DLL. As \fBwinedump\fR reads each exported symbol from the source DLL, it first tries to demangle the name. If the name is a C++ symbol, the arguments, class and return value are all encoded into the symbol name. Winedump @@ -122,24 +121,24 @@ arguments are printed out when the function is called. Structs that are passed by value are printed as "struct", and functions that take variable argument lists print "...". .IP "\fB-f \fIdll\fR" -Forward calls to '\fIdll\fR' (implies \fB-t\fR). +Forward calls to \fIdll\fR (implies \fB-t\fR). This is the most complicated level of code generation. The same code is generated as \fB-t\fR, however support is added for forwarding calls to another DLL. The DLL to forward to is -given as '\fIdll\fR'. +given as \fIdll\fR. .IP \fB-D\fR Generate documentation. -By default, winedump generates a standard comment at the +By default, \fBwinedump\fR generates a standard comment at the header of each function it generates. Passing this option -makes winedump output a full header template for standard +makes \fBwinedump\fR output a full header template for standard Wine documentation, listing the parameters and return value of the function. .IP "\fB-o \fIname\fR" -Set the output dll name (default: \fIdll\fR). -By default, if winedump is run on DLL 'foo', it creates -files 'foo.spec', 'foo_main.c' etc, and prefixes any -functions generated with 'FOO_'. If '-o bar' is given, -these will become 'bar.spec', 'bar_main.c' and 'BAR_' +Set the output dll name (default: \fBdll\fR). +By default, if \fBwinedump\fR is run on DLL \fIfoo\fR, it creates +files \fIfoo.spec\fR, \fIfoo_main.c\fR etc, and prefixes any +functions generated with \fIFOO_\fR. If \fB-o \fIbar\fR is given, +these will become \fIbar.spec\fR, \fIbar_main.c\fR and \fIBAR_\fR respectively. This option is mostly useful when generating a forwarding DLL. .IP \fB-C\fR @@ -148,18 +147,18 @@ If winebuild cannot determine the calling convention, __stdcall is used by default, unless this option has been given. Unless \fB-q\fR is given, a warning will be printed for every -function that winedump determines the calling convention +function that \fBwinedump\fR determines the calling convention for and which does not match the assumed calling convention. .IP "\fB-s \fInum\fR" -Start prototype search after symbol '\fInum\fR'. +Start prototype search after symbol \fInum\fR. .IP "\fB-e \fInum\fR" -End prototype search after symbol '\fInum\fR'. -By passing the \fB-s\fR or \fB-e\fR options you can have winedump try to +End prototype search after symbol \fInum\fR. +By passing the \fB-s\fR or \fB-e\fR options you can have \fBwinedump\fR try to generate code for only some functions in your DLL. This may be used to generate a single function, for example, if you wanted to add functionality to an existing DLL. .IP "\fB-S \fIsymfile\fR" -Search only prototype names found in '\fIsymfile\fR'. +Search only prototype names found in \fIsymfile\fR. If you want to only generate code for a subset of exported functions from your source DLL, you can use this option to provide a text file containing the names of the symbols to @@ -170,17 +169,17 @@ Don't show progress (quiet). No output is printed unless a fatal error is encountered. .IP \fB-v\fR Show lots of detail while working (verbose). -There are 3 levels of output while winedump is running. The -default level, when neither -q or -v are given, prints the +There are 3 levels of output while \fBwinedump\fR is running. The +default level, when neither \fB-q\fR or \fB-v\fR are given, prints the number of exported functions found in the dll, followed by the name of each function as it is processed, and a status -indication of whether it was processed OK. With -v given, a -lot of information is dumped while winedump works: this is +indication of whether it was processed OK. With \fB-v\fR given, a +lot of information is dumped while \fBwinedump\fR works: this is intended to help debug any problems. .PP .B Sym mode: -.IP \fI<sym>\fR -Demangles C++ symbol '\fI<sym>\fR' and then exits. +.IP \fIsym\fR +Demangles C++ symbol \fIsym\fR and then exits. .SH FILES .I function_grep.pl .RS @@ -188,13 +187,13 @@ Perl script used to retrieve a function prototype. .RE .PP Files output in -.B spec mode +.BR spec " mode" for -.I foo.dll: +.IR foo.dll : .nf .I foo.spec .RS -This is the .spec file. +This is the \fI.spec\fR file. .RE .I foo_dll.h .nf @@ -202,12 +201,12 @@ This is the .spec file. .RS These are the source code files containing the minimum set of code to build a stub DLL. The C file contains one -function, FOO_Init, which does nothing (but must be +function, \fIFOO_Init\fR, which does nothing (but must be present). .RE .I Makefile.in .RS -This is a template for 'configure' to produce a makefile. It +This is a template for \fBconfigure\fR to produce a makefile. It is designed for a DLL that will be inserted into the Wine source tree. .SH BUGS

1 0

Frédéric Delanoy : wmc: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: 3864fd8d377e88ecde33a74f59e8ebf60112b9ca URL: http://source.winehq.org/git/wine.git/?a=commit;h=3864fd8d377e88ecde33a74f5… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:21 2013 +0200 wmc: Fix manpage formatting. --- tools/wmc/wmc.man.in | 30 +++++++++++++++--------------- 1 files changed, 15 insertions(+), 15 deletions(-) diff --git a/tools/wmc/wmc.man.in b/tools/wmc/wmc.man.in index e5eb317..890f716 100644 --- a/tools/wmc/wmc.man.in +++ b/tools/wmc/wmc.man.in @@ -1,9 +1,9 @@ -.\" -*- nroff -*- .TH WMC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME wmc \- Wine Message Compiler .SH SYNOPSIS -.BI "wmc " "[options] " "[inputfile]" +.B wmc +.RI [ options ]\ [ inputfile ] .SH DESCRIPTION .B wmc compiles messages from @@ -11,15 +11,15 @@ compiles messages from into FormatMessage[AW] compatible format encapsulated in a resourcescript format. .B wmc -outputs the data either in a standard \fB.bin\fR formatted binary +outputs the data either in a standard \fI.bin\fR formatted binary file, or can generated inline resource data. .PP .B wmc -takes only one \fBinputfile\fR as argument (see \fBBUGS\fR). The -\fBinputfile\fR normally has extension \fB.mc\fR. The messages are read from +takes only one \fIinputfile\fR as argument (see \fBBUGS\fR). The +\fIinputfile\fR normally has extension \fI.mc\fR. The messages are read from standard input if no inputfile is given. If the outputfile is not specified -with \fI-o\fR, then \fBwmc\fR will write the output to \fBinputfile.{rc,h}\fR. -The outputfile is named \fBwmc.tab.{rc,h}\fR if no inputfile was given. +with \fB-o\fR, then \fBwmc\fR will write the output to \fIinputfile.{rc,h}\fR. +The outputfile is named \fIwmc.tab.{rc,h}\fR if no inputfile was given. .SH OPTIONS .TP .BI \-B\ x @@ -55,7 +55,7 @@ Set the output format. Supported formats are \fBrc\fR (the default), .BI \-P\ directory Enable the generation of resource translations based on po files loaded from the specified directory. That directory must follow the -gettext convention, in particular in must contain one .po file for +gettext convention, in particular in must contain one \fI.po\fR file for each language, and a LINGUAS file listing the available languages. .TP .B \-u @@ -74,30 +74,30 @@ Print version end exit. Enable pedantic warnings. .SH EXTENSIONS The original syntax is extended to support codepages more smoothly. Normally, -codepages are based on the DOS\-codepage from the language setting. The +codepages are based on the DOS codepage from the language setting. The original syntax only allows the destination codepage to be set. However, this is not enough for non\-DOS systems which do not use unicode source-files. .PP -A new keyword \fICodepages\fR is introduced to set both input and output +A new keyword \fBCodepages\fR is introduced to set both input and output codepages to anything one wants for each language. The syntax is similar to the other constructs: .PP Codepages '=' '(' language '=' cpin ':' cpout ... ')' .PP The \fIlanguage\fR is the numerical language\-ID or the alias set with -LanguageNames. The input\-codepage \fIcpin\fR and output\-codepage -\fIcpout\fR are the numerical codepage\-IDs. There can be multiple mapping +LanguageNames. The input codepage \fIcpin\fR and output codepage +\fIcpout\fR are the numerical codepage IDs. There can be multiple mappings within the definition and the definition may occur more than once. .SH AUTHORS .B wmc was written by Bertho A. Stultiens. .SH BUGS -The message compiler should be able to have multiple inputfiles and combine -them into one outputfile. This would enable the splitting of languages into +The message compiler should be able to have multiple input files and combine +them into one output file. This would enable the splitting of languages into separate files. .PP Unicode detection of the input is suboptimal, to say the least. It should -recognize byte\-order\-marks (BOM) and decide what to do. +recognize byte order marks (BOM) and decide what to do. .PP Decimal output is completely lacking. Don't know whether it should be implemented because it is a, well, non-informative format change. It is

1 0

Frédéric Delanoy : wrc: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: f753720eb594de7e47eb4f2a3440bd6c5eeb5d08 URL: http://source.winehq.org/git/wine.git/?a=commit;h=f753720eb594de7e47eb4f2a3… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:20 2013 +0200 wrc: Fix manpage formatting. --- tools/wrc/wrc.man.in | 50 +++++++++++++++++++++++++------------------------- 1 files changed, 25 insertions(+), 25 deletions(-) diff --git a/tools/wrc/wrc.man.in b/tools/wrc/wrc.man.in index 0eeed9c..3c4683f 100644 --- a/tools/wrc/wrc.man.in +++ b/tools/wrc/wrc.man.in @@ -1,32 +1,32 @@ -.\" -*- nroff -*- .TH WRC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME wrc \- Wine Resource Compiler .SH SYNOPSIS -.BI "wrc " "[options] " "[inputfiles]" +.B wrc +.RI [ options ]\ [ inputfile ...] .SH DESCRIPTION .B wrc -compiles resources from \fBinputfile\fR +compiles resources from \fIinputfile\fR into win16 and win32 compatible binary format. .PP -The source\-file is preprocessed with a builtin ANSI\-C compatible +The source file is preprocessed with a builtin ANSI\-C compatible preprocessor before the resources are compiled. See \fBPREPROCESSOR\fR below. .PP .B wrc -takes a series of \fBinputfile\fR as argument. The resources are read from -standard input if no inputfile is given. If the output file is not -specified with \fI-o\fR, then \fBwrc\fR will write the output to -\fBinputfile.res\fR with \fB.rc\fR stripped, or to \fBwrc.tab.res\fR if +takes a series of \fIinputfile\fR as argument. The resources are read from +standard input if no inputfile is given. If the output file is not +specified with \fB-o\fR, then \fBwrc\fR will write the output to +\fIinputfile.res\fR with \fI.rc\fR stripped, or to \fIwrc.tab.res\fR if no inputfile was given. .SH OPTIONS .TP -.BI \-b,\ --target= cpu-manufacturer[-kernel]-os +.BI \-b,\ --target= cpu-manufacturer\fR[\fI\fB-\fIkernel\fR]\fB-\fIos Specify the target CPU and platform on which the generated code will be built. The target specification is in the standard autoconf format -as returned by config.sub. +as returned by \fBconfig.sub\fR. .TP -.I \fB\-D\fR, \fB\-\-define\fR=\fIid[=val]\fR +.I \fB\-D\fR, \fB\-\-define\fR=\fIid\fR[\fB=\fIval\fR] Define preprocessor identifier \fIid\fR to (optionally) value \fIval\fR. See also .B PREPROCESSOR @@ -56,14 +56,14 @@ The name of the input file. If this option is not used, then \fBwrc\fR will use the first non-option argument as the input file name. If there are no non-option arguments, then \fBwrc\fR will read from standard input. .TP -.I \fB\-I\fR, \fB\-\-include\-dir\fR=\fIfile\fR -Add \fIpath\fR to include search directories. \fIPath\fR may contain +.I \fB\-I\fR, \fB\-\-include\-dir\fR=\fIpath\fR +Add \fIpath\fR to include search directories. \fIpath\fR may contain multiple directories, separated with ':'. It is allowed to specify -\fI\-I\fR multiple times. Include files are searched in the order in -with the \fI\-I\fR options were specified. +\fB\-I\fR multiple times. Include files are searched in the order in +which the \fB\-I\fR options were specified. .br The search is compatible with gcc, in which '<>' quoted filenames are -searched exclusively via the \fI\-I\fR set path, whereas the '""' quoted +searched exclusively via the \fB\-I\fR set path, whereas the '""' quoted filenames are first tried to be opened in the current directory. Also resource statements with file references are located in the same way. .TP @@ -71,18 +71,18 @@ resource statements with file references are located in the same way. Sets the input format. Valid options are 'rc' or 'rc16'. Setting the input to 'rc16' disables the recognition of win32 keywords. .TP -.I \fB\-l\fR, \fB\-\-language\fR=\fIlan\fR -Set default language to \fIlan\fR. Default is the neutral language 0 +.I \fB\-l\fR, \fB\-\-language\fR=\fIlang\fR +Set default language to \fIlang\fR. Default is the neutral language 0 (i.e. "LANGUAGE 0, 0"). .TP .B \-m16, -m32, -m64 -Generate resources for 16-bit, 32-bit, respectively 64-bit -platforms. The only difference between 32-bit and 64-bit is whether +Generate resources for 16-bit, 32-bit or 64-bit platforms respectively. +The only difference between 32-bit and 64-bit is whether the _WIN64 preprocessor symbol is defined. .TP .I \fB\-\-nostdinc\fR Do not search the standard include path, look for include files only -in the directories explicitly specified with the \fI\-I\fR option. +in the directories explicitly specified with the \fB\-I\fR option. .TP .I \fB\-\-no\-use\-temp\-file\fR Ignored for compatibility with \fIwindres\fR. @@ -100,7 +100,7 @@ format defaults to \fBres\fR. In \fBpo\fR mode, if an output file name is specified it must match a known language name, like \fBen_US.po\fR; only resources for the specified language are output. If no output file name is specified, a -separate .po file is created for every language encountered in the +separate \fI.po\fR file is created for every language encountered in the input. .TP .I \fB\-\-pedantic\fR @@ -110,7 +110,7 @@ be discovered with this option. .I \fB\-\-po-dir=\fIdir\fR Enable the generation of resource translations based on mo files loaded from the specified directory. That directory must follow the -gettext convention, in particular in must contain one .mo file for +gettext convention, in particular it must contain one \fI.mo\fR file for each language, and a LINGUAS file listing the available languages. .TP .I \fB\-r\fR @@ -133,10 +133,10 @@ below. Ignored for compatibility with \fIwindres\fR. .TP .I \fB\-v\fR, \fB\-\-verbose\fR -Turns on verbose mode (equivalent to -d 1). +Turns on verbose mode (equivalent to \fB-d 1\fR). .TP .I \fB\-\-version\fR -Print version end exit. +Print version and exit. .SH PREPROCESSOR The preprocessor is ANSI\-C compatible with some of the extensions of the gcc preprocessor.

1 0

Frédéric Delanoy : winebuild: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: 5dc595a6d90762de8e2290a7dbf6ef997304f18f URL: http://source.winehq.org/git/wine.git/?a=commit;h=5dc595a6d90762de8e2290a7d… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:19 2013 +0200 winebuild: Fix manpage formatting. --- tools/winebuild/winebuild.man.in | 34 +++++++++++++++++----------------- 1 files changed, 17 insertions(+), 17 deletions(-) diff --git a/tools/winebuild/winebuild.man.in b/tools/winebuild/winebuild.man.in index c729499..b0b2784 100644 --- a/tools/winebuild/winebuild.man.in +++ b/tools/winebuild/winebuild.man.in @@ -1,9 +1,9 @@ -.\" -*- nroff -*- .TH WINEBUILD 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME winebuild \- Wine dll builder .SH SYNOPSIS -.BI winebuild\ [options]\ [input\ files] +.B winebuild +.RI [ options ]\ [ inputfile ...] .SH DESCRIPTION .B winebuild generates the assembly files that are necessary to build a Wine dll, @@ -21,7 +21,7 @@ what you want winebuild to generate. .BI \--dll Build an assembly file from a .spec file (see \fBSPEC FILE SYNTAX\fR for details), or from a standard Windows .def file. The .spec/.def -file is specified via the -E option. The resulting file must be +file is specified via the \fB-E\fR option. The resulting file must be assembled and linked to the other object files to build a working Wine dll. In this mode, the .I input files @@ -33,22 +33,22 @@ other dlls. .TP .BI \--exe Build an assembly file for an executable. This is basically the same as -the --dll mode except that it doesn't require a .spec/.def file as input, +the \fB--dll\fR mode except that it doesn't require a .spec/.def file as input, since an executable need not export functions. Some executables however do export functions, and for those a .spec/.def file can be specified via -the -E option. The executable is named from the .spec/.def file name if -present, or explicitly through the -F option. The resulting file must be +the \fB-E\fR option. The executable is named from the .spec/.def file name if +present, or explicitly through the \fB-F\fR option. The resulting file must be assembled and linked to the other object files to build a working Wine executable, and all the other object files must be listed as .I input files. .TP .BI \--def Build a .def file from a spec file. The .spec file is specified via the --E option. This is used when building dlls with a PE (Win32) compiler. +\fB-E\fR option. This is used when building dlls with a PE (Win32) compiler. .TP .BI \--implib Build a PE import library from a spec file. The .spec file is -specified via the -E option. +specified via the \fB-E\fR option. .TP .B \--resources Generate a .o file containing all the input resources. This is useful @@ -62,7 +62,7 @@ so there's no need for an intermediate .o file. Specify the command to use to compile assembly files; the default is \fBas\fR. .TP -.BI \-b,\ --target= cpu-manufacturer[-kernel]-os +.BI \-b,\ --target= cpu-manufacturer\fR[\fB-\fIkernel\fR]\fB-\fIos Specify the target CPU and platform on which the generated code will be built. The target specification is in the standard autoconf format as returned by config.sub. @@ -154,7 +154,7 @@ Import the specified library, looking for a corresponding option. .TP .B \-m16, -m32, -m64 -Generate 16-bit, 32-bit, respectively 64-bit code. +Generate respectively 16-bit, 32-bit or 64-bit code. .TP .BI \-M,\ --main-module= module When building a 16-bit dll, set the name of its 32-bit counterpart to @@ -171,20 +171,20 @@ KRNL386.EXE. It shouldn't be needed otherwise. Specify the command to use to get the list of undefined symbols; the default is \fBnm\fR. .TP -.BI --nxcompat= yes|no +.BI --nxcompat= yes\fR|\fIno Specify whether the module is compatible with no-exec support. The default is yes. .TP .BI \-o,\ --output= file Set the name of the output file (default is standard output). If the -output file name end in \fB.o\fR, the text output is sent to a +output file name ends in .o, the text output is sent to a temporary file that is then assembled to produce the specified .o file. .TP .BI \-r,\ --res= rsrc.res Load resources from the specified binary resource file. The \fIrsrc.res\fR file can be produced from a source resource file with -.BR wrc(1) +.BR wrc (1) (or with a Windows resource compiler). .br This option is only necessary for Win16 resource files, the Win32 ones @@ -197,7 +197,7 @@ option will also work for Win32 files). .B --save-temps Do not delete the various temporary files that \fBwinebuild\fR generates. .TP -.BI --subsystem= subsystem[:major[.minor]] +.BI --subsystem= subsystem\fR[\fB:\fImajor\fR[\fB.\fIminor\fR]] Set the subsystem of the executable, which can be one of the following: .br .B console @@ -227,7 +227,7 @@ library to be included when resolving imports. .TP .B \-v, --verbose Display the various subcommands being invoked by -.B winebuild. +.BR winebuild . .TP .B \--version Display the program version and exit. @@ -296,10 +296,10 @@ accessed through GetProcAddress. The entry point will be imported by ordinal instead of by name. The name is still exported. .TP -.BI -arch= cpu[,cpu] +.BI -arch= cpu\fR[\fB,\fIcpu\fR] The entry point is only available on the specified CPU architecture(s). The names \fBwin32\fR and \fBwin64\fR match all -32-bit, respectively 64-bit, CPU architectures. In 16-bit dlls, +32-bit or 64-bit CPU architectures respectively. In 16-bit dlls, specifying \fB-arch=win32\fR causes the entry point to be exported from the 32-bit wrapper module. .SS "Function ordinals"

1 0

Frédéric Delanoy : winemaker: Fix manpage formatting.
by Alexandre Julliard 17 Jul '13

17 Jul '13

Module: wine Branch: master Commit: 7b8b39f69c6742a9e435e2e1fe19ba9d44edae4e URL: http://source.winehq.org/git/wine.git/?a=commit;h=7b8b39f69c6742a9e435e2e1f… Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com> Date: Wed Jul 17 16:45:18 2013 +0200 winemaker: Fix manpage formatting. --- tools/winemaker.man.in | 13 ++++++------- 1 files changed, 6 insertions(+), 7 deletions(-) diff --git a/tools/winemaker.man.in b/tools/winemaker.man.in index e41a843..7abffcc 100644 --- a/tools/winemaker.man.in +++ b/tools/winemaker.man.in @@ -1,4 +1,3 @@ -.\" -*- nroff -*- .TH WINEMAKER 1 "Jan 2012" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME winemaker \- generate a build infrastructure for compiling Windows programs on Unix @@ -48,7 +47,7 @@ In order to do this winemaker can perform the following operations: - rename your source files and directories to lowercase in the event they got all uppercased during the transfer. .PP -- perform Dos to Unix (CRLF to LF) conversions. +- perform DOS to Unix (CRLF to LF) conversions. .PP - scan the include statements and resource file references to replace the backslashes with forward slashes. @@ -84,7 +83,7 @@ makes changes. This is the default. Tells winemaker not to backup modified source files. .TP .B --nosource-fix -Directs winemaker not to try fixing the source files (e.g. Dos to Unix +Directs winemaker not to try fixing the source files (e.g. DOS to Unix conversion). This prevents complaints if the files are readonly. .TP .B --lower-all @@ -136,7 +135,7 @@ MFC library. .B --nomfc Specifies that targets are not MFC-based. This option disables use of MFC libraries even if winemaker encounters files "stdafx.cpp" or "stdafx.h" that would cause it -to enable MFC automatically if neither --nomfc nor --mfc was specified. +to enable MFC automatically if neither \fB--nomfc\fR nor \fB--mfc\fR was specified. .TP .BI -D macro "\fR[=\fIdefn\fR]" Adds the specified macro definition to the global list of macro definitions. @@ -159,7 +158,7 @@ Adds the specified library to the global list of libraries to link with. .B --nodlls This option tells winemaker not to use the standard set of winelib libraries for imports. That is, any DLL your code uses must be explicitly passed to -winemaker with -i options. +winemaker with \fB-i\fR options. The standard set of libraries is: odbc32.dll, odbccp32.dll, ole32.dll, oleaut32.dll and winspool.drv. .TP @@ -172,8 +171,8 @@ Puts winemaker in interactive mode. In this mode winemaker will ask you to confirm each directory's list of targets, and then to provide directory and target specific options. .TP -.BR --single-target " name" -Specifies that there is only one target, and that it is called "name". +.BI --single-target " name" +Specifies that there is only one target, called \fIname\fR. .TP .B --generated-files Tells winemaker to generate the Makefile. This is the default.

1 0

← Newer
1
...
21
22
23
24
25
26
27
...
45
Older →

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-commits July 2013