Partager via

BuildMethod Block (Windows CE 5.0)

  • Article

Send Feedback

The BuildMethod block provides information about which CPUs support your Catalog item and, if applicable, links to source files, Help documentation (.chm) files, and user-created projects.

Note   Build-specific information in custom CEC files is not supported in Windows CE 5.0. Although this does not prevent CEC files from earlier versions of Platform Builder from being used, the information that is no longer supported, such as custom build steps, is ignored. For information about including custom build actions at a project level in your OS design, see Specifying Project Settings.

For more information about changes to BuildMethod blocks in Windows CE 5.0, see Catalog Item Migration.

The following code example shows a BuildMethod block.

BuildMethods(
   BuildMethod(
      CPU ( "x86" )
      Step ( BSP )
      Action ( '#CLONE_MODULE(common,ddi_flat)' )
   )
)

The following table shows the elements of a BuildMethod block.

Element Description
CPU Specifies which microprocessors this build method supports.

The following microprocessors are supported by default:

  • ARMV4I
  • Emulator
  • MIPSII, MIPSII_FP, MIPSIV, MIPSIV_FP
  • SH4
  • x86

The microprocessor list must be enclosed in quotation marks.

The string "default" refers to the default microprocessor list.
CoreOS (Optional) Specifies whether the Catalog item is a Core OS Catalog item, or a Third Party Catalog item.

Uses the format shown in the following code example.

CoreOS( CEBASE )
Step Build step. Only one step per build method is allowed.
Note   This information is required in a .cec file, but is otherwise ignored in Windows CE 5.0.
GUID (Optional) Supplies the GUID for the build method.

If the GUID is not present, it is created when the implementation is imported.
Setting (Optional) Supplies a path for the Help documentation, using the following format. 
Setting ( '#CHM( "CHM_FILE" )' )

This attaches an HTML Help file (.chm) to the Catalog item described in the .cec file. Exported SDKs that include the item will also contain the associated HTML help files.

This setting is used to determine whether a help file is exported to the SDK for the OS design.
Action Specifies metadata associated with the selected Catalog item or module, using a string that uses one of the following formats: 
Action( '#SRCCODE( DIR|SOURCES, "SOURCES_FULLPATH" )' )
Action( '#SRCCODE( USER_PROJECT, "SOURCES_FULLPATH" )' )
Action( '#CLONE_MODULE(DEPENDENCY_TREE,MODULE_NAME)' )

Valid metadata descriptors that you can choose include the following:

  • #SRCCODE

    Specifies the directory containing the sources, dirs, and makefile files associated with this Catalog item.

    You can also use this action to specify the Platform Builder project (.pbpxml) file associated with this Catalog item. However, using this descriptor will not build code. For information about including custom build actions at a project level in your OS design, see Specifying Project Settings.

  • #CLONE_MODULE

    Specifies the dependency tree containing the target module that you want to clone by replacing one or more of the libraries in the selected module during the build process.

See Also

Catalog Item Files | Build Phases

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.