In fact, if "ocpidev build" by itself does not solve the problem, it
means there could be a dependency bug in "ocpidev build".
I.e. the "clean" action is only needed to overcome a change that
"ocpidev build" somehow does not recognize based on file modification dates.
Unless modification dates have been hacked somehow, any change should be
automatically recognized and cause a rebuild.
An example of a change that "ocpidev build" would *not* recognize is
when some input file was replaced with a different one that was still
older than the last build.
Some build systems actually look at hashes of input files rather than
modification dates, but OpenCPI doesn't.
Thus "clean" is indeed needed when something unusual like this happens.
On 5/17/23 2:35 PM, Dominic Walters via discuss wrote:
> In general, you should never have to edit files that OpenCPI generates
> in `gen` or `target-*` directories.
> If you feel like you need to: `ocpidev clean` then `ocpidev build`.
>
> On Wed, May 17, 2023 at 9:07 AM <dwp_at_md1tech.co.uk> wrote:
>
> Thanks! This worked
>
> _______________________________________________
> discuss mailing list -- discuss_at_lists.opencpi.org
> To unsubscribe send an email to discuss-leave_at_lists.opencpi.org
>
>
> _______________________________________________
> discuss mailing list --discuss_at_lists.opencpi.org
> To unsubscribe send an email todiscuss-leave_at_lists.opencpi.org
Received on Wed May 17 2023 - 19:43:18 CDT