On 12 September 2011 11:53, Florian Fainelli <[email protected]> wrote: > Hello, > > On Friday 09 September 2011 16:53:15 Roman Yeryomin wrote: >> On 6 September 2011 18:37, Roman Yeryomin <[email protected]> wrote: >> > Did anyone think of separating buildroot-ng from the content (packages >> > and targets) into a separate project (under OpenWrt name of cause)? >> > Then one can do something like `make content' and depending on what is >> > configured get either openwrt or something else. >> >> Really noone? >> Well then how about not thinking but actually doing it? >> I already use it like that and thought that community could benefit >> from such approach too. > > This looks like a good idea, I am not sure about how many OpenWrt-specific > stuff > are folded into our build system, but if you have any patches to decouple > OpenWrt-specificities from buildroot, feel free to get them posted. > --
Actually build system and it's content can be very easily separated with minor changes in the structure and additional makefile. I'm using this approach for about a year already. I took fairly recent git clone of OpenWrt trunk and made two branches there: bng (separated buildroot-ng) and bng-content-owrt (separated content) and put that into github: https://github.com/yeryomin/openwrt-bng/tree/bng Of cause there is a lot of space for improvement but this can be used as start point. Maybe then sometime buildroot-ng will be able to support non linux targets also (e.g. nuttx realtime os). Regards, Roman _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
