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

[Jean-François Dagenais]

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.

Thanks for your reply!