Hello Mirko,
> Problem statement
>
> To support new chipsets, it is sometimes necessary to work with
> vendor-specific toolchains. Until now, the process to add these
> toolchains to the build environment is a manual one. This leads
> companies to create their own automation scripts, creating a p
On 23/04/2019 16:17, Jeff Kletsky wrote:
On 4/23/19 12:41 AM, Florian Eckert wrote:
Hello Mirko,
I am not a member of OpenWrt but this are my hints.
To start this process, we have collected a small number of core
features that we would propose to add to the OpenWrt build system. Our
goal w
On 4/23/19 12:41 AM, Florian Eckert wrote:
Hello Mirko,
I am not a member of OpenWrt but this are my hints.
To start this process, we have collected a small number of core
features that we would propose to add to the OpenWrt build system. Our
goal with these patches is to remove the need for
Hello Mirko,
I am not a member of OpenWrt but this are my hints.
To start this process, we have collected a small number of core
features that we would propose to add to the OpenWrt build system. Our
goal with these patches is to remove the need for companies to develop
external scripts used t
Hi OpenWrt developers,
The prpl Foundation and its members would like to open a new chapter in the
collaboration between the two projects.
One of the most important aspects is to ensure that any development prpl does
is in-line with OpenWrt expectations, guidelines, and architectural standa
