I just noticed that "git pull" shows no update since my last sync then I checked dev.openwrt.org and saw that there were no more commits since 12 may
I see all development moved to LEDE (last commit 38 min ago)...

Do you have any news about the future of Openwrt?

People are still submitting patches, but it's really hard to tell what is going on. I must admit that I am starting to make my builds from LEDE just because I can see some action.

What is the difference between these two projects?

Is the procedure of making images (with imagebuilder) and flashing the same?

There was no difference (LEDE claims to accept patches by git and not just patchwork emails), LEDE split/forked/rebooted from OpenWRT (political or personality clashes or whatever), but now the LEDE code seems to developing while OpenWRT seems to have become a little stale just recently. Otherwise building and flashing etc. were/are just the same.

(Last edited by Xotic750 on 23 May 2016, 13:46)

i have downloaded an unzipped a lede image builder tarball to compare it with an openwrt image builder tarball.  it appears there are more packages in openwrt tarball than the lede tarball.  anybody else has noticed the difference?

Changed build system, I think. I haven't checked imagebuilder itself as I compile from sources, but I know that LEDE changed the build system architecture to have more packages shared between platforms and just the non-shared packages are included in a platform's private set. E.g. all mips 34kc processors share the same package binaries (e.g. ar71xx/generic, ar71xx/nand, ar71xx-mikrotik etc.) and only the platform specific core things like kernel and firmware images are in "targets".
See e.g.
platform-specific: https://downloads.lede-project.org/snapshots/targets/
shared: https://downloads.lede-project.org/snapshots/packages/

e.g. for my ar71xx/generic I use
https://downloads.lede-project.org/snap … x/generic/
https://downloads.lede-project.org/snap … mips_34kc/
(both repos are listed in opkg config)

So, I guess that the difference you see is coming from more packages being downloaded from packages repos during the build.

wrtboy: I'm not sure if you're looking in the right place; LEDE splits out the regular packages (most userspace stuff) from a few core libraries and the kernel modules, the latter two ending up in their own directory. Maybe that works similarly in the image builder as well?

Either way, I have migrated all my deployments last night after a testing period and everything I needed was there, same as on OpenWrt. After all, LEDE still uses the OpenWrt package feeds. So I don't know which packages would be missing.

Edit: basically what hnyman said for the first part

(Last edited by Borromini on 23 May 2016, 14:52)

@hnyman and borromini, i have not been compiling from sources.  i have been using the openwrt kirkwood image builder tar ball simply to rebuild an image for an ea4500.  that's when i have observed the openwrt and lede tar balls being different.  e.g.  the lede tar ball doesn't even include luci-ssl so will generate an error even with a simple "make" command.

make image PROFILE=VIPER PACKAGES="luci-ssl luci-app-adblock"

EDIT:  sorry, i found out what caused the error--bad internet connection.

(Last edited by wrtboy on 24 May 2016, 00:53)

Well, I tested your command...
Downloaded the LEDE Kirkwood imagebuilder and uncompressed it.
Your example command works just nicely. No errors. Luci-ssl downloaded during the build. Firmware built normally.

perus@ub1604:/Openwrt/ib/LEDE-ImageBuilder-kirkwood.Linux-x86_64$ ls -l bin/targets/kirkwood/generic/
total 70592
-rw-rw-r-- 1 perus perus 6029312 touko 23 19:53 lede-kirkwood-dockstar-squashfs-factory.bin
-rw-rw-r-- 1 perus perus 4986880 touko 23 19:53 lede-kirkwood-dockstar-squashfs-sysupgrade.tar
-rw-rw-r-- 1 perus perus 6029312 touko 23 19:53 lede-kirkwood-goflexhome-squashfs-factory.bin
-rw-rw-r-- 1 perus perus 4986880 touko 23 19:53 lede-kirkwood-goflexhome-squashfs-sysupgrade.tar
-rw-rw-r-- 1 perus perus 6029312 touko 23 19:53 lede-kirkwood-goflexnet-squashfs-factory.bin
-rw-rw-r-- 1 perus perus 4986880 touko 23 19:53 lede-kirkwood-goflexnet-squashfs-sysupgrade.tar
-rw-rw-r-- 1 perus perus 5963776 touko 23 19:53 lede-kirkwood-linksys-audi-squashfs-factory.bin
-rw-rw-r-- 1 perus perus 4986880 touko 23 19:53 lede-kirkwood-linksys-audi-squashfs-sysupgrade.tar
-rw-rw-r-- 1 perus perus 6815744 touko 23 19:53 lede-kirkwood-linksys-viper-squashfs-factory.bin
-rw-rw-r-- 1 perus perus 4986880 touko 23 19:53 lede-kirkwood-linksys-viper-squashfs-sysupgrade.tar
-rw-rw-r-- 1 perus perus 4982784 touko 23 19:53 lede-kirkwood-viper-jffs2-nand-2048-128k.img
-rw-rw-r-- 1 perus perus 4007035 touko 23 19:53 lede-kirkwood-viper-rootfs.tar.gz
-rw-rw-r-- 1 perus perus 7471104 touko 23 19:53 lede-kirkwood-viper-squashfs.img
-rw-rw-r-- 1 perus perus    1078 touko 23 19:53 md5sums
-rw-rw-r-- 1 perus perus    1638 touko 23 19:53 sha256sums

perus@ub1604:/Openwrt/ib/LEDE-ImageBuilder-kirkwood.Linux-x86_64$ ls dl/luci*
dl/luci-app-adblock_git-16.135.27427-6415c04-1_all.ipk
dl/luci-app-firewall_git-16.135.27427-6415c04-1_all.ipk
dl/luci-base_git-16.135.27427-6415c04-1_arm_xscale.ipk
dl/luci_git-16.135.27427-6415c04-1_all.ipk
dl/luci-lib-ip_git-16.135.27427-6415c04-1_arm_xscale.ipk
dl/luci-lib-jsonc_git-16.135.27427-6415c04-1_arm_xscale.ipk
dl/luci-lib-nixio_git-16.135.27427-6415c04-1_arm_xscale.ipk
dl/luci-mod-admin-full_git-16.135.27427-6415c04-1_arm_xscale.ipk
dl/luci-proto-ipv6_git-16.135.27427-6415c04-1_all.ipk
dl/luci-proto-ppp_git-16.135.27427-6415c04-1_all.ipk
dl/luci-ssl_git-16.135.27427-6415c04-1_all.ipk
dl/luci-theme-bootstrap_git-16.135.27427-6415c04-1_all.ipk

(Last edited by hnyman on 23 May 2016, 18:02)

thanks hnyman.  with the openwrt kirkwood tar ball, there is no further need to download luci-ssl since the packages are already found in the openwrt image builder tar ball.  i think keeping all the packages with the downloaded build tar ball would ensure compatibility if there is a need to remake an image from the same extracted tar ball.

Anybody can confirm this project is dead ? I seen some openwrt's developer move to LEDE project.

I saw an email today from luka at openwrt.org making a proposal for some hosting changes, no indication that the project is dead. Just seems stagnant after the split.

is it dead now?

not dead at all

???
last from 05.02.2017 see: https://github.com/openwrt/openwrt/commits/master

What are the difference between LEDE and OpenWRT ?
Only that the name LEDE at my opinium are crap because if I search someting about LEDE inside the internet I find a lot of staff about LEDs but not LEDE.
And the OpenWRT forum is more ugly them the LEDE forum but better readeble (IMHO).