digitalmars.com
Last update Sun Mar 4 11:58:08 2018
Compiler & Tools Guide
Tools
BCC
CHMOD
CL
COFF2OMF
COFFIMPLIB
DMC
DIFF
DIFFDIR
DMAN
DUMP
DUMPOBJ
DUMPEXE
EXE2BIN
FLPYIMG
GREP
HC
HTOD
IMPLIB
LIB
LIBUNRES
MAKE
MAKEDEP
ME
OBJ2ASM
PATCHOBJ
RC
RCC
SC
SHELL
SMAKE
TOUCH
UNMANGLE
WHEREIS
Compiling
Compiling Code
C Implementation
C++ Implementation
C++0x Implementation
Language Extensions
Mixing Languages
Assembly Language
Inline Assembler
Optimizing Code
Numerics Programming
Regular Expressions
Acrtused
Pragmas
Precompiled Headers
Predefined Macros
Warning Messages
Error Messages
Runtime Messages
Linking
Optlink
Switches
Module Definition Files
Operation and Design
Error Messages
Win32 Programming
Win32 Programming
DOS and Win16 Programming
Memory Models
16 Bit Pointer Types and Type Modifiers
Handle Pointers
DOS
DOS 32 (DOSX)
Win16
Win16 DLLs
Win16 Prolog/Epilog
Virtual Memory For 640Kb DOS
C/C++ Extensions
Contract Programming
__debug statement
__debug declaration
Dynamic Profiling
Embedding C in HTML
Porting to DMC++
Switching to DMC++
from Microsoft
from Borland
Porting Guide
<h1><a name="ctgRC">Compiling Resources with RC</a> </h1> This chapter describes the Microsoft Resource Compiler (<strong>rc</strong>) - a tool that compiles resources such as icons, cursors, menus, and dialog boxes, that your application uses. You add the resulting binary resource file to the application's binary file to produce an executable Windows 3.x application. <p> <strong>Note:</strong> When building a program with the IDDE, it calls Digital Mars' <a href="/index.cgi/contrast/https://digitalmars.com/ctg/rcc.html">rcc</a> resource compiler to compile the program's resources (the Digital Mars linker actually binds the resources to the executable). In contrast, <strong>rc</strong> both compiles the resources and binds them to the executable. <h3>What's in This Chapter</h3> <ul> <li> How to include resources in an application. <li> How to create resource scripts. <li> <strong>rc</strong> command line syntax and options. </ul> <h3>Including Resources in an Application</h3> To include resources in a Windows 3.x application, follow these steps: <ol> <li> Create individual resource files for cursors, icons, bitmaps, dialogs, and fonts, using the appropriate resource editors. <li> Create a resource script (.rc) file that defines each application resource by specifying its name and description. If the resource is in a separate file, this description includes that file's name. For example, the .rc file might define a cursor resource by naming it SampleCursor, describing it as a resource of type Cursor, and defining it as the cursor contained in the file sample.cur. <li> Compile the resource script file using <strong>rc</strong>. The result will be a compiled resource file with the file extension .res. <li> Add the compiled resources to the application's compiled executable (.exe) file using <strong>rc</strong>. You can perform this step and the preceding step with a single <strong>rc</strong> command. </ol> <h3>Creating a Resource Script File</h3> After creating individual resource files for the application's icon, cursor, bitmap, font, and dialog resources, create a resource script file. The resource script file always has the .rc extension and is often referred to simply as the .rc file. <p> The resource script file lists every resource in the application and describes some types of resources in detail: <ul> <li> For resources that exist in a separate file, such as icons and cursors, the resource script file simply names the resource and the file that contains it. <li> For some types of resources, such as menus, the entire definition of the resource exists within the resource script file. </ul> Create a resource script file using any ASCII text editor. The file can contain resource statements and directives. Resource statements name and describe each resource. Directives are a special type of statement that define an action you want <strong>rc</strong> to perform on the resource script file before actually compiling it. You can use directives to assign values to names, include the contents of files, and control compilation of the script file. You use directives in a resource script file the same way you use the corresponding C language directives. <p> <strong>Note:</strong> A line in the resource script file cannot exceed 256 characters. <h3>Using <strong>rc</strong></h3> <strong>rc</strong> does the following: <ul> <li> Compiles the resource script file and the resource files, such as icon and cursor files, into a binary resource (.res) file. <li> Combines the compiled resource file with the executable (.exe) file created by the linker. The result is an executable Win16 application. <li> Marks all Win16 applications (even if they have no resources) with a Windows version stamp. </ul> <p>To start <strong>rc</strong>, use the <strong>rc</strong> command. What you specify on the command line will depend on whether you are compiling resources, adding compiled resources to an executable file, or both. For more information, see the section "Different Ways to Use the <strong>rc</strong> Command" later in this chapter. </p> <h3><strong>rc</strong> command syntax</h3> <p><strong>rc</strong> commands have the following form:</p> <pre><strong>rc</strong> [options] [resource-file] [executable-file] </pre> <p>The options are command line options. The resource-file is the name of the resource file, and executable-file is the name of the executable with which you want to combine resource-file. These command parameters are described below. </p> <h3>The "options" parameter</h3> <p><strong>rc</strong> options are not case-sensitive. For example, -r and -R are equivalent. You can combine single-letter options if they do not require any additional parameters. For example, the command: </p> <pre><strong>rc</strong> -R -E -V sample.rc </pre> <p>is equivalent to the command:</p> <pre><strong>rc</strong> -REV sample.rc </pre> <p>The options parameter can include one or more of the <strong>rc</strong> options described in the section below. </p> <h3>Resource-file parameter</h3> <p>The resource-file parameter specifies the name of the script file that contains the names, types, filenames, and descriptions of the resources you want to add to the executable file. It can also specify the name of a compiled resource file in which case <strong>rc</strong> adds the compiled resources to the executable file. </p> <h3>Executable-file parameter</h3> <p>The executable-file parameter specifies the name of the executable file to which the resources should be added. If you do not specify an executable file, <strong>rc</strong> uses the executable file with the same name as the script file. </p> <h3><strong>rc</strong> Options</h3> <p>This section describes the options you can use with <strong>rc</strong>.</p> <h4>-D</h4> <p>Defines a symbol for the preprocessor that testable with the #ifdef directive. </p> <p>You can specify conditional branching in a resource script file based on whether or not a term is defined on the <strong>rc</strong> command line using the -D option. For example, suppose your application has a pop-up menu, the Debug menu, which you want to appear only during debugging. When you compile the application for normal use, the Debug menu is not included. Your resource script file contains the following statements to define the Debug menu: </p> <pre>MainMenu MENU BEGIN ... #ifdef DEBUG POPUP &Debug BEGIN MENUITEM &Memory usage, ID_MEMORY MENUITEM &Walk data heap, ID_WALK_HEAP END #endif END </pre> <p>When compiling resources for a debugging version of the application, you include the Debug menu by using the following command: </p> <pre><strong>rc</strong> -R -D DEBUG myapp.rc </pre> <p>To compile resources for a version of the application that does not include the Debug menu, you would use the following command: </p> <pre><strong>rc</strong> -R myapp.rc </pre> <h3>Naming files</h3> <p>These switches control how <strong>rc</strong> names the executable and resource files it creates. </p> <dl><dt>-FE</dt> <dd>Names the executable file</dd> <dt>-FO</dt> <dd>Renames the resource file</dd> </dl> <p>Normally, <strong>rc</strong> names the compiled resource file after the resource script file and places it in the same directory as the script file. For example, when compiling myapp.rc, you would normally type: </p> <pre><strong>rc</strong> -R myapp.rc </pre> <p><strong>rc</strong> would then create a compiled resource file named myapp.res in the same directory as myapp.rc. </p> <p>This option gives the resulting resource file a name that differs from the corresponding resource script file. For example, to name the resulting resource file newfile.res, type: </p> <pre><strong>rc</strong> -R -FO newfile.res myapp.rc </pre> <p>Use this option to place the resource file in a different directory. For example, the following command places the compiled resource file myapp.res in the directory c:\resource: </p> <pre><strong>rc</strong> -R -FO c:\source\resource\myapp.res myapp.rc </pre> <h3>Choosing the directories that <strong>rc</strong> searches</h3> <p>Normally, <strong>rc</strong> searches for include files and resource files, such as icon and cursor files, first in the current directory and then in the directories specified by the INCLUDE environment variable. (The PATH environment variable has no effect on the directories <strong>rc</strong> searches.) </p> <h4>-I</h4> <p>Searches the specified directory before searching the directories specified by the INCLUDE environment variable. </p> <p>With this option, the compiler searches directories in the following order: </p> <ol> <li> The current directory <li> The directory or directories you specify by using the -I option, in the order in which they appear on the command line <li> The list of directories specified by the INCLUDE environment variable, in the order in which the variable lists them, unless you specify the -X option </ol> <p>The following example compiles the resource script file myapp.rc and adds the compiled resources to myapp.exe: </p> <pre><strong>rc</strong> -I c:\source\stuff -I d:\resources myapp.rc myapp.exe </pre> <p>When compiling the script file, <strong>rc</strong> searches for include files and resource files first in the current directory, then in c:\source\stuff and d:\resources, and lastly in the directories specified by the INCLUDE environment variable. </p> <h4>-X</h4> <p>Prevents <strong>rc</strong> from checking the INCLUDE environment variable when searching for include files or resource files. </p> <p>If you use this option, the compiler searches for files in the current directory and in any directories you specify using the -I option. The following example compiles the resource script file myapp.rc and adds the compiled resources to myapp. exe: </p> <pre><strong>rc</strong> -X -I c:\source\stuff myapp.rc myapp.exe </pre> <p>When compiling the script file, <strong>rc</strong> searches for include files and resource files first in the current directory and then in c:\source\stuff. </p> <h3>Memory utilization</h3> <p>These options let you specify how your application uses memory.</p> <p><strong>Note:</strong> The Memory options have no effect on applications written for Windows 3.1 or later. </p> <h4>-E</h4> <p>For a DLL, changes the default location of global memory from below the EMS bank line to above it. </p> <h4>-L</h4> <p>Tells Windows that the application uses expanded memory directly, according to the Lotus-Intel-Microsoft Expanded Memory Specification (EMS), version 2.2. </p> <p>This switch can also be specified as -LIM32. </p> <h4>-M</h4> <p>Assigns each instance of the application task to a distinct EMS bank, when Windows is running with the EMS 4.0 memory configuration. By default, all instances of a task share the same EMS bank. </p> <p>This option can also be specified as -MULTINST. </p> <h4>-P</h4> <p>Creates a private DLL that is called by only one application. This allows Windows to use memory more efficiently because only one application (or multiple instances of the same application) will be calling into the DLL. For example, in the large-frame EMS memory model, the DLL is loaded above the EMS bank line, freeing memory below the bank line. </p> <h4>-T</h4> <p>Creates an application that runs only with Windows in protected (standard or 386 enhanced) mode. If the user attempts to run the application in real mode, Windows displays a message box telling the user that the application cannot run in real mode. </p> <h3>Optimizing</h3> <p>This option lets you choose whether <strong>rc</strong> optimizes your resources for preloading. </p> <h4>-K</h4> <p>Disables <strong>rc</strong>'s load-optimization feature. If this option is not specified, the compiler arranges segments and resources in the executable file so that all preloaded information is contiguous. This feature allows Windows to load the application much more quickly. </p> <p>Without the -K option, all data segments, nondiscardable code segments, and the entry-point code segment will be preloaded, unless any segment and its relocation information exceed 64KB. If the PRELOAD attribute is not assigned to these segments in the module-definition (.def) file when you link your application, the compiler will add the preload attribute and display a warning. Resources and segments will have the same segment alignment. This alignment should be as small as possible to prevent the final executable file from growing unnecessarily large. You can set the alignment using the linker's /alignment option. </p> <h3>Compiling resources separately</h3> <p>This option sets where to place the resources: in a resource file or an executable file. </p> <h4>-R</h4> <p>Creates a resource file from a resource script file. </p> <p>By default, <strong>rc</strong> adds the compiled resources to the specified executable file. Sometimes you might want to compile the resources first and then add them to the executable file in separate steps. This can be useful if the contents of a resource file will be stable after initial development. You can save time by compiling resources separately, then adding the compiled resource file to your executable file each time you recompile the executable. </p> <p>Use the -R option to compile the resources separately, without adding them to the executable file. When you use this option, <strong>rc</strong> compiles the resource script file and creates a compiled resource file. For example, this command reads the resource script file sample.rc and creates the compiled resource file sample.res: </p> <pre><strong>rc</strong> -R sample.rc </pre> <p>The command does not add sample.res to the executable file.</p> <h3>Displaying progress messages</h3> <h4>-V</h4> <p>Normally, <strong>rc</strong> does not display messages that report on its progress as it compiles. You can, however, tell the compiler to display these messages with this option. The following example causes the compiler to report on its progress as it compiles the script file sample.rc, creates the compiled resource file sample.res, and adds the resource file to the executable file sample. exe: </p> <pre><strong>rc</strong> -V sample.rc </pre> <h3>On-line help</h3> <p>This option displays on-line help for <strong>rc</strong>. </p> <h4>-H, -?</h4> <p>Displays a list of the <strong>rc</strong> command line options. </p> <h3>Different Ways to Use the <strong>rc</strong> Command</h3> <p>This section describes the various ways to use the <strong>rc</strong> command. </p> <h3>Compiling a resource script file</h3> <p>To compile resources separately, use the <strong>rc</strong> command in the following form: </p> <pre><strong>rc</strong> -R options script-file </pre> <p>With this form, <strong>rc</strong> ignores the executable file if you specify one. </p> <h3>Compiling and adding to an executable</h3> <p>To compile a resource script file and add the resulting resource file to the executable file, use the <strong>rc</strong> command in the following form: </p> <pre><strong>rc</strong> options script-file executable-file </pre> <h3>Creating a DLL without resources</h3> <p>To compile a DLL that does not have a resource file, use the <strong>rc</strong> command in the following form: </p> <pre><strong>rc</strong> options dll-file </pre> <p>With this form, the DLL filename must explicitly have an .exe, .drv, or .dll extension. </p> <h3>Adding resources to an executable</h3> <p>To add a compiled resource (.res) file to an executable file, use the <strong>rc</strong> command in the following form: </p> <pre><strong>rc</strong> options res-file.res executable-file </pre> </div> <div id="footernav"> <a href="https://www.digitalmars.com/" title="digitalmars.com">Home</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../rtl/rtl.html" title="Runtime Library Reference">Runtime Library</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../ugr/ugr.html" title="IDDE Reference">IDDE Reference</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../stl/index.html" title="Standard Template Library">STL</a> | <a href="https://www.digitalmars.com/advancedsearch.html" title="Search Digital Mars web site">Search</a> | <a href="https://www.digitalmars.com//download/freecompiler.html" title="download C++">Download</a> | <a href="https://www.digitalmars.com/NewsGroup.html" title="Forums">Forums</a> </div> <div id="copyright"> Copyright © 1999-2018 by Digital Mars ®, All Rights Reserved | Page generated by <a href="https://dlang.org/spec/ddoc.html">Ddoc</a>. </div> </div><div class="naked_ctrl"> <form action="/index.cgi/contrast" method="get" name="gate"> <p><a href="http://altstyle.alfasado.net">AltStyle</a> によって変換されたページ <a href="https://digitalmars.com/ctg/ctgRC.html">(->オリジナル)</a> / <label>アドレス: <input type="text" name="naked_post_url" value="https://digitalmars.com/ctg/ctgRC.html" size="22" /></label> <label>モード: <select name="naked_post_mode"> <option value="default">デフォルト</option> <option value="speech">音声ブラウザ</option> <option value="ruby">ルビ付き</option> <option value="contrast" selected="selected">配色反転</option> <option value="larger-text">文字拡大</option> <option value="mobile">モバイル</option> </select> <input type="submit" value="表示" /> </p> </form> </div> </body> </html>