-# Relative to WORKSPACE
-TOOLS_DEFINITION_FILE = Tools/Conf/tools_def.txt
-
-# Relative to WORKSPACE
-# ACTIVE_PLATFORM = MdePkg/MdePkg.fpd
-
-# Separate multiple targets with space, not not use comma
-TARGET =
-TARGET_ARCH =
-TAGNAME =
-
+#\r
+# Copyright (c) 2006, Intel Corporation\r
+#\r
+# All rights reserved. This program and the accompanying materials\r
+# are licensed and made available under the terms and conditions of the BSD License\r
+# which accompanies this distribution. The full text of the license may be found at\r
+# http://opensource.org/licenses/bsd-license.php\r
+\r
+# THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
+# WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r
+#\r
+# Filename: target.template\r
+#\r
+# ALL Paths are Relative to WORKSPACE\r
+\r
+# Separate multiple LIST entries with a SINGLE SPACE character, do not use comma characters.\r
+# Un-set an option by either commenting out the line, or not setting a value.\r
+\r
+#\r
+# PROPERTY Type Use Description\r
+# ---------------- -------- -------- -----------------------------------------------------------\r
+# ACTIVE_PLATFORM Filename Recommended Specify the WORKSPACE relative Path and Filename \r
+# of the platform FPD file that will be used for the build\r
+# This line is required if and only if the current working\r
+# directory does not contain one or more FPD files.\r
+ACTIVE_PLATFORM = EdkNt32Pkg/Nt32.fpd\r
+\r
+# TARGET List Optional Zero or more of the following: DEBUG, RELEASE, \r
+# UserDefined; separated by a space character. \r
+# If the line is missing or no value is specified, all \r
+# valid targets specified in the FPD file will attempt \r
+# to be built. The following line will build all platform\r
+# targets.\r
+TARGET = DEBUG\r
+\r
+# TARGET_ARCH List Optional What kind of architecture is the binary being target for. \r
+# One, or more, of the following, IA32, IPF, X64, EBC or ARM.\r
+# Multiple values can be specified on a single line, using \r
+# space charaters to separate the values. These are used \r
+# during the parsing of an FPD file, restricting the build\r
+# output target(s.)\r
+# The Build Target ARCH is determined by a logical AND of:\r
+# FPD BuildOptions: <SupportedArchitectures> tag\r
+# If not specified, then all valid architectures specified \r
+# in the FPD file, for which tools are available, will be \r
+# built.\r
+# TARGET_ARCH = \r
+\r
+# TOOL_DEFINITION_FILE Filename Optional Specify the name of the filename to use for specifying \r
+# the tools to use for the build. If not specified, \r
+# tools_def.txt will be used for the build. This file \r
+# MUST be located in the WORKSPACE/Tools/Conf directory.\r
+TOOL_CHAIN_CONF = Tools/Conf/tools_def.txt\r
+\r
+# TAGNAME List Optional Specify the name(s) of the tools_def.txt TagName to use. \r
+# If not specified, all applicable TagName tools will be \r
+# used for the build. The list uses space character separation.\r
+TOOL_CHAIN_TAG = MYTOOLS\r
+\r
+# MULTIPLE_THREAD FLAG Optional Flag to enable multi-thread build. If not specified, default\r
+# is "Disable". If your computer is multi-core or multiple CPUs, \r
+# enabling this feature will bring much benefit. For multi-thread \r
+# built, the log will write to ${BUILD_DIR}/build.log. \r
+# This feature is only for PLATFORM build, and clean, cleanall or\r
+# stand-alone module build is still using the normal way. \r
+MULTIPLE_THREAD = Enable\r
+\r
+# MAX_CONCURRENT_THREAD_NUMBER NUMBER Optional The number of concurrent threads. Default is 2. Recommend to \r
+# set this value to one more than the number of your compurter\r
+# cores or CPUs. \r
+MAX_CONCURRENT_THREAD_NUMBER = 2
\ No newline at end of file