| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
windmc may be used to generator Windows message resources.
Warning: windmc is not always built as part of the binary
utilities, since it is only useful for Windows targets.
windmc [options] input-file |
windmc reads message definitions from an input file (.mc) and
translate them into a set of output files. The output files may be of
four kinds:
h
rc
windres tool.
bin
dbg
The exact description of these different formats is available in documentation from Microsoft.
When windmc converts from the mc format to the bin
format, rc, h, and optional dbg it is acting like the
Windows Message Compiler.
-a
--ascii_in
-A
--ascii_out
bin files should be in ASCII
format.
-b
--binprefix
bin filenames should have to be prefixed by the
basename of the source file.
-c
--customflag
-C codepage
--codepage_in codepage
-d
--decimal_values
-e ext
--extension ext
-F target
--target target
windmc will use the default
format, which is the first one listed by the `--help' option.
18.1 Target Selection.
-h path
--headerdir path
-H
--help
-m characters
--maxlength characters
windmc to generate a warning if the length
of any message exceeds the number specified.
-n
--nullterminate
bin files by zero. By default they are
terminated by CR/LF.
-o
--hresult_use
windmc to generate an OLE2 header
file, using HRESULT definitions. Status codes are used if the flag is not
specified.
-O codepage
--codepage_out codepage
-r path
--rcdir path
rc script and the generated
bin files that the resource compiler script includes. The default
is the current directory.
-u
--unicode_in
-U
--unicode_out
bin file should be in UTF16
format. This is the default behaviour.
-v
--verbose
-V
--version
windmc.
-x path
--xdgb path
dbg C include file that maps message id's to the
symbolic name. No such file is generated without specifying the switch.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |