Nightly builds (NEW)

I know that, I don’t know why?

Because no one was using it.

It will be available in next nightly build.

Updated to CoreELEC-Amlogic.arm-9.2-nightly_20210104, hanging on the logo.

Yes, seems CoreELEC-Amlogic.arm-9.2-nightly_20210104 is bad and doesn’t boot :frowning:

Yes, the nightly got removed to prevent update to 20200104.

For those who already updated please download last working nightly:

Replace on your CE boot media the files kernel.img with KERNEL and SYSTEM with SYSTEM from the tar located in the subfolder target. Please rename KERNEL to kernel.img again. CE should boot normally again without any loss of data.
The copy of the md5 files is not necessary.

I did it right away.

Still see 20200104 build:

And my box still informs about new update. Fortunatelly i changed to manual update.

You only see the ng and those are fine.

Thank You.
And sorry for mess.

1 Like

As I understand the difference between the builds from “20210103” and “20210105” does not exist?


CoreELEC nightly 2021/01/06 successfully updating and booting from:

  • TaNix TX5 Deluxe Edition (905X3)
  • Turewell F2 A95X (S905X2)
  • TaNix TX3 MAX (S905W)
  • NexBox A95X-B7N (S905X)
1 Like

Are scripts behind available somewhere, git repo maybe? Or build logs for entire process?

I’m for example interested in which commands are used to build odroid n2 armlogic-ng images.

@arek it’s basically the following wrapped in some checks to see if there has been an update, and to generate the changelog and add it to the img.

git clone
cd CoreELEC
PROJECT=Amlogic-ng ARCH=arm make image

And other targets?

Would be nice if build logs, including commands, ended up also on relkai.

If you want to build for the devices supported by the Amlogic builds then it’s the same except you change PROJECT=Amlogic-ng to PROJECT=Amlogic

Is there a particular reason you want the build logs?

Ok, thanks.

buildlogs - to compare my build logs (and I have build errors) with “working” (as building fine) nightly builds

Maybe if you open a new thread about the build problems you are having then somebody might be able to help figure out the problem you are having.

I’ll figure on my own (and if not then I’ll do that).

Just saying that logs make sense for other people, too.
Look at how linux distros are doing that,,

How to enable verbose build and disable parallel build?

So far was playing with these options but all didn’t work:
PKG_BUILD_FLAGS="+verbose -parallel" PROJECT=Amlogic-ng ARCH=arm make image
MAKEFLAGS=“V=1 VERBOSE=1” PROJECT=Amlogic-ng ARCH=arm make -j1 image


And even with parallel build you get log for each package in folder build.CoreELEC*/.threads/logs.