Well, the boot loader is actually a full application, which is something that
has not yet been part of the RIOT source tree. So I suggest to create a new base
directory "applications" under dist/ or root (I am leaning towards dist/) for it
and put it there. That would make it either at /applications/bootloader or
/dist/applications/bootloader.
cheers
Mathias
On Mit, 2017-08-09 at 23:54 +0200, Francisco Javier Acosta Padilla wrote:
> Hi!
>
> I think I’m quite against `dist/tools/bootloader`. Most of the code there can
> be built by itself, which is not the case of the bootloader… I was maybe
> thinking about leave it there in the root or move it to sys/ as a module. The
> module option seems to me a bit adequate since is an optional feature we
> provide to some boards, and can be deactivated when is not needed.
>
> Cheers,
>
> Paco.
>
> On 9 August 2017 at 15:02:19, Martine Lenders (m...@martine-lenders.eu) wrote:
>
> Hi,
>
> gut feeling says `dist/tools/bootloader` (maybe something more unique than
> just bootloader?), since it isn't really part of the system and not really an
> example, but a quite specific application. Then again, for the same reasons I
> could argue to put it in the root folder, that IMHO should be kept small,
> however.
>
> Cheers,
> Martine
>
> 2017-08-09 13:29 GMT+02:00 Kaspar Schleiser :
> Hi everyone,
>
> PR #7457 will introduce a bootloader application.
>
> The question came up where to put it within the source tree?
> Currently the PR puts it in the root folder (./bootloader).
>
> Do we want that? Is there a better place?
>
> Options:
> examples/bootloader
> dist/tools/bootloader
> ...
>
> Kaspar
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel