[meta-xilinx] [PATCH 6/7] xsctbase: rebuild all products when XILINX_VER_MAIN changes

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: Jean-Francois Dagenais [mailto:jeff.dagenais at gmail.com]
> Sent: Thursday, July 06, 2017 10:17 AM
> To: Manjukumar Harthikote Matha <MANJUKUM at xilinx.com>; Sai Pavan Boddu
> <saipava at xilinx.com>; Cyril Chemparathy <cyrilc at xilinx.com>
> Cc: git <git at xilinx.com>; michal.simek at xilinx.com; meta-xilinx at yoctoproject.org;
> Jean-Francois Dagenais <jeff.dagenais at gmail.com>
> Subject: [PATCH 6/7] xsctbase: rebuild all products when XILINX_VER_MAIN changes
>
> When we update the tools, it's natural to expect all those recipes using these tools
> to spontaneously rebuild.
>
> Signed-off-by: Jean-Francois Dagenais <jeff.dagenais at gmail.com>
> ---
>  classes/xsctbase.bbclass | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/classes/xsctbase.bbclass b/classes/xsctbase.bbclass index
> fac7b8f..0aaf9c4 100644
> --- a/classes/xsctbase.bbclass
> +++ b/classes/xsctbase.bbclass
> @@ -21,6 +21,7 @@ XSCTH_ARCH ?= "${@bb.utils.contains('XSCTH_PROC',
> 'psu_cortexa53_0', '64', '32',  PROJ_ARG ??= "-ws ${XSCTH_WS} -pname
> ${XSCTH_PROJ} -rp ${XSCTH_REPO}"
>  HW_ARG ??= "-processor ${XSCTH_PROC} -hdf ${XSCTH_HDF} -arch
> ${XSCTH_ARCH}"
>
> +do_configure[vardeps] += "XILINX_VER_MAIN"

Regenerating the HDF using newer version of the tool is always required (Vivado does not guarantee backward compatibility). I don't mind taking this patch in, however regenerating HDF is the right thing to do.

Thanks,
Manju

>  do_configure[depends] += "virtual/hdf:do_deploy"
>  do_configure[lockfiles] = "${TMPDIR}/xsct-invoke.lock"
>  do_configure() {
> --
> 2.1.4



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.