◄Up► ◄Contents► ◄Index► ◄Back► ─────Programmer's WorkBench───────────────────────────────────────────────── A project template is a named set of Build switches that describes how PWB is to compile a file and how PWB is to create and update a project makefile. These switches also hold the data involved in maintaining a project. You can choose a project template supplied by the Microsoft language and utilities extensions, or you can create a custom project template. Before you can compile a file or create a project, you must specify a project template. PWB uses the information in the template to perform the required actions. See: ◄Options menu, Project Templates Cascaded Menu► About Project Templates PWB is a general platform for building all sorts of targets using many languages and tools. It has no built-in knowledge of specific target environments (such as MS-DOS or Windows), source languages, compilers, or other tools involved in the build process. This information is provided by the language and utilities extensions. Each predefined template defines the commands and appropriate default compiler and linker options that are required to build the type of project that is described by the template's name. For example, information about building a Windows application, including information about the resource compiler (RC), is included only in the Windows project templates. If you do not choose a Windows template but add resource compiler source files (.RC files) to the project file list, PWB displays the message: File type not used with current project template Project templates are grouped by the run-time support that is included in the template. The templates listed under 'None' do not include run-time support. You must explicitly specify the correct libraries and object files. This grouping is a convention that is not enforced by PWB. Custom templates saved under None can provide run-time support if appropriate. See ◄Introduction to Custom Project Templates► ◄Creating a New Project Template► -♦-