This is a simple example of hooks at the post-build stage of fusesoc. In my sense, the hook MUST be executed in order of specification of each item. (i.e., generate_mcs_AA (if target_chip_AA is defined) -> generate_chip_BB (if target_chip_BB is defined) -> post_build_script)
However, I found if there are hook items with the conditional statements, they go to the back of the list. So, if target_chip_AA is defined, fusesoc executes the hook items in this order: post_build_script -> target_chip_AA.
This sense is not intuition and must be fixed as the order will be kept.
Currently, I am using the following configuration to keep the order.
The CAPI 2 format supports the conditional inclusion as follows:
This is a simple example of hooks at the post-build stage of fusesoc. In my sense, the hook MUST be executed in order of specification of each item. (i.e.,
generate_mcs_AA(iftarget_chip_AAis defined) ->generate_chip_BB(iftarget_chip_BBis defined) ->post_build_script) However, I found if there are hook items with the conditional statements, they go to the back of the list. So, iftarget_chip_AAis defined, fusesoc executes the hook items in this order:post_build_script->target_chip_AA. This sense is not intuition and must be fixed as the order will be kept.Currently, I am using the following configuration to keep the order.
Please fix this problem at the next patch.