Can you provide a more detailed log output?
What does make -j1 V=s prints...?
Will try tonight after cloning my working build directory to a new folder.
make[4]: Entering directory '/home/test/B/openwrt/build_dir/target-mips_24kc_musl/oui-ui-core-2019-10-02-ff73aac'
make[4]: /home/test/B/openwrt/staging_dir/host/bin/node: Command not found
node:
make[4]: /home/test/B/openwrt/staging_dir/host/bin/npm: Command not found
npm:
make[4]: /home/test/B/openwrt/staging_dir/host/bin/node: Command not found
Makefile:12: *** "Node required at least v8.16, current not installed". Stop.
make[4]: Leaving directory '/home/test/B/openwrt/build_dir/target-mips_24kc_musl/oui-ui-core-2019-10-02-ff73aac'
Makefile:76: recipe for target '/home/test/B/openwrt/build_dir/target-mips_24kc_musl/oui-ui-core-2019-10-02-ff73aac/.built' failed
make[3]: *** [/home/test/B/openwrt/build_dir/target-mips_24kc_musl/oui-ui-core-2019-10-02-ff73aac/.built] Error 2
make[3]: Leaving directory '/home/test/B/openwrt/feeds/oui/oui-ui-core'
time: package/feeds/oui/oui-ui-core/compile#0.05#0.01#0.17
package/Makefile:111: recipe for target 'package/feeds/oui/oui-ui-core/compile' failed
make[2]: *** [package/feeds/oui/oui-ui-core/compile] Error 2
make[2]: Leaving directory '/home/test/B/openwrt'
package/Makefile:107: recipe for target '/home/test/B/openwrt/staging_dir/target-mips_24kc_musl/stamp/.package_compile' failed
make[1]: *** [/home/test/B/openwrt/staging_dir/target-mips_24kc_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/test/B/openwrt'
/home/test/B/openwrt/include/toplevel.mk:225 : la recette pour la cible « world » a échouée
make: *** [world] Erreur 2
NodeJS missing in the build environment by the looks of it.
1 Like
Right in the end it compiled for me. However unless your using a WRT3200 or WRT32X with firmware compiled for neon-vfpv3 there is no point in sharing the ipk's
i have add node.js in my debian
but i have not found parameters in Menuconfig -> Language -> Node.js ???
found ??? i think node.js is not supported for ramips
parameters exist but for anothers Target System as for Allwinner A1x/A20/Axx/R40 or BroadCom27xx ...
After a period of development, the current Oui is a brand new Oui.
Oui --->
Applications --->
<*> oui-app-admin............................................. Administration
<*> oui-app-diagnostics.......................................... Diagnostics
<*> oui-app-firewall................................................ Firewall
<*> oui-app-home.......................................... Built-in home page
<*> oui-app-interfaces.................................... Network Interfaces
<*> oui-app-system............................................ System Setting
<*> oui-app-upgrade......................................... Backup / Upgrade
<*> oui-app-wireless................................................ Wireless
-*- oui-bwm........................................ Bandwidth Monitor for oui
-*- oui-httpd................................................ Oui rpc backend
-*- oui-ui-core.................................................. Oui ui core
2 Likes
How big are the dependencies. Particularly when compared to current LUCI?
Only depends libubox-lua libuci-lua libubus-lua libev libuhttpd jansson liblua5.1.
1 Like
What about the JS frameworks?
vue.
antd-vue
Have you measured a size comparison at all? Trying to understand if this is viable for regular routers or whether it will just be a toy.
1 Like
It's already used in commercial products.
Amazing work so far.
Do you plan to add your packages to a official package repo?
I think this would give more users the possibility to test, report bugs and probably create PRs for further improvements.
Yes.... but what is the size compared to LUCI?
1 Like
Hi! Kind of a newbie here. I have installed OWRT 19.07.4. If I try this new interface, will I have all my menu links as I have with LUCI? I mean like the screenshot
The size is quite good. For comparison with luci you have to sum up the sizes by yourself.
johann@johann-pc:~/dev/openwrt/openwrt$ du -sh bin/packages/mips_24kc/oui/oui-*.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-active-routes_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-admin_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-cron_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-dhcp_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-diagnostics_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-dmesg_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-example_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-firewall_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-home_git-2020.284.10683-e95e3a7-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-hosts_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
20K bin/packages/mips_24kc/oui/oui-app-interfaces_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-leds_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-login_git-2020.283.56028-e7bc21e-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-processes_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-routes_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-rtty_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-ssh_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
8,0K bin/packages/mips_24kc/oui/oui-app-syslog_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
16K bin/packages/mips_24kc/oui/oui-app-system_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-upgrade_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
12K bin/packages/mips_24kc/oui/oui-app-wireless_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
4,0K bin/packages/mips_24kc/oui/oui-bwm_git-2020.279.29375-5a688ed-1_mips_24kc.ipk
20K bin/packages/mips_24kc/oui/oui-httpd_git-2020.284.46790-5f13c99-1_mips_24kc.ipk
692K bin/packages/mips_24kc/oui/oui-ui-core_git-2020.284.09961-c81f502-1_mips_24kc.ipk
I have made the file and I installed it on my router but I can not find the theme as you gave
Dear @zhaojh329
the new web interface you have developed looks very promising! 
I am looking forward to see more of this because it is a huge step forward compared to the actual state of LuCi.
The main thing what LuCi is missing is "User Experience" (UX) optimization. Therefore OpenWRT feels like software which was developed 20 years ago.
I would love to see a restructuring of the data in the menu ... and on the pages which are being displayed.
The web interface should be set up in a way that relevant information is shown on the main page and also relevant functionalities should be easily accessible.
Today the starting page shows informations like "Firmware-Version, Kernel-Version, Architecture, ....".
All those things are "stats for nerds" - but for normal usage of no use.
From UX point of view you could use this area for more important features like displaying the clients ... so that the user can see who is connected (... and e. g. to decide whom to block). Similar to how it is realized in Padavan, or OpenWRT, or any other UX optimized web interface.
The "stats for nerds" can be put in the last menu section under "Information", "About", or whatever you want to call it 
But nevertheless thanks for working hard on making an excellent product much better!
I have not understood, should i make my own build to see the interface? 