Tool/software: Code Composer Studio
Hello,
We are creating an 'emptyAssemblyOnly' project via commandline which is having 6 build configurations. During nightly build test automation, we need to build each of the build configuration one by one using a shell script where we faced a problem.
We observe that the build configuration gets switched a wrong one than what specified using -ccs.configuration argument. I have put echo messages in the script just to make sure that the $BUILD_CONFIG_NAME variable value is passed correctly from the parent script.
Below are the script commands and the sample output for reference:
echo "Building project ${PROJECT_NAME} for $BUILD_CONFIG_NAME build configuration..."
$CCS_INSTALL_DIR/eclipse/eclipse -noSplash -data "$CCS_WORKSPACE_LOC" -application com.ti.ccstudio.apps.projectBuild -ccs.projects $PROJECT_NAME -ccs.configuration $BUILD_CONFIG_NAME -ccs.buildType full
Building project profinet_switch for PRU1_IRT build configuration...[echo message added in shell script]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Tue Feb 21 16:50:17 IST 2017]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
================================================================================
Pre processing...
================================================================================
Building...
**** Build of configuration PRU0_IRT for project profinet_switch **** [Message during build]
We observe that this behavior is completely random and happens to different build configurations at different times. Is there any clue on why the build happens with wrong build configuration than what specified. What are the points to be checked further to track this issue?
Regards,
Nijin P
