> -----Original Message-----
> From: Jean-François Dagenais [mailto:[email protected]]
> Sent: Friday, July 07, 2017 7:29 PM
> To: Manjukumar Harthikote Matha <[email protected]>
> Cc: Jean-François Dagenais <[email protected]>; Sai Pavan Boddu
> <[email protected]>; Cyril Chemparathy <[email protected]>; git
> <[email protected]>; [email protected]; [email protected]
> Subject: Re: [PATCH 6/7] xsctbase: rebuild all products when XILINX_VER_MAIN
> changes
>
> On Jul 7, 2017, at 18:21, Manjukumar Harthikote Matha
> <[email protected]> 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.

-- 
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to