It leads to an unexpected behavior where a user can only partially find libraries before using them in a custom target, be it a library or an executable.
It casts doubt on the way CoreLibs are created today, i.e. as part of creating a user target.
It'll probably be wiser to create them as part of a setup function, such as get_board_id, which must be called in order for the framework to behave correctly. This function will of course be renamed if CoreLib creation will be embedded in it.
Since it's a big change which directly affects the API, it'll probably be wiser to integrate it into v0.7, and not just as a patch.
It leads to an unexpected behavior where a user can only partially find libraries before using them in a custom target, be it a library or an executable.
It casts doubt on the way CoreLibs are created today, i.e. as part of creating a user target. It'll probably be wiser to create them as part of a setup function, such as
get_board_id
, which must be called in order for the framework to behave correctly. This function will of course be renamed if CoreLib creation will be embedded in it.Since it's a big change which directly affects the API, it'll probably be wiser to integrate it into v0.7, and not just as a patch.