> Also I woud advise against this common dir in boards, since it prevents
users from creating custom boards from built-in ones.
We can still create a custom board from an in-tree board that has the
common dir. We just have to either include the common dir or remove it
and adapt the makefiles as we did here.
I have something similar to this:
tree -L 2 boards/
|── board1
│ ├── configs
...
│ └── src
|── board2
│ ├── configs
...
│ └── src
└── stm32
├── common
├── drivers
└── stm32-board1
└── stm32-board2
I think the common dir just added an extra step (although, it's not too obvious)
> I've just tested the external board build following these simple steps.
These steps will work because STM32L4 family doesn't have a common
directory. This is the "old" method that Sebastien was referring to.
In any case, I think we can write a script that can create a custom
board based on an in-tree board, regardless of the presence or not of
the common directory.
On Thu, May 20, 2021 at 2:35 PM Alan Carvalho de Assis
<acas...@gmail.com> wrote:
>
> I agree, it should a good idea if it could be turned into a Documentation
> page!
>
> BR,
>
> Alan
>
> On 5/20/21, Sebastien Lorquet <sebast...@lorquet.fr> wrote:
> > :o
> >
> > it worked.
> >
> > How am I supposed to guess this?
> >
> > Your email should be copied verbatim in the official documentation
> > somewhere under "how to create and build a custom board"
> >
> > Also I woud advise against this common dir in boards, since it prevents
> > users from creating custom boards from built-in ones.
> >
> > Duplication is not always bad, as we know...
> >
> > Sebastien
> >
> >
> > Le 20/05/2021 à 15:27, Abdelatif Guettouche a écrit :
> >> Rename Make.defs to Makefile
> >
