Buildroot fork.
 
 
 
 
 
 
Go to file
Adam Duskett a610bf9967 package/openjdk{-bin}: bump version to 17.0.1+12
OpenJDK 17 is a new LTS release, which leaves the Buildroot Config option of
"LTS" and "LATEST" as a misnomer because both 11 and 17 are LTS releases.

There are two options in this case:

1) Remove "LATEST" and update OpenJDK 11 to 17, and only support 17.
2) Change "LTS" to "11" and "LATEST" to "17" and only support the latest 2 LTS
OpenJDK releases.

After some discussion with Thomas Petazzoni and Peter Korsgaard, and testing,
option 2 is the best course of action for a few reasons:

  - OpenJDK 11 and 17 have very long support cycles:
  - OpenJDK 11 has two years of Active and five years of security support left.
  - OpenJDK 17 has five years of Active and ten years of security support left.
  - Both OpenJDK versions build with the same parameters.
  - The maintenance cost of both versions is meager.
  - Both versions pass tests.package.test_openjdk without issue.

Changes:
  - Change BR2_OPENJDK_VERSION_LATEST -> BR2_OPENJDK_VERSION_17
  - Change BR2_OPENJDK_VERSION_LTS -> BR2_OPENJDK_VERSION_11
Signed-off-by: Adam Duskett <aduskett@gmail.com>
[Peter: add Config.in.legacy, use BR2_PACKAGE_OPENJDK_ prefix]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-11-05 15:48:11 +01:00
arch arch/config: Make RISC-V 64-bits MMU optional 2021-10-27 14:39:01 +02:00
board configs/qemu_ppc_g3beige: update to Linux 5.15 2021-11-03 18:43:12 +01:00
boot boot/optee-os: bump to version 3.15.0 2021-10-27 22:28:03 +02:00
configs configs/raspberrypi: bump kernel to 581049d (5.10.76) 2021-11-03 23:39:18 +01:00
docs docs/manual/contribute.txt: rewrite the section dedicated to runtime tests 2021-10-27 21:44:51 +02:00
fs fs/ext2: fir (again) namespace for variables 2021-10-13 18:01:34 +02:00
linux {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.{4, 10, 14}.x series 2021-11-03 22:56:44 +01:00
package package/openjdk{-bin}: bump version to 17.0.1+12 2021-11-05 15:48:11 +01:00
support support/testing: fix the TestPythonPy[2,3]Incremental test cases 2021-10-31 18:42:55 +01:00
system system: support br2-external init systems 2020-10-14 22:48:42 +02:00
toolchain {linux, linux-headers}: add version 5.15 2021-11-03 22:12:36 +01:00
utils utils/getdeveloperlib.py: call Developer.hasfile() with relative path 2021-11-02 23:20:11 +01:00
.defconfig arch: remove support for sh64 2016-09-08 22:15:15 +02:00
.flake8 Revert ".flake8: fix check for 80/132 columns" 2021-01-02 17:38:20 +01:00
.gitignore update gitignore 2013-05-04 12:41:55 +02:00
.gitlab-ci.yml .gitlab-ci.yml: use the Docker image from gitlab registry 2021-10-24 16:12:43 +02:00
CHANGES Update for 2021.02.6 2021-10-12 08:15:00 +02:00
COPYING COPYING: add exception about patch licensing 2016-02-26 19:50:13 +01:00
Config.in Config.in: disable Fortify Source for microblaze 2021-08-23 23:08:05 +02:00
Config.in.legacy package/openjdk{-bin}: bump version to 17.0.1+12 2021-11-05 15:48:11 +01:00
DEVELOPERS DEVELOPERS: drop Mirza Krak 2021-11-04 13:32:26 +01:00
Makefile Revert "make: support: use `command -v' instead of `which'" 2021-10-01 20:09:58 +02:00
Makefile.legacy Remove BR2_DEPRECATED 2016-10-15 23:14:45 +02:00
README docs: move the IRC channel away from Freenode 2021-05-29 22:16:23 +02:00

README

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches