X-Git-Url: https://git.ti.com/gitweb?p=processor-sdk%2Fpdk.git;a=blobdiff_plain;f=packages%2Fmakefile;h=4bf86d979e319d138d4efa0021bb73098163a6f4;hp=6b5c9e4ccd1b70bdfd645c4265e5a0feaa31dd30;hb=7ba4377f2c5badcab53dfcf442aed4ac9b0f24d5;hpb=27475274ac07ce36f2e14beebdbeb346632c8bde diff --git a/packages/makefile b/packages/makefile index 6b5c9e4cc..4bf86d979 100755 --- a/packages/makefile +++ b/packages/makefile @@ -1,10 +1,10 @@ #******************************************************************************* -#* FILE PURPOSE: Top level makefile for Creating Component Libraries and example +#* FILE PURPOSE: Top level makefile for Creating Component Libraries and example #* binaries of PDK #******************************************************************************* #* FILE NAME: makefile #* -#* DESCRIPTION: Builds the PDK Drivers & Examples +#* DESCRIPTION: Builds the PDK Drivers & Examples #* #* #******************************************************************************* @@ -13,7 +13,11 @@ .NOTPARALLEL: # This make file is not parallel in its highest level. This is done to serialize the multiple SOCS,BOARDS,CORES. # However the subsequent makefiles invoked by this makefile have parallelism supported. i.e -j option given to this -# makefile will be passed on to the subsequent makefiles resulting in parallel builds. +# makefile will be passed on to the subsequent makefiles resulting in parallel builds. + +#Default when PDK env script is not run +PDK_INSTALL_PATH ?= $(abspath .) +SDK_INSTALL_PATH ?= $(abspath ../../) ifeq ($(RULES_MAKE), ) include $(PDK_INSTALL_PATH)/ti/build/Rules.make @@ -56,7 +60,7 @@ CORE_LIST = $(filter-out $(PRUCORE_LIST),$(LIMIT_CORES)) else CORE_LIST = $(CORE) endif - + .PHONY: all all_libs all_examples clean env_check help xdc_meta \ buildinfra_all buildinfra_clean buildinfra_pdk_examples \ non-buildinfra_all non-buildinfra_clean buildinfra_pdk_libs non-buildinfra_pdk_examples \ @@ -65,7 +69,7 @@ endif # Default BUILD profile is release BUILD_PROFILE ?= release #The top level makefile two kinds of sub modules. Ones which are supported by the 'build infrastructure' and which are not. -# i.e The modules which supports 'build infrastructure' are included in ti/build/component.mk and follow a standard set of conventions and targets. +# i.e The modules which supports 'build infrastructure' are included in ti/build/component.mk and follow a standard set of conventions and targets. # They can be built using ti/build/makefile. Many newer targets such as AM3/4/5/6/7 have their modules in this category. # Those targets in this makefile has the 'buildinfra_' prefix in them. @@ -99,8 +103,9 @@ non-buildinfra_all non-buildinfra_pdk_libs non-buildinfra_pdk_examples: ### Non library/example targets env_check: -ifeq ($(PDK_SOC),) - $(ECHO) "Warning !! PDK_SOC is not set!!! Please run 'help' and refer to 'Optional Arguments' in the help section" +ifneq ($(PDK_SOC),$(filter $(PDK_SOC), $(PROCSDK_SUPPORTED_PDK_SOCS))) + $(ECHO) "Warning !! PDK_SOC is not set properly!!!" + $(ECHO) "PDK_SOC should be set to any of the values: $(PROCSDK_SUPPORTED_PDK_SOCS)" endif help: env_check @@ -142,14 +147,15 @@ help: env_check $(ECHO) "PDK_SOC= This will specify the SOC version if the pdk directory does not specify it (if git clone pdk.git is used)" $(ECHO) "If pdk is git cloned, PDK_SOC should be set to the where the original PDK directory from the installer was pdk__)" $(ECHO) "For example if the original PDK installed directory (which got replaced by pdk.git) was /pdk_am65xx_1_0_5, PDK_SOC=am65xx" + $(ECHO) " PDK_SOC should be set to any of the values: $(PROCSDK_SUPPORTED_PDK_SOCS)" $(ECHO) "" $(ECHO) "BUILD_PROFILE= This will determine the type of libraries/examples generated (release/debug friendly). Default is 'release " $(ECHO) "Valid values of LIMIT_CORES are $(LIMIT_CORES)" $(ECHO) "" $(ECHO) "SOC= CORE= BOARD= This will build libraries/examples for the specified combination of " $(ECHO) "Valid values of SOC/BOARD/CORE are found from LIMIT_SOC/BOARD/CORES above" - - + + # if PDK.git is initiated from a fresh clone, the XDC meta headers will not have been generated. (xdc meta headers are used for CCS based projects)