All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] ti-ccsv6-native: Add CCS 6.1.1.00022
Date: Thu, 22 Oct 2015 10:33:41 -0400	[thread overview]
Message-ID: <20151022143341.GB8780@edge> (raw)
In-Reply-To: <1445522994-16866-1-git-send-email-j-stiffler@ti.com>

On Thu, Oct 22, 2015 at 10:09:54AM -0400, Jacob Stiffler wrote:
> * Due to licensing, this installer must be downloaded manually and
>   placed into either the downloads directory, or placed on a mirror.
> * Please see http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_6_Downloads
> 
> * NOTE: That the Linux off-line installation tarball is the file required.
> 
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
>  recipes-ti/devtools/ti-ccsv6-native_6.1.1.00022.bb | 40 ++++++++++++++++++++++
>  recipes-ti/includes/ti-paths.inc                   |  4 +++
>  2 files changed, 44 insertions(+)
>  create mode 100644 recipes-ti/devtools/ti-ccsv6-native_6.1.1.00022.bb
> 
> diff --git a/recipes-ti/devtools/ti-ccsv6-native_6.1.1.00022.bb b/recipes-ti/devtools/ti-ccsv6-native_6.1.1.00022.bb
> new file mode 100644
> index 0000000..11590b9
> --- /dev/null
> +++ b/recipes-ti/devtools/ti-ccsv6-native_6.1.1.00022.bb
> @@ -0,0 +1,40 @@
> +DESCRIPTION = "TI DSP Code Generation Tools"
> +HOMEPAGE = "https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm"
> +LICENSE = "(TI-TSPA & Thai-Open-Source-Software-Center) & BSD-3-Clause & BSL-1.0 & Hewlett-Packard & AFL-3.0 & MIT & BSD-2-Clause & PD"
> +
> +LIC_FILES_CHKSUM = "file://${WORKDIR}/ccsv6/doc/EULA/EULA.doc;md5=24fb8a52ac52d3938b5888362edb295a"
> +
> +inherit native
> +
> +require recipes-ti/includes/ti-unpack.inc
> +require recipes-ti/includes/ti-staging.inc
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = "http://install.source.dir.local/CCS${PV}_linux.tar.gz;name=ccsv6"
> +
> +S = "${WORKDIR}/CCS${PV}_linux"
> +
> +BINFILE = "CCS${PV}_linux/ccs_setup_${PV}.bin"
> +TI_BIN_UNPK_ARGS = "--mode unattended --prefix ${WORKDIR}"
> +TI_BIN_UNPK_CMDS = ""
> +
> +SRC_URI[ccsv6.md5sum] = "648d5f41e8a7a93c16d51cd34045ba15"
> +SRC_URI[ccsv6.sha256sum] = "b82958a125d5c6bea07cfc12a6f2a77c45e1560217c1aac02194b6e3408c5105"
> +
> +do_install() {
> +    install -d ${D}${CCSv6_INSTALL_DIR_RECIPE}
> +    cp -r ${WORKDIR}/ccsv6/. ${D}${CCSv6_INSTALL_DIR_RECIPE}
> +
> +    install -d ${D}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}
> +    cp -r ${WORKDIR}/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/. \

You may want to extract cgt version into a variable. Even though it's specific 
to CCS version, it might be useful to have it set as a variable.


> +          ${D}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}
> +}
> +
> +FILES_${PN} += "\
> +  ${CCSv6_INSTALL_DIR_RECIPE} \
> +  ${M4_TOOLCHAIN_INSTALL_DIR_RECIPE} \
> +"
> +
> +INSANE_SKIP_${PN} = "arch libdir ldflags staticdev textrel dev-so"
> +
> +EXCLUDE_FROM_SHLIBS = "1"
> diff --git a/recipes-ti/includes/ti-paths.inc b/recipes-ti/includes/ti-paths.inc
> index bd80fa1..a38685e 100644
> --- a/recipes-ti/includes/ti-paths.inc
> +++ b/recipes-ti/includes/ti-paths.inc
> @@ -45,6 +45,8 @@ export XDAIS_INSTALL_DIR_RECIPE      = "${installdir}/ti-xdais-tree"
>  export XDC_INSTALL_DIR_RECIPE        = "${installdir}/ti-xdctools-tree"
>  export PDK_INSTALL_DIR_RECIPE        = "${installdir}/ti-pdk-tree"
>  export OSAL_INSTALL_DIR_RECIPE       = "${installdir}/ti-osal-tree"
> +export M4_TOOLCHAIN_INSTALL_DIR_RECIPE    = "${installdir}/ti-cgt-arm"
> +export CCSv6_INSTALL_DIR_RECIPE           = "${installdir}/ccsv6"

Lowercase character in otherwise all-caps variable name? Technically it's 
acceptable, but could potentially cause some troubles... It's up to you :)


>  # This is where the tools will end up in sysroot
>  export BIOS_INSTALL_DIR       = "${STAGING_DIR_TARGET}${BIOS_INSTALL_DIR_RECIPE}"
> @@ -80,6 +82,8 @@ export XDAIS_INSTALL_DIR      = "${STAGING_DIR_TARGET}${XDAIS_INSTALL_DIR_RECIPE
>  export XDC_INSTALL_DIR        = "${STAGING_DIR_TARGET}${XDC_INSTALL_DIR_RECIPE}"
>  export PDK_INSTALL_DIR        = "${STAGING_DIR_TARGET}${PDK_INSTALL_DIR_RECIPE}"
>  export OSAL_INSTALL_DIR       = "${STAGING_DIR_TARGET}${OSAL_INSTALL_DIR_RECIPE}"
> +export M4_TOOLCHAIN_INSTALL_DIR    = "${STAGING_DIR_NATIVE}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}"
> +export CCSv6_INSTALL_DIR           = "${STAGING_DIR_NATIVE}${CCSv6_INSTALL_DIR_RECIPE}"
>  
>  DSPSUFFIX_omapl137 = "x674"
>  DSPSUFFIX_omapl138 = "x674"
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


      parent reply	other threads:[~2015-10-22 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 14:09 [PATCH] ti-ccsv6-native: Add CCS 6.1.1.00022 Jacob Stiffler
2015-10-22 14:18 ` Jacob Stiffler
2015-10-22 14:33 ` Denys Dmytriyenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151022143341.GB8780@edge \
    --to=denys@ti.com \
    --cc=j-stiffler@ti.com \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.