Automatically generated by Pod::Man v1.37, Pod::Parser v1.32 Standard preamble: ========================================================================
\\$1
..
..
..
..
Set up some character translations and predefined strings. \*(-- will give an unbreakable dash, \*(PI will give pi, \*(L" will give a left double quote, and \*(R" will give a right double quote. | will give a real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to do unbreakable dashes and therefore won't be available. \*(C` and \*(C' expand to `' in nroff, nothing in troff, for use with C<>..tr \(*W-|\(bv\*(Tr
. ds -- \(*W-
. ds PI pi
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
. ds L" ""
. ds R" ""
. ds C` ""
. ds C' ""
'br\}
. ds -- \|\(em\|
. ds PI \(*p
. ds L" ``
. ds R" ''
'br\}
If the F register is turned on, we'll generate index entries on stderr for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index entries marked with X<> in POD. Of course, you'll have to process the output yourself in some meaningful fashion.. de IX
. tm Index:\\$1\t\\n%\t"\\$2"
..
. nr % 0
. rr F
.\}
For nroff, turn off justification. Always turn off hyphenation; it makes way too many mistakes in technical documents. Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). Fear. Run. Save yourself. No user-serviceable parts.. \" fudge factors for nroff and troff
. ds #H 0
. ds #V .8m
. ds #F .3m
. ds #[ \f1
. ds #]
.\}
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. ds #V .6m
. ds #F 0
. ds #[ \&
. ds #] \&
.\}
. \" simple accents for nroff and troff
. ds ' \&
. ds ` \&
. ds ^ \&
. ds , \&
. ds ~ ~
. ds /
.\}
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
. \" troff and (daisy-wheel) nroff accents
. \" corrections for vroff
. \" for low resolution devices (crt and lpr)
\{\
. ds : e
. ds 8 ss
. ds o a
. ds d- d\h'-1'\(ga
. ds D- D\h'-1'\(hy
. ds th \o'bp'
. ds Th \o'LP'
. ds ae ae
. ds Ae AE
.\}
======================================================================== Title "WINDRES 1" WINDRES 1 "2008-09-10" "binutils-2.18.90" "GNU Development Tools"
"NAME"
windres - manipulate Windows resources.
"SYNOPSIS"
Header "SYNOPSIS" windmc [options] input-file
windres [options] [input-file] [output-file]
"DESCRIPTION"
Header "DESCRIPTION" \fBwindres reads resources from an input file and copies them into
an output file. Either file may be in one of three formats:
Item "rc" A text format read by the Resource Compiler.
Item "res" A binary format generated by the Resource Compiler.
Item "coff" A \s-1COFF\s0 object or executable.
The exact description of these different formats is available in
documentation from Microsoft.
When windres converts from the \*(C`rc\*(C' format to the \*(C`res\*(C'
format, it is acting like the Windows Resource Compiler. When
\fBwindres converts from the \*(C`res\*(C' format to the \*(C`coff\*(C'
format, it is acting like the Windows \*(C`CVTRES\*(C' program.
When windres generates an \*(C`rc\*(C' file, the output is similar
but not identical to the format expected for the input. When an input
\f(CW\*(C`rc\*(C' file refers to an external filename, an output \*(C`rc\*(C' file
will instead include the file contents.
If the input or output format is not specified, windres will
guess based on the file name, or, for the input file, the file contents.
A file with an extension of .rc will be treated as an \*(C`rc\*(C'
file, a file with an extension of .res will be treated as a
\f(CW\*(C`res\*(C' file, and a file with an extension of .o or
\fI.exe will be treated as a \*(C`coff\*(C' file.
If no output file is specified, windres will print the resources
in \*(C`rc\*(C' format to standard output.
The normal use is for you to write an \*(C`rc\*(C' file, use windres
to convert it to a \s-1COFF\s0 object file, and then link the \s-1COFF\s0 file into
your application. This will make the resources described in the
\f(CW\*(C`rc\*(C' file available to Windows.
"OPTIONS"
Header "OPTIONS" "-i filename" 4
Item "-i filename" 0
"--input filename" 4
Item "--input filename"
The name of the input file. If this option is not used, then
\fBwindres will use the first non-option argument as the input file
name. If there are no non-option arguments, then windres will
read from standard input. windres can not read a \s-1COFF\s0 file from
standard input.
"-o filename" 4
Item "-o filename" 0
"--output filename" 4
Item "--output filename"
The name of the output file. If this option is not used, then
\fBwindres will use the first non-option argument, after any used
for the input file name, as the output file name. If there is no
non-option argument, then windres will write to standard output.
\fBwindres can not write a \s-1COFF\s0 file to standard output. Note,
for compatibility with rc the option -fo is also
accepted, but its use is not recommended.
"-J format" 4
Item "-J format" 0
"--input-format format" 4
Item "--input-format format"
The input format to read. format may be res, rc, or
\fBcoff. If no input format is specified, windres will
guess, as described above.
"-O format" 4
Item "-O format" 0
"--output-format format" 4
Item "--output-format format"
The output format to generate. format may be res,
\fBrc, or coff. If no output format is specified,
\fBwindres will guess, as described above.
"-F target" 4
Item "-F target" 0
"--target target" 4
Item "--target target"
Specify the \s-1BFD\s0 format to use for a \s-1COFF\s0 file as input or output. This
is a \s-1BFD\s0 target name; you can use the --help option to see a list
of supported targets. Normally windres will use the default
format, which is the first one listed by the --help option.
"--preprocessor program" 4
Item "--preprocessor program" When
windres reads an
\*(C`rc\*(C' file, it runs it through the C
preprocessor first. This option may be used to specify the preprocessor
to use, including any leading arguments. The default preprocessor
argument is
\*(C`gcc -E -xc-header -DRC_INVOKED\*(C'.
"-I directory" 4
Item "-I directory" 0
"--include-dir directory" 4
Item "--include-dir directory"
Specify an include directory to use when reading an \*(C`rc\*(C' file.
\fBwindres will pass this to the preprocessor as an -I
option. windres will also search this directory when looking for
files named in the \*(C`rc\*(C' file. If the argument passed to this command
matches any of the supported formats (as described in the -J
option), it will issue a deprecation warning, and behave just like the
\fB-J option. New programs should not use this behaviour. If a
directory happens to match a format, simple prefix it with ./
to disable the backward compatibility.
"-D target" 4
Item "-D target" 0
"--define sym[=val]" 4
Item "--define sym[=val]"
Specify a -D option to pass to the preprocessor when reading an
\f(CW\*(C`rc\*(C' file.
"-U target" 4
Item "-U target" 0
"--undefine sym" 4
Item "--undefine sym"
Specify a -U option to pass to the preprocessor when reading an
\f(CW\*(C`rc\*(C' file.
"-r" 4
Item "-r" Ignored for compatibility with rc.
"-v" 4
Item "-v" Enable verbose mode. This tells you what the preprocessor is if you
didn't specify one.
"-c val" 4
Item "-c val" 0
"--codepage val" 4
Item "--codepage val"
Specify the default codepage to use when reading an \*(C`rc\*(C' file.
\fIval should be a hexadecimal prefixed by 0x or decimal
codepage code. The valid range is from zero up to 0xffff, but the
validity of the codepage is host and configuration dependent.
"-l val" 4
Item "-l val" 0
"--language val" 4
Item "--language val"
Specify the default language to use when reading an \*(C`rc\*(C' file.
\fIval should be a hexadecimal language code. The low eight bits are
the language, and the high eight bits are the sublanguage.
"--use-temp-file" 4
Item "--use-temp-file" Use a temporary file to instead of using popen to read the output of
the preprocessor. Use this option if the popen implementation is buggy
on the host (eg., certain non-English language versions of Windows 95 and
Windows 98 are known to have buggy popen where the output will instead
go the console).
"--no-use-temp-file" 4
Item "--no-use-temp-file" Use popen, not a temporary file, to read the output of the preprocessor.
This is the default behaviour.
"-h" 4
Item "-h" 0
"--help" 4
Item "--help"
Prints a usage summary.
"-V" 4
Item "-V" 0
"--version" 4
Item "--version"
Prints the version number for windres.
"--yydebug" 4
Item "--yydebug" If
windres is compiled with
\*(C`YYDEBUG\*(C' defined as
1,
this will turn on parser debugging.
"@file" 4
Item "@file" Read command-line options from
file. The options read are
inserted in place of the original @
file option. If
file
does not exist, or cannot be read, then the option will be treated
literally, and not removed.
.Sp
Options in
file are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
with a backslash. The
file may itself contain additional
@
file options; any such options will be processed recursively.
"SEE ALSO"
Header "SEE ALSO" the Info entries for
binutils.
"COPYRIGHT"
Header "COPYRIGHT" Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, with no Front-Cover Texts, and with no
Back-Cover Texts. A copy of the license is included in the
section entitled \*(L"\s-1GNU\s0 Free Documentation License\*(R".