Re: [LEDE-DEV] Predict sysupgrade file name
Thank you! On 01/31/2018 06:10 PM, John Crispin wrote: On 31/01/18 16:00, Yury Shvedov wrote: Hi all, I have a task to universal automatically predict sysupgrade (or factory) file name on the board, with already installed openwrt. The filename format is clear inside buildroot, but I can't find the way to learn CONFIG_TARGET_BOARD and CONFIG_TARGET_SUBTARGET variables values inside running system. I can pass them to my package, but it will not rebuilt when CONFIG_TARGET_SUBTARGET changed and will left invalid. I can clean it manually every time, but this way is unacceptable. Is there any common way to get that values or *sysupgrade.* filename from running system or make package rebuild each time? Hi cat /etc/openwrt_release | grep DISTRIB_TARGET DISTRIB_TARGET='mediatek/32' John -- С уважением, Юрий Шведов WiMark Systems ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Predict sysupgrade file name
Ok, sorry. Finally find simple system.board method: ubus call system board On 01/31/2018 06:00 PM, Yury Shvedov wrote: Hi all, I have a task to universal automatically predict sysupgrade (or factory) file name on the board, with already installed openwrt. The filename format is clear inside buildroot, but I can't find the way to learn CONFIG_TARGET_BOARD and CONFIG_TARGET_SUBTARGET variables values inside running system. I can pass them to my package, but it will not rebuilt when CONFIG_TARGET_SUBTARGET changed and will left invalid. I can clean it manually every time, but this way is unacceptable. Is there any common way to get that values or *sysupgrade.* filename from running system or make package rebuild each time? -- С уважением, Юрий Шведов WiMark Systems ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Predict sysupgrade file name
On 31/01/18 16:00, Yury Shvedov wrote: Hi all, I have a task to universal automatically predict sysupgrade (or factory) file name on the board, with already installed openwrt. The filename format is clear inside buildroot, but I can't find the way to learn CONFIG_TARGET_BOARD and CONFIG_TARGET_SUBTARGET variables values inside running system. I can pass them to my package, but it will not rebuilt when CONFIG_TARGET_SUBTARGET changed and will left invalid. I can clean it manually every time, but this way is unacceptable. Is there any common way to get that values or *sysupgrade.* filename from running system or make package rebuild each time? Hi cat /etc/openwrt_release | grep DISTRIB_TARGET DISTRIB_TARGET='mediatek/32' John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Predict sysupgrade file name
Hi all, I have a task to universal automatically predict sysupgrade (or factory) file name on the board, with already installed openwrt. The filename format is clear inside buildroot, but I can't find the way to learn CONFIG_TARGET_BOARD and CONFIG_TARGET_SUBTARGET variables values inside running system. I can pass them to my package, but it will not rebuilt when CONFIG_TARGET_SUBTARGET changed and will left invalid. I can clean it manually every time, but this way is unacceptable. Is there any common way to get that values or *sysupgrade.* filename from running system or make package rebuild each time? -- Yury Shvedov, WiMark Systems ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
