BSP_CONSOLE_MINOR option for Zynq board with new build system
Sebastian Huber
sebastian.huber at embedded-brains.de
Fri Sep 25 15:18:49 UTC 2020
On 25/09/2020 17:14, Gedare Bloom wrote:
> On Fri, Sep 25, 2020 at 9:11 AM Sebastian Huber
> <sebastian.huber at embedded-brains.de> wrote:
>> On 25/09/2020 17:08, Gedare Bloom wrote:
>>
>>>> Yes, this could be a potential problem in several BSPs. I used a script
>>>> to convert the BSP options, but to detect if it was an integer or
>>>> boolean type was just an heuristic. In order to fix this, you first have
>>>> to find the build specification item of the option:
>>>>
>>>> spec/build/bsps/arm/xilinx-zynqmp/optconminor.yml:name: BSP_CONSOLE_MINOR
>>>> spec/build/bsps/arm/xilinx-zynq/optconminor.yml:name: BSP_CONSOLE_MINOR
>>>>
>>>> So, we have this option duplicated. This is an issue on its own. At some
>>>> point in time we should unify the options across the BSPs.
>>>>
>>> Yes, I imagine we should like to use 'shared' folders at several
>>> levels of the spec/.../bsps tree
>>>
>> The "shared" folder is just a parent directory. For example
>> "spec/build/bsps" contains all items relevant to BSPs in general,
>> "spec/build/bsps/arm" contains all times relevant to "arm" architecture
>> BSPs.
> OK, that makes sense. But it does not allow for partially shared items I guess?
If you use an item or not is defined by the links. So, when a BSP
doesn't link to a parent item, then it is not used.
More information about the devel
mailing list