[meta-xilinx] [PATCH 6/7] xsctbase: rebuild all products when XILINX_VER_MAIN changes
Manjukumar Harthikote Matha
manjukumar.harthikote-matha at xilinx.com
Sat Jul 8 09:41:15 PDT 2017
> -----Original Message-----
> From: Jean-François Dagenais [mailto:jeff.dagenais at gmail.com]
> Sent: Friday, July 07, 2017 7:29 PM
> To: Manjukumar Harthikote Matha <MANJUKUM at xilinx.com>
> Cc: Jean-François Dagenais <jeff.dagenais at gmail.com>; Sai Pavan Boddu
> <saipava at xilinx.com>; Cyril Chemparathy <cyrilc at xilinx.com>; git
> <git at xilinx.com>; michal.simek at xilinx.com; meta-xilinx at yoctoproject.org
> Subject: Re: [PATCH 6/7] xsctbase: rebuild all products when XILINX_VER_MAIN
> changes
>
> On Jul 7, 2017, at 18:21, Manjukumar Harthikote Matha
> <manjukumar.harthikote-matha at xilinx.com> wrote:
>
> 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.
>
>
> I agree. However, if you didn't, which is an entirely possible
> scenario, take us for example, it doesn't rebuild, even if you did
> swap the xsdk version. That is unexpected, and un-predictible
> behaviour. It's way better to have the faulty/non-supported build
> output every time when you are in this configuration, no matter what
> the state of your work dir timestamps.
>
> About backward compatibility... perhaps then, a "bb.warning(...)"
> would be proper when the HDF and XILINX_VER_MAIN don't match? It would
> perhaps help some people finding themselves in this situation
> unbeknownst to them.
>
Agreed, let me look into it, there might be a way to find the tool version from HDF and compare it with
XILINX_VER_MAIN
Thanks
Manju
> Thanks for your reply!
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.
More information about the meta-xilinx
mailing list