2 # Copyright (c) 2006-2007, Intel Corporation
\r
4 # All rights reserved. This program and the accompanying materials
\r
5 # are licensed and made available under the terms and conditions of the BSD License
\r
6 # which accompanies this distribution. The full text of the license may be found at
\r
7 # http://opensource.org/licenses/bsd-license.php
\r
9 # THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
\r
10 # WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
\r
12 # Filename: target.template
\r
14 # ALL Paths are Relative to WORKSPACE
\r
16 # Separate multiple LIST entries with a SINGLE SPACE character, do not use comma characters.
\r
17 # Un-set an option by either commenting out the line, or not setting a value.
\r
20 # PROPERTY Type Use Description
\r
21 # ---------------- -------- -------- -----------------------------------------------------------
\r
22 # ACTIVE_PLATFORM Filename Recommended Specify the WORKSPACE relative Path and Filename
\r
23 # of the platform description file that will be used for the
\r
24 # build. This line is required if and only if the current
\r
25 # working directory does not contain one or more description
\r
27 ACTIVE_PLATFORM = Nt32Pkg/Nt32Pkg.dsc
\r
29 # TARGET List Optional Zero or more of the following: DEBUG, RELEASE,
\r
30 # UserDefined; separated by a space character.
\r
31 # If the line is missing or no value is specified, all
\r
32 # valid targets specified in the platform description file
\r
33 # will attempt to be built. The following line will build all
\r
37 # TARGET_ARCH List Optional What kind of architecture is the binary being target for.
\r
38 # One, or more, of the following, IA32, IPF, X64, EBC or ARM.
\r
39 # Multiple values can be specified on a single line, using
\r
40 # space charaters to separate the values. These are used
\r
41 # during the parsing of an platform description file,
\r
42 # restricting the build output target(s.)
\r
43 # The Build Target ARCH is determined by a logical AND of:
\r
44 # platform BuildOptions: <SupportedArchitectures> tag
\r
45 # If not specified, then all valid architectures specified
\r
46 # in the platform file, for which tools are available, will be
\r
50 # TOOL_DEFINITION_FILE Filename Optional Specify the name of the filename to use for specifying
\r
51 # the tools to use for the build. If not specified,
\r
52 # tools_def.txt will be used for the build. This file
\r
53 # MUST be located in the WORKSPACE/Conf directory.
\r
54 TOOL_CHAIN_CONF = Conf/tools_def.txt
\r
56 # TAGNAME List Optional Specify the name(s) of the tools_def.txt TagName to use.
\r
57 # If not specified, all applicable TagName tools will be
\r
58 # used for the build. The list uses space character separation.
\r
59 TOOL_CHAIN_TAG = MYTOOLS
\r
61 # MULTIPLE_THREAD FLAG Optional Flag to enable multi-thread build. If not specified, default
\r
62 # is "Disable". If your computer is multi-core or multiple CPUs,
\r
63 # enabling this feature will bring much benefit.
\r
64 # This feature is only available for "spawn" build mode, and
\r
65 # only for PLATFORM build. The clean, cleanall or
\r
66 # stand-alone module build is still using the normal way.
\r
67 MULTIPLE_THREAD = Enable
\r
69 # MAX_CONCURRENT_THREAD_NUMBER NUMBER Optional The number of concurrent threads. Default is 1. Recommend to
\r
70 # set this value to one more than the number of your compurter
\r
72 MAX_CONCURRENT_THREAD_NUMBER = 1
\r
74 # Build rules definition
\r
77 BUILD_RULE_CONF = Conf/build_rule.txt
\r