[tisdk-build-scripts][PATCH 1/4] config-build-env: Add support for adding a source mirror

[tisdk-build-scripts][PATCH 1/4] config-build-env: Add support for adding a source mirror

[Jacob Stiffler]

* Source mirrors may be used by setting the SOURCE_MIRROR_URL parameter in the
  configuration file.

Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
---
 lib/oesdk/config-build-env |    5 +++++
 1 file changed, 5 insertions(+)

diff --git a/lib/oesdk/config-build-env b/lib/oesdk/config-build-env
index 655a7eb..cace93f 100644
--- a/lib/oesdk/config-build-env
+++ b/lib/oesdk/config-build-env
@@ -74,5 +74,10 @@ config_build_dir() {
     sed -i "s+^SSTATE_DIR =.*+STATE_DIR = \"$BUILD_ROOT/sstate-cache\"+" local.conf
     sed -i "s+^TMPDIR =.*+TMPDIR = \"$BUILD_ROOT/$build_dir/arago-tmp\"+" local.conf
     sed -i "s+^export BUILDDIR=.*+export BUILDDIR=\"$BUILD_ROOT/$build_dir\"+" setenv
+
+    if [ ! -z "$SOURCE_MIRROR_URL" ]; then
+      echo "SOURCE_MIRROR_URL = \"$SOURCE_MIRROR_URL\"" >> local.conf
+      echo "INHERIT += \"own-mirrors\"" >> local.conf
+    fi
     cd - > /dev/null 2>&1
 }
-- 
1.7.9.5

[tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

[Jacob Stiffler]

* The configuration parameter INSTALLER_PREFIX is used to set the prefix of the i
  installer filename and the default installation directory.
* This parameter must be set when PRODUCTIZE_SDK="true"

Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
---
 lib/oesdk/package-sdks |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/oesdk/package-sdks b/lib/oesdk/package-sdks
index d6b01f7..9bfd887 100644
--- a/lib/oesdk/package-sdks
+++ b/lib/oesdk/package-sdks
@@ -109,7 +109,7 @@ create_sd_card_content() {
     cd $start_here_root
 
     # Copy the installer
-    cp $DEPLOY_ROOT/$m/$BUILD_ID/ti-sdk-$m* $start_here_root/
+    cp $DEPLOY_ROOT/$m/$BUILD_ID/${INSTALLER_PREFIX}-$m* $start_here_root/
 
     if [ "$?" != "0" ]
     then
@@ -184,7 +184,7 @@ create_sdk_installer() {
 
     $INSTALL_BUILDER/builder build $INSTALL_BUILDER_PROJECT linux --setvars \
         sdk_loc="$installer_root/" \
-        sdk_name_prefix="ti-sdk"                  \
+        sdk_name_prefix="${INSTALLER_PREFIX}"                  \
         sdk_tar_name=$sdk_tar                     \
         output_dir="$deploy_root"                 \
         platform="$m"                             \
@@ -277,7 +277,7 @@ package_web_content() {
     fi
 
     # Move the installer into the exports directory
-    mv $deploy_root/ti-sdk-$m* $exports_root/
+    mv $deploy_root/${INSTALLER_PREFIX}-$m* $exports_root/
 
     # Create the md5sum file
     cd $exports_root
-- 
1.7.9.5

[tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Jacob Stiffler]

* Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable logging stdout
  and stderr for the bitbake command to the build log.

Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
---
 lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/lib/oesdk/bitbake-test-sdk-image b/lib/oesdk/bitbake-test-sdk-image
index cff86e4..7d8d093 100644
--- a/lib/oesdk/bitbake-test-sdk-image
+++ b/lib/oesdk/bitbake-test-sdk-image
@@ -375,12 +375,16 @@ bitbake_sdk_images(){
         for c in "${bitbake_command_list[@]}"
         do
             log $machine_build_log echo "executing bitbake command $c for machine $m"
-            MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
+            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
+                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a $machine_build_log
+            else
+                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
+            fi
 
             # Check the return status of the build process.  If the build returned
             # a non-zero exit value then log the failure and continue (without
             # testing).  A lack of a test file will indicate a test skip
-            if [ "$?" != "0" ]
+            if [ "${PIPESTATUS[0]}" != "0" ]
             then
                 echo "FAILED" > $LOG_DIR/$m-build-result.txt
                 build_status="fail"
-- 
1.7.9.5

[tisdk-build-scripts][PATCH 4/4] configs: Add new configuration parameters

[Jacob Stiffler]

* SOURCE_MIRROR_URL
* INSTALLER_PREFIX
* BUILD_LOG_VERBOSE

Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
---
 configs/amsdk/amsdk-config-05.06.00.00.txt      |   20 +++++++++++++++++++-
 configs/amsdk/amsdk-config-05.07.00.00.txt      |   20 +++++++++++++++++++-
 configs/amsdk/amsdk-config-06.00.00.00.txt      |   20 +++++++++++++++++++-
 configs/amsdk/amsdk-config-07.00.00.00.txt      |   20 +++++++++++++++++++-
 configs/amsdk/amsdk-config-07.01.00.00.txt      |   20 +++++++++++++++++++-
 configs/amsdk/amsdk-config-08.00.00.00.txt      |   20 +++++++++++++++++++-
 configs/arago-core-tisdk-daisy-puget.txt        |   18 ++++++++++++++++++
 configs/arago-core-tisdk-danny-puget.txt        |   18 ++++++++++++++++++
 configs/arago-core-tisdk-dora-puget.txt         |   18 ++++++++++++++++++
 configs/arago-core-tisdk-dylan-puget.txt        |   18 ++++++++++++++++++
 configs/coresdk/arago-core-amsdk-2013.04.01.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.04.00.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.04.01.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.04.02.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.10.00.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.12.00.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2013.12.01.txt |   20 +++++++++++++++++++-
 configs/coresdk/arago-core-tisdk-2014.08.00.txt |   20 +++++++++++++++++++-
 configs/distroless-meta-ti-puget.txt            |   18 ++++++++++++++++++
 19 files changed, 356 insertions(+), 14 deletions(-)

diff --git a/configs/amsdk/amsdk-config-05.06.00.00.txt b/configs/amsdk/amsdk-config-05.06.00.00.txt
index 5c459e8..ca4ac43 100644
--- a/configs/amsdk/amsdk-config-05.06.00.00.txt
+++ b/configs/amsdk/amsdk-config-05.06.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-05.06.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -207,6 +215,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/amsdk/amsdk-config-05.07.00.00.txt b/configs/amsdk/amsdk-config-05.07.00.00.txt
index 0f39da1..5424320 100644
--- a/configs/amsdk/amsdk-config-05.07.00.00.txt
+++ b/configs/amsdk/amsdk-config-05.07.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-05.07.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -222,6 +230,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/amsdk/amsdk-config-06.00.00.00.txt b/configs/amsdk/amsdk-config-06.00.00.00.txt
index 8684a6a..228761c 100644
--- a/configs/amsdk/amsdk-config-06.00.00.00.txt
+++ b/configs/amsdk/amsdk-config-06.00.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-06.00.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/amsdk/amsdk-config-07.00.00.00.txt b/configs/amsdk/amsdk-config-07.00.00.00.txt
index 8f65d39..d967cbb 100644
--- a/configs/amsdk/amsdk-config-07.00.00.00.txt
+++ b/configs/amsdk/amsdk-config-07.00.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-07.00.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/amsdk/amsdk-config-07.01.00.00.txt b/configs/amsdk/amsdk-config-07.01.00.00.txt
index 9dbcc73..3e4774e 100644
--- a/configs/amsdk/amsdk-config-07.01.00.00.txt
+++ b/configs/amsdk/amsdk-config-07.01.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-07.01.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/amsdk/amsdk-config-08.00.00.00.txt b/configs/amsdk/amsdk-config-08.00.00.00.txt
index ff724e9..b4d98bb 100644
--- a/configs/amsdk/amsdk-config-08.00.00.00.txt
+++ b/configs/amsdk/amsdk-config-08.00.00.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/amsdk/amsdk-08.00.00.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/arago-core-tisdk-daisy-puget.txt b/configs/arago-core-tisdk-daisy-puget.txt
index c132baf..4e2422a 100644
--- a/configs/arago-core-tisdk-daisy-puget.txt
+++ b/configs/arago-core-tisdk-daisy-puget.txt
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/arago-daisy-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/OE/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -229,6 +237,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/arago-core-tisdk-danny-puget.txt b/configs/arago-core-tisdk-danny-puget.txt
index be54fb0..1aa3e46 100644
--- a/configs/arago-core-tisdk-danny-puget.txt
+++ b/configs/arago-core-tisdk-danny-puget.txt
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/arago-danny-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/OE/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -229,6 +237,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/arago-core-tisdk-dora-puget.txt b/configs/arago-core-tisdk-dora-puget.txt
index 6ac968c..623817b 100644
--- a/configs/arago-core-tisdk-dora-puget.txt
+++ b/configs/arago-core-tisdk-dora-puget.txt
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/arago-dora-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/OE/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -229,6 +237,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/arago-core-tisdk-dylan-puget.txt b/configs/arago-core-tisdk-dylan-puget.txt
index e71fe7d..595212f 100644
--- a/configs/arago-core-tisdk-dylan-puget.txt
+++ b/configs/arago-core-tisdk-dylan-puget.txt
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/arago-dylan-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/OE/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -229,6 +237,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-amsdk-2013.04.01.txt b/configs/coresdk/arago-core-amsdk-2013.04.01.txt
index 2cc7686..cb85f35 100644
--- a/configs/coresdk/arago-core-amsdk-2013.04.01.txt
+++ b/configs/coresdk/arago-core-amsdk-2013.04.01.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.04.01-amsdk-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -230,6 +238,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.04.00.txt b/configs/coresdk/arago-core-tisdk-2013.04.00.txt
index ccd9e19..c6466a4 100644
--- a/configs/coresdk/arago-core-tisdk-2013.04.00.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.04.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.04.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -230,6 +238,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.04.01.txt b/configs/coresdk/arago-core-tisdk-2013.04.01.txt
index 303597d..7b7fac5 100644
--- a/configs/coresdk/arago-core-tisdk-2013.04.01.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.04.01.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.04.01-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -230,6 +238,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.04.02.txt b/configs/coresdk/arago-core-tisdk-2013.04.02.txt
index 0bfb29d..a8f0a11 100644
--- a/configs/coresdk/arago-core-tisdk-2013.04.02.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.04.02.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.04.02-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -230,6 +238,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.10.00.txt b/configs/coresdk/arago-core-tisdk-2013.10.00.txt
index 0af3398..c05ffa7 100644
--- a/configs/coresdk/arago-core-tisdk-2013.10.00.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.10.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/arago-dylan-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.12.00.txt b/configs/coresdk/arago-core-tisdk-2013.12.00.txt
index 51b7be6..2f855c6 100644
--- a/configs/coresdk/arago-core-tisdk-2013.12.00.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.12.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.12.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2013.12.01.txt b/configs/coresdk/arago-core-tisdk-2013.12.01.txt
index a7ff529..0fc905f 100644
--- a/configs/coresdk/arago-core-tisdk-2013.12.01.txt
+++ b/configs/coresdk/arago-core-tisdk-2013.12.01.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2013.12.01-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/coresdk/arago-core-tisdk-2014.08.00.txt b/configs/coresdk/arago-core-tisdk-2014.08.00.txt
index 1a5e20c..b616732 100644
--- a/configs/coresdk/arago-core-tisdk-2014.08.00.txt
+++ b/configs/coresdk/arago-core-tisdk-2014.08.00.txt
@@ -6,7 +6,7 @@
 # that MUST be set to a value.  Failure to set these variables could
 # lead to corruption of the host system or the build script not
 # executing properly
-MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
+MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION INSTALLER_PREFIX"
 
 # This variable holds the SDK version you are building.  This will be picked
 # up in the installer name if you choose to package an installer.  You can
@@ -126,11 +126,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/coresdk/coresdk-2014.08.00-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/home/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -228,6 +236,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
diff --git a/configs/distroless-meta-ti-puget.txt b/configs/distroless-meta-ti-puget.txt
index 917b125..bc9f783 100644
--- a/configs/distroless-meta-ti-puget.txt
+++ b/configs/distroless-meta-ti-puget.txt
@@ -112,11 +112,19 @@ CONFIG_FILE="${BUILD_ROOT}/configs/distroless-meta-ti-config.txt"
 #   4. Packaging logs for individual machines
 LOG_DIR="${BUILD_ROOT}/log-files"
 
+# Setting this variable to "true" will enable logging stdout and stderr of the 
+# bitbake command to the appropriate machine's build_log.txt.
+#BUILD_LOG_VERBOSE="true"
+
 # This is the directory where you want to configure your build to download
 # files to.  This is best done as a shared directory among the builds to
 # save download time and space.
 DL_DIR="/OE/downloads"
 
+# Setting this variable will configure the builds to attempt to use a mirror to 
+# obtain the build sources.
+#SOURCE_MIRROR_URL="http://some.web.server/arago-sources/"
+
 # This variable points to an optional location where additional installer
 # content can be placed to be packaged inside of any image recipe that
 # inherits the tisdk-image class.  It is expected that the directory
@@ -215,6 +223,16 @@ INSTALLER_ROOT="$BUILD_ROOT/installer"
 # installer
 INSTALL_BUILDER_PROJECT="$SCRIPTS_ROOT/installer-files/tisdk.xml"
 
+# This variable will provide the prefix for the installer filename and default 
+# installation directory.
+# NOTE: This prefix should match the installer filename given in the webgen.mak
+#  
+# Installer name will have the form: 
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}-Linux-x86-Install.bin
+# Installation directory will have the form:
+#   - ${INSTALLER_PREFIX}-${MACHINE}-${TISDK_VERSION}
+INSTALLER_PREFIX="ti-sdk"
+
 # This variable points to a directory where additional SD card content
 # is located.  In general this directory should have a structure like
 #   - <machine>/boot - holds extra boot partition content
-- 
1.7.9.5

Re: [tisdk-build-scripts][PATCH 1/4] config-build-env: Add support for adding a source mirror

[Denys Dmytriyenko]

Looks good, thanks! Ack.

On Thu, Sep 04, 2014 at 01:31:05PM -0400, Jacob Stiffler wrote:
> * Source mirrors may be used by setting the SOURCE_MIRROR_URL parameter in the
>   configuration file.
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/config-build-env |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/lib/oesdk/config-build-env b/lib/oesdk/config-build-env
> index 655a7eb..cace93f 100644
> --- a/lib/oesdk/config-build-env
> +++ b/lib/oesdk/config-build-env
> @@ -74,5 +74,10 @@ config_build_dir() {
>      sed -i "s+^SSTATE_DIR =.*+STATE_DIR = \"$BUILD_ROOT/sstate-cache\"+" local.conf
>      sed -i "s+^TMPDIR =.*+TMPDIR = \"$BUILD_ROOT/$build_dir/arago-tmp\"+" local.conf
>      sed -i "s+^export BUILDDIR=.*+export BUILDDIR=\"$BUILD_ROOT/$build_dir\"+" setenv
> +
> +    if [ ! -z "$SOURCE_MIRROR_URL" ]; then
> +      echo "SOURCE_MIRROR_URL = \"$SOURCE_MIRROR_URL\"" >> local.conf
> +      echo "INHERIT += \"own-mirrors\"" >> local.conf
> +    fi
>      cd - > /dev/null 2>&1
>  }
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

[Denys Dmytriyenko]

Just a quick question - what do you plan to use instead of "ti-sdk" prefix?


On Thu, Sep 04, 2014 at 01:31:06PM -0400, Jacob Stiffler wrote:
> * The configuration parameter INSTALLER_PREFIX is used to set the prefix of the i
>   installer filename and the default installation directory.
> * This parameter must be set when PRODUCTIZE_SDK="true"
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/package-sdks |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/oesdk/package-sdks b/lib/oesdk/package-sdks
> index d6b01f7..9bfd887 100644
> --- a/lib/oesdk/package-sdks
> +++ b/lib/oesdk/package-sdks
> @@ -109,7 +109,7 @@ create_sd_card_content() {
>      cd $start_here_root
>  
>      # Copy the installer
> -    cp $DEPLOY_ROOT/$m/$BUILD_ID/ti-sdk-$m* $start_here_root/
> +    cp $DEPLOY_ROOT/$m/$BUILD_ID/${INSTALLER_PREFIX}-$m* $start_here_root/
>  
>      if [ "$?" != "0" ]
>      then
> @@ -184,7 +184,7 @@ create_sdk_installer() {
>  
>      $INSTALL_BUILDER/builder build $INSTALL_BUILDER_PROJECT linux --setvars \
>          sdk_loc="$installer_root/" \
> -        sdk_name_prefix="ti-sdk"                  \
> +        sdk_name_prefix="${INSTALLER_PREFIX}"                  \
>          sdk_tar_name=$sdk_tar                     \
>          output_dir="$deploy_root"                 \
>          platform="$m"                             \
> @@ -277,7 +277,7 @@ package_web_content() {
>      fi
>  
>      # Move the installer into the exports directory
> -    mv $deploy_root/ti-sdk-$m* $exports_root/
> +    mv $deploy_root/${INSTALLER_PREFIX}-$m* $exports_root/
>  
>      # Create the md5sum file
>      cd $exports_root
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Denys Dmytriyenko]

Can you please elaborate on this change? You don't seem to be increasing 
Bitbake's verbosity level, just enabling capturing stdout and stderr into a 
file, which gets captured by results.html anyway. What's the purpose?


On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable logging stdout
>   and stderr for the bitbake command to the build log.
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/oesdk/bitbake-test-sdk-image b/lib/oesdk/bitbake-test-sdk-image
> index cff86e4..7d8d093 100644
> --- a/lib/oesdk/bitbake-test-sdk-image
> +++ b/lib/oesdk/bitbake-test-sdk-image
> @@ -375,12 +375,16 @@ bitbake_sdk_images(){
>          for c in "${bitbake_command_list[@]}"
>          do
>              log $machine_build_log echo "executing bitbake command $c for machine $m"
> -            MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a $machine_build_log
> +            else
> +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> +            fi
>  
>              # Check the return status of the build process.  If the build returned
>              # a non-zero exit value then log the failure and continue (without
>              # testing).  A lack of a test file will indicate a test skip
> -            if [ "$?" != "0" ]
> +            if [ "${PIPESTATUS[0]}" != "0" ]
>              then
>                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
>                  build_status="fail"
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 1/4] config-build-env: Add support for adding a source mirror

[Cooper Jr., Franklin]

Acked-by: Franklin Cooper Jr. <fcooper@ti.com>

> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> bounces@arago-project.org] On Behalf Of Stiffler, Jacob
> Sent: Thursday, September 04, 2014 12:31 PM
> To: meta-arago@arago-project.org
> Subject: [meta-arago] [tisdk-build-scripts][PATCH 1/4] config-build-env: Add
> support for adding a source mirror
> 
> * Source mirrors may be used by setting the SOURCE_MIRROR_URL
> parameter in the
>   configuration file.
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/config-build-env |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/lib/oesdk/config-build-env b/lib/oesdk/config-build-env index
> 655a7eb..cace93f 100644
> --- a/lib/oesdk/config-build-env
> +++ b/lib/oesdk/config-build-env
> @@ -74,5 +74,10 @@ config_build_dir() {
>      sed -i "s+^SSTATE_DIR =.*+STATE_DIR = \"$BUILD_ROOT/sstate-
> cache\"+" local.conf
>      sed -i "s+^TMPDIR =.*+TMPDIR = \"$BUILD_ROOT/$build_dir/arago-
> tmp\"+" local.conf
>      sed -i "s+^export BUILDDIR=.*+export
> BUILDDIR=\"$BUILD_ROOT/$build_dir\"+" setenv
> +
> +    if [ ! -z "$SOURCE_MIRROR_URL" ]; then
> +      echo "SOURCE_MIRROR_URL = \"$SOURCE_MIRROR_URL\"" >>
> local.conf
> +      echo "INHERIT += \"own-mirrors\"" >> local.conf
> +    fi
>      cd - > /dev/null 2>&1
>  }
> --
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

[Cooper Jr., Franklin]

Acked-by: Franklin Cooper Jr. <fcooper@ti.com>

> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> bounces@arago-project.org] On Behalf Of Stiffler, Jacob
> Sent: Thursday, September 04, 2014 12:31 PM
> To: meta-arago@arago-project.org
> Subject: [meta-arago] [tisdk-build-scripts][PATCH 2/4] package-sdks: Add
> configuration parameter to specify the installer prefix.
> 
> * The configuration parameter INSTALLER_PREFIX is used to set the prefix of
> the i
>   installer filename and the default installation directory.
> * This parameter must be set when PRODUCTIZE_SDK="true"
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/package-sdks |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/oesdk/package-sdks b/lib/oesdk/package-sdks index
> d6b01f7..9bfd887 100644
> --- a/lib/oesdk/package-sdks
> +++ b/lib/oesdk/package-sdks
> @@ -109,7 +109,7 @@ create_sd_card_content() {
>      cd $start_here_root
> 
>      # Copy the installer
> -    cp $DEPLOY_ROOT/$m/$BUILD_ID/ti-sdk-$m* $start_here_root/
> +    cp $DEPLOY_ROOT/$m/$BUILD_ID/${INSTALLER_PREFIX}-$m*
> + $start_here_root/
> 
>      if [ "$?" != "0" ]
>      then
> @@ -184,7 +184,7 @@ create_sdk_installer() {
> 
>      $INSTALL_BUILDER/builder build $INSTALL_BUILDER_PROJECT linux --
> setvars \
>          sdk_loc="$installer_root/" \
> -        sdk_name_prefix="ti-sdk"                  \
> +        sdk_name_prefix="${INSTALLER_PREFIX}"                  \
>          sdk_tar_name=$sdk_tar                     \
>          output_dir="$deploy_root"                 \
>          platform="$m"                             \
> @@ -277,7 +277,7 @@ package_web_content() {
>      fi
> 
>      # Move the installer into the exports directory
> -    mv $deploy_root/ti-sdk-$m* $exports_root/
> +    mv $deploy_root/${INSTALLER_PREFIX}-$m* $exports_root/
> 
>      # Create the md5sum file
>      cd $exports_root
> --
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

[Stiffler, Jacob]

I have been using "processor-linux-sdk" for the prefix.


-----Original Message-----
From: Dmytriyenko, Denys 
Sent: Thursday, September 04, 2014 1:37 PM
To: Stiffler, Jacob
Cc: meta-arago@arago-project.org
Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

Just a quick question - what do you plan to use instead of "ti-sdk" prefix?


On Thu, Sep 04, 2014 at 01:31:06PM -0400, Jacob Stiffler wrote:
> * The configuration parameter INSTALLER_PREFIX is used to set the prefix of the i
>   installer filename and the default installation directory.
> * This parameter must be set when PRODUCTIZE_SDK="true"
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/package-sdks |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/oesdk/package-sdks b/lib/oesdk/package-sdks index 
> d6b01f7..9bfd887 100644
> --- a/lib/oesdk/package-sdks
> +++ b/lib/oesdk/package-sdks
> @@ -109,7 +109,7 @@ create_sd_card_content() {
>      cd $start_here_root
>  
>      # Copy the installer
> -    cp $DEPLOY_ROOT/$m/$BUILD_ID/ti-sdk-$m* $start_here_root/
> +    cp $DEPLOY_ROOT/$m/$BUILD_ID/${INSTALLER_PREFIX}-$m* 
> + $start_here_root/
>  
>      if [ "$?" != "0" ]
>      then
> @@ -184,7 +184,7 @@ create_sdk_installer() {
>  
>      $INSTALL_BUILDER/builder build $INSTALL_BUILDER_PROJECT linux --setvars \
>          sdk_loc="$installer_root/" \
> -        sdk_name_prefix="ti-sdk"                  \
> +        sdk_name_prefix="${INSTALLER_PREFIX}"                  \
>          sdk_tar_name=$sdk_tar                     \
>          output_dir="$deploy_root"                 \
>          platform="$m"                             \
> @@ -277,7 +277,7 @@ package_web_content() {
>      fi
>  
>      # Move the installer into the exports directory
> -    mv $deploy_root/ti-sdk-$m* $exports_root/
> +    mv $deploy_root/${INSTALLER_PREFIX}-$m* $exports_root/
>  
>      # Create the md5sum file
>      cd $exports_root
> --
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Stiffler, Jacob]

This change is to capture stderr and stdout to a file. I could not find anywhere that the stderr and stdout of the bitbake command was logged.  From what I see, results.html only shows the configuration parameters. In the log directory, the $m-build-log.txt only contains a single line: " executing bitbake command arago-amsdk-image for machine am57xx-evm". 

Without this, the only place I can find the complete log is the Jenkins console in a browser window. Here is an example of what I would like to enable with this change: http://158.218.103.230/nightly_builds/mcsdk-8.0.x/75-2014-09-03_13-16-59/artifacts/logs/log-files/am57xx-evm-build-log.txt 



-----Original Message-----
From: Dmytriyenko, Denys 
Sent: Thursday, September 04, 2014 1:39 PM
To: Stiffler, Jacob
Cc: meta-arago@arago-project.org
Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

Can you please elaborate on this change? You don't seem to be increasing Bitbake's verbosity level, just enabling capturing stdout and stderr into a file, which gets captured by results.html anyway. What's the purpose?


On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable logging stdout
>   and stderr for the bitbake command to the build log.
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/oesdk/bitbake-test-sdk-image 
> b/lib/oesdk/bitbake-test-sdk-image
> index cff86e4..7d8d093 100644
> --- a/lib/oesdk/bitbake-test-sdk-image
> +++ b/lib/oesdk/bitbake-test-sdk-image
> @@ -375,12 +375,16 @@ bitbake_sdk_images(){
>          for c in "${bitbake_command_list[@]}"
>          do
>              log $machine_build_log echo "executing bitbake command $c for machine $m"
> -            MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a $machine_build_log
> +            else
> +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> +            fi
>  
>              # Check the return status of the build process.  If the build returned
>              # a non-zero exit value then log the failure and continue (without
>              # testing).  A lack of a test file will indicate a test skip
> -            if [ "$?" != "0" ]
> +            if [ "${PIPESTATUS[0]}" != "0" ]
>              then
>                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
>                  build_status="fail"
> --
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.

[Denys Dmytriyenko]

Where's this name come from? You can reply off the list, if needed.


On Thu, Sep 04, 2014 at 01:56:10PM -0400, Stiffler, Jacob wrote:
> I have been using "processor-linux-sdk" for the prefix.
> 
> 
> -----Original Message-----
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 04, 2014 1:37 PM
> To: Stiffler, Jacob
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 2/4] package-sdks: Add configuration parameter to specify the installer prefix.
> 
> Just a quick question - what do you plan to use instead of "ti-sdk" prefix?
> 
> 
> On Thu, Sep 04, 2014 at 01:31:06PM -0400, Jacob Stiffler wrote:
> > * The configuration parameter INSTALLER_PREFIX is used to set the prefix of the i
> >   installer filename and the default installation directory.
> > * This parameter must be set when PRODUCTIZE_SDK="true"
> > 
> > Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> > ---
> >  lib/oesdk/package-sdks |    6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/lib/oesdk/package-sdks b/lib/oesdk/package-sdks index 
> > d6b01f7..9bfd887 100644
> > --- a/lib/oesdk/package-sdks
> > +++ b/lib/oesdk/package-sdks
> > @@ -109,7 +109,7 @@ create_sd_card_content() {
> >      cd $start_here_root
> >  
> >      # Copy the installer
> > -    cp $DEPLOY_ROOT/$m/$BUILD_ID/ti-sdk-$m* $start_here_root/
> > +    cp $DEPLOY_ROOT/$m/$BUILD_ID/${INSTALLER_PREFIX}-$m* 
> > + $start_here_root/
> >  
> >      if [ "$?" != "0" ]
> >      then
> > @@ -184,7 +184,7 @@ create_sdk_installer() {
> >  
> >      $INSTALL_BUILDER/builder build $INSTALL_BUILDER_PROJECT linux --setvars \
> >          sdk_loc="$installer_root/" \
> > -        sdk_name_prefix="ti-sdk"                  \
> > +        sdk_name_prefix="${INSTALLER_PREFIX}"                  \
> >          sdk_tar_name=$sdk_tar                     \
> >          output_dir="$deploy_root"                 \
> >          platform="$m"                             \
> > @@ -277,7 +277,7 @@ package_web_content() {
> >      fi
> >  
> >      # Move the installer into the exports directory
> > -    mv $deploy_root/ti-sdk-$m* $exports_root/
> > +    mv $deploy_root/${INSTALLER_PREFIX}-$m* $exports_root/
> >  
> >      # Create the md5sum file
> >      cd $exports_root
> > --
> > 1.7.9.5
> > 
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Denys Dmytriyenko]

On Thu, Sep 04, 2014 at 02:05:01PM -0400, Stiffler, Jacob wrote:
> This change is to capture stderr and stdout to a file. I could not find 
> anywhere that the stderr and stdout of the bitbake command was logged.  From 
> what I see, results.html only shows the configuration parameters. In the log 
> directory, the $m-build-log.txt only contains a single line: " executing 
> bitbake command arago-amsdk-image for machine am57xx-evm".

Yes, you are right, it's captured by Jenkins, not results.html...
I've been meaning to add the per-machine logs to the output and email, but 
never had time. This basically makes it possible - thanks!


> Without this, the only place I can find the complete log is the Jenkins 
> console in a browser window. Here is an example of what I would like to 
> enable with this change: 
> http://158.218.103.230/nightly_builds/mcsdk-8.0.x/75-2014-09-03_13-16-59/artifacts/logs/log-files/am57xx-evm-build-log.txt
> 
> 
> 
> -----Original Message-----
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 04, 2014 1:39 PM
> To: Stiffler, Jacob
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.
> 
> Can you please elaborate on this change? You don't seem to be increasing Bitbake's verbosity level, just enabling capturing stdout and stderr into a file, which gets captured by results.html anyway. What's the purpose?
> 
> 
> On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> > * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable logging stdout
> >   and stderr for the bitbake command to the build log.
> > 
> > Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> > ---
> >  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
> >  1 file changed, 6 insertions(+), 2 deletions(-)
> > 
> > diff --git a/lib/oesdk/bitbake-test-sdk-image 
> > b/lib/oesdk/bitbake-test-sdk-image
> > index cff86e4..7d8d093 100644
> > --- a/lib/oesdk/bitbake-test-sdk-image
> > +++ b/lib/oesdk/bitbake-test-sdk-image
> > @@ -375,12 +375,16 @@ bitbake_sdk_images(){
> >          for c in "${bitbake_command_list[@]}"
> >          do
> >              log $machine_build_log echo "executing bitbake command $c for machine $m"
> > -            MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> > +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a $machine_build_log
> > +            else
> > +                MACHINE=$m EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}" TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > +            fi
> >  
> >              # Check the return status of the build process.  If the build returned
> >              # a non-zero exit value then log the failure and continue (without
> >              # testing).  A lack of a test file will indicate a test skip
> > -            if [ "$?" != "0" ]
> > +            if [ "${PIPESTATUS[0]}" != "0" ]
> >              then
> >                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
> >                  build_status="fail"
> > --
> > 1.7.9.5
> > 
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Cooper Jr., Franklin]

> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> bounces@arago-project.org] On Behalf Of Dmytriyenko, Denys
> Sent: Thursday, September 04, 2014 2:03 PM
> To: Stiffler, Jacob
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-
> image: Add support to control verbosity of build logging.
> 
> On Thu, Sep 04, 2014 at 02:05:01PM -0400, Stiffler, Jacob wrote:
> > This change is to capture stderr and stdout to a file. I could not
> > find anywhere that the stderr and stdout of the bitbake command was
> > logged.  From what I see, results.html only shows the configuration
> > parameters. In the log directory, the $m-build-log.txt only contains a
> > single line: " executing bitbake command arago-amsdk-image for machine
> am57xx-evm".
> 
> Yes, you are right, it's captured by Jenkins, not results.html...
> I've been meaning to add the per-machine logs to the output and email, but
> never had time. This basically makes it possible - thanks!
[Franklin] Took me awhile to realize we never actually do anything with that build-log file.
Jacob,

How are you uploading your builds to your server? We don't upload this log file so having your patch upload that file also along with the results file would make things very useful for all of us.                                                                                                                                                                             
> 
> 
> > Without this, the only place I can find the complete log is the Jenkins
> > console in a browser window. Here is an example of what I would like to
> > enable with this change:
> > http://158.218.103.230/nightly_builds/mcsdk-8.0.x/75-2014-09-03_13-16-
> 59/artifacts/logs/log-files/am57xx-evm-build-log.txt
> >
> >
> >
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Thursday, September 04, 2014 1:39 PM
> > To: Stiffler, Jacob
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-
> sdk-image: Add support to control verbosity of build logging.
> >
> > Can you please elaborate on this change? You don't seem to be increasing
> Bitbake's verbosity level, just enabling capturing stdout and stderr into a file,
> which gets captured by results.html anyway. What's the purpose?
> >
> >
> > On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> > > * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable
> logging stdout
> > >   and stderr for the bitbake command to the build log.
> > >
> > > Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> > > ---
> > >  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
> > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/lib/oesdk/bitbake-test-sdk-image
> > > b/lib/oesdk/bitbake-test-sdk-image
> > > index cff86e4..7d8d093 100644
> > > --- a/lib/oesdk/bitbake-test-sdk-image
> > > +++ b/lib/oesdk/bitbake-test-sdk-image
> > > @@ -375,12 +375,16 @@ bitbake_sdk_images(){
> > >          for c in "${bitbake_command_list[@]}"
> > >          do
> > >              log $machine_build_log echo "executing bitbake command $c for
> machine $m"
> > > -            MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> > > +                MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a
> $machine_build_log
> > > +            else
> > > +                MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > +            fi
> > >
> > >              # Check the return status of the build process.  If the build
> returned
> > >              # a non-zero exit value then log the failure and continue (without
> > >              # testing).  A lack of a test file will indicate a test skip
> > > -            if [ "$?" != "0" ]
> > > +            if [ "${PIPESTATUS[0]}" != "0" ]
> > >              then
> > >                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
> > >                  build_status="fail"
> > > --
> > > 1.7.9.5
> > >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Stiffler, Jacob]

>>>
[Franklin] Took me awhile to realize we never actually do anything with that build-log file.
Jacob,

How are you uploading your builds to your server? We don't upload this log file so having your patch upload that file also along with the results file would make things very useful for all of us.    
<<<

The upload to the archive server is done by our common Jenkins scripts (which are responsible for creating a VM, generating the results email, etc...). I am simply copying the $LOG_DIR to the location that will get copied. We have a single tarbal (artifacts.tar.gz) which will get uploaded to this server.

If your are interested, in our build wrapper, I also implemented a way to parse the logs to get the recipe that caused an error and copy the appropriate error log to the $LOG_DIR.

-----Original Message-----
From: Cooper Jr., Franklin 
Sent: Thursday, September 04, 2014 3:09 PM
To: Dmytriyenko, Denys; Stiffler, Jacob
Cc: meta-arago@arago-project.org
Subject: RE: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.



> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago- 
> bounces@arago-project.org] On Behalf Of Dmytriyenko, Denys
> Sent: Thursday, September 04, 2014 2:03 PM
> To: Stiffler, Jacob
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] 
> bitbake-test-sdk-
> image: Add support to control verbosity of build logging.
> 
> On Thu, Sep 04, 2014 at 02:05:01PM -0400, Stiffler, Jacob wrote:
> > This change is to capture stderr and stdout to a file. I could not 
> > find anywhere that the stderr and stdout of the bitbake command was 
> > logged.  From what I see, results.html only shows the configuration 
> > parameters. In the log directory, the $m-build-log.txt only contains 
> > a single line: " executing bitbake command arago-amsdk-image for 
> > machine
> am57xx-evm".
> 
> Yes, you are right, it's captured by Jenkins, not results.html...
> I've been meaning to add the per-machine logs to the output and email, 
> but never had time. This basically makes it possible - thanks!
[Franklin] Took me awhile to realize we never actually do anything with that build-log file.
Jacob,

How are you uploading your builds to your server? We don't upload this log file so having your patch upload that file also along with the results file would make things very useful for all of us.                                                                                                                                                                             
> 
> 
> > Without this, the only place I can find the complete log is the 
> > Jenkins console in a browser window. Here is an example of what I 
> > would like to enable with this change:
> > http://158.218.103.230/nightly_builds/mcsdk-8.0.x/75-2014-09-03_13-1
> > 6-
> 59/artifacts/logs/log-files/am57xx-evm-build-log.txt
> >
> >
> >
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Thursday, September 04, 2014 1:39 PM
> > To: Stiffler, Jacob
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] 
> > bitbake-test-
> sdk-image: Add support to control verbosity of build logging.
> >
> > Can you please elaborate on this change? You don't seem to be 
> > increasing
> Bitbake's verbosity level, just enabling capturing stdout and stderr 
> into a file, which gets captured by results.html anyway. What's the purpose?
> >
> >
> > On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> > > * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable
> logging stdout
> > >   and stderr for the bitbake command to the build log.
> > >
> > > Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> > > ---
> > >  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
> > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/lib/oesdk/bitbake-test-sdk-image
> > > b/lib/oesdk/bitbake-test-sdk-image
> > > index cff86e4..7d8d093 100644
> > > --- a/lib/oesdk/bitbake-test-sdk-image
> > > +++ b/lib/oesdk/bitbake-test-sdk-image
> > > @@ -375,12 +375,16 @@ bitbake_sdk_images(){
> > >          for c in "${bitbake_command_list[@]}"
> > >          do
> > >              log $machine_build_log echo "executing bitbake 
> > > command $c for
> machine $m"
> > > -            MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> > > +                MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a 
> $machine_build_log
> > > +            else
> > > +                MACHINE=$m
> EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > +            fi
> > >
> > >              # Check the return status of the build process.  If 
> > > the build
> returned
> > >              # a non-zero exit value then log the failure and continue (without
> > >              # testing).  A lack of a test file will indicate a test skip
> > > -            if [ "$?" != "0" ]
> > > +            if [ "${PIPESTATUS[0]}" != "0" ]
> > >              then
> > >                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
> > >                  build_status="fail"
> > > --
> > > 1.7.9.5
> > >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.

[Denys Dmytriyenko]

On Thu, Sep 04, 2014 at 03:19:37PM -0400, Stiffler, Jacob wrote:
> >>>
> [Franklin] Took me awhile to realize we never actually do anything with that 
> build-log file.
> Jacob,
> 
> How are you uploading your builds to your server? We don't upload this log 
> file so having your patch upload that file also along with the results file 
> would make things very useful for all of us.
>  <<<
> 
> The upload to the archive server is done by our common Jenkins scripts 
> (which are responsible for creating a VM, generating the results email, 
> etc...). I am simply copying the $LOG_DIR to the location that will get 
> copied. We have a single tarbal (artifacts.tar.gz) which will get uploaded 
> to this server.
> 
> If your are interested, in our build wrapper, I also implemented a way to 
> parse the logs to get the recipe that caused an error and copy the 
> appropriate error log to the $LOG_DIR.

Can we implement that part here in tisdk-build-scripts? The icing on the cake 
wwould be to link individual machine logs from the main results.html log and 
email - I'd be willing to provide space on arago-project.org for the logs, so 
one can simply click on the FAILED status and open up the corrspoding build 
log to ivestigate!

-- 
Denys


> -----Original Message-----
> From: Cooper Jr., Franklin 
> Sent: Thursday, September 04, 2014 3:09 PM
> To: Dmytriyenko, Denys; Stiffler, Jacob
> Cc: meta-arago@arago-project.org
> Subject: RE: [meta-arago] [tisdk-build-scripts][PATCH 3/4] bitbake-test-sdk-image: Add support to control verbosity of build logging.
> 
> 
> 
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago- 
> > bounces@arago-project.org] On Behalf Of Dmytriyenko, Denys
> > Sent: Thursday, September 04, 2014 2:03 PM
> > To: Stiffler, Jacob
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] 
> > bitbake-test-sdk-
> > image: Add support to control verbosity of build logging.
> > 
> > On Thu, Sep 04, 2014 at 02:05:01PM -0400, Stiffler, Jacob wrote:
> > > This change is to capture stderr and stdout to a file. I could not 
> > > find anywhere that the stderr and stdout of the bitbake command was 
> > > logged.  From what I see, results.html only shows the configuration 
> > > parameters. In the log directory, the $m-build-log.txt only contains 
> > > a single line: " executing bitbake command arago-amsdk-image for 
> > > machine
> > am57xx-evm".
> > 
> > Yes, you are right, it's captured by Jenkins, not results.html...
> > I've been meaning to add the per-machine logs to the output and email, 
> > but never had time. This basically makes it possible - thanks!
> [Franklin] Took me awhile to realize we never actually do anything with that build-log file.
> Jacob,
> 
> How are you uploading your builds to your server? We don't upload this log file so having your patch upload that file also along with the results file would make things very useful for all of us.                                                                                                                                                                             
> > 
> > 
> > > Without this, the only place I can find the complete log is the 
> > > Jenkins console in a browser window. Here is an example of what I 
> > > would like to enable with this change:
> > > http://158.218.103.230/nightly_builds/mcsdk-8.0.x/75-2014-09-03_13-1
> > > 6-
> > 59/artifacts/logs/log-files/am57xx-evm-build-log.txt
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Dmytriyenko, Denys
> > > Sent: Thursday, September 04, 2014 1:39 PM
> > > To: Stiffler, Jacob
> > > Cc: meta-arago@arago-project.org
> > > Subject: Re: [meta-arago] [tisdk-build-scripts][PATCH 3/4] 
> > > bitbake-test-
> > sdk-image: Add support to control verbosity of build logging.
> > >
> > > Can you please elaborate on this change? You don't seem to be 
> > > increasing
> > Bitbake's verbosity level, just enabling capturing stdout and stderr 
> > into a file, which gets captured by results.html anyway. What's the purpose?
> > >
> > >
> > > On Thu, Sep 04, 2014 at 01:31:07PM -0400, Jacob Stiffler wrote:
> > > > * Setting BUILD_LOG_VERBOSE="true" (case sensitive) will enable
> > logging stdout
> > > >   and stderr for the bitbake command to the build log.
> > > >
> > > > Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> > > > ---
> > > >  lib/oesdk/bitbake-test-sdk-image |    8 ++++++--
> > > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/lib/oesdk/bitbake-test-sdk-image
> > > > b/lib/oesdk/bitbake-test-sdk-image
> > > > index cff86e4..7d8d093 100644
> > > > --- a/lib/oesdk/bitbake-test-sdk-image
> > > > +++ b/lib/oesdk/bitbake-test-sdk-image
> > > > @@ -375,12 +375,16 @@ bitbake_sdk_images(){
> > > >          for c in "${bitbake_command_list[@]}"
> > > >          do
> > > >              log $machine_build_log echo "executing bitbake 
> > > > command $c for
> > machine $m"
> > > > -            MACHINE=$m
> > EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> > TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > > +            if [ "${BUILD_LOG_VERBOSE}" = "true" ]; then
> > > > +                MACHINE=$m
> > EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> > TISDK_VERSION="${TISDK_VERSION}" bitbake $c 2>&1 | eval tee -a 
> > $machine_build_log
> > > > +            else
> > > > +                MACHINE=$m
> > EXTRA_TISDK_FILES="${INSTALLER_EXTRAS_ROOT}/${MACHINE}"
> > TISDK_VERSION="${TISDK_VERSION}" bitbake $c
> > > > +            fi
> > > >
> > > >              # Check the return status of the build process.  If 
> > > > the build
> > returned
> > > >              # a non-zero exit value then log the failure and continue (without
> > > >              # testing).  A lack of a test file will indicate a test skip
> > > > -            if [ "$?" != "0" ]
> > > > +            if [ "${PIPESTATUS[0]}" != "0" ]
> > > >              then
> > > >                  echo "FAILED" > $LOG_DIR/$m-build-result.txt
> > > >                  build_status="fail"
> > > > --
> > > > 1.7.9.5
> > > >
> > > > _______________________________________________
> > > > meta-arago mailing list
> > > > meta-arago@arago-project.org
> > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago