Go to file
Frank Vanbever c5b5892b6d support/cmake: Explicitly set CMAKE_SYSTEM
Some packages test for CMAKE_SYSTEM explicitly[1]

CMAKE_SYSTEM is comprised of CMAKE_SYSTEM_NAME and CMAKE_SYSTEM_VERSION.
It defaults to CMAKE_SYSTEM_NAME if CMAKE_SYSTEM_VERSION is not set[2]

At the point CMAKE_SYSTEM_NAME is set to "Linux" CMAKE_SYSTEM is already
constructed. Setting it explicitly ensures that it is the correct value.

This is because we do set CMAKE_SYSTEM_NAME twice, in fact:

  - first in toolchainfile.cmake, so that we tell cmake to use the
    "Buildroot" platform,

  - second, in the Buildroot.cmake platform definition itself, so that
    we eventually behave like the Linux platform.

We also set CMAKE_SYSTEM_VERSION to 1, and so the real CMAKE_SYSTEM
value should be set to Linux-1 if we were to follow the documentation to
the letter.

However, for Linux, the version does not matter, and in some situations
may even be harmful (that was reported in one of the commits that
introduce Buildroot.cmake and toolchainfile.cmake).

[1] Fluidsynth 0cd44d00e1/CMakeLists.txt (L80)
[2] https://cmake.org/cmake/help/git-master/variable/CMAKE_SYSTEM.html#variable:CMAKE_SYSTEM

Signed-off-by: Frank Vanbever <frank.vanbever@mind.be>
Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
[Peter: update commit message with description from Yann]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

(cherry picked from commit 07f31ee263)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-30 22:35:08 +02:00
arch arch: Add support for Westmere targets 2019-06-23 23:08:56 +02:00
board board/qemu: ensure root is available before mounting it 2019-07-06 22:22:53 +02:00
boot boot/arm-trusted-firmware: licensing info is only valid for v1.4 2019-08-04 19:24:05 +02:00
configs configs/bananapi_m64: uboot needs host pylibfdt to build 2019-05-13 20:16:53 +02:00
docs docs/manual: 'Fixes' tag needs a colon 2019-07-31 23:42:48 +02:00
fs fs/common.mk: do not store original names and timestamps when creating gzipped rootfs 2019-08-04 19:10:46 +02:00
linux {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.{1, 2}.x series 2019-08-20 15:52:32 +02:00
package package/busybox/udhcpc.script: fix domain search comment 2019-08-30 22:33:01 +02:00
support support/cmake: Explicitly set CMAKE_SYSTEM 2019-08-30 22:35:08 +02:00
system system/skeleton: remove password expiration from shadow 2019-03-20 23:06:29 +01:00
toolchain toolchain/toolchain-external/toolchain-external-andes-nds32: add missing dependencies/select 2019-05-31 00:06:52 +02:00
utils utils/check-package: Add a quiet flag 2019-07-07 08:42:01 +02:00
.defconfig
.flake8 .flake8: fix check for 80/132 columns 2019-04-10 12:31:33 +02:00
.gitignore
.gitlab-ci.yml support/testing/tests: drop Python 2.x test in test_ipython 2019-05-18 22:41:22 +02:00
.gitlab-ci.yml.in .gitlab-ci.yml: add trigger per job 2019-05-01 15:42:45 +02:00
CHANGES Update for 2019.05.1 2019-07-07 22:09:08 +02:00
Config.in toolchain: set the ssp gcc option in kconfig 2019-03-13 00:01:55 +01:00
Config.in.legacy Config.in.legacy: add legacy entry for 4.20.x headers 2019-06-24 20:56:32 +02:00
COPYING
DEVELOPERS DEVELOPERS: Remove Markos Chandras 2019-06-24 22:07:44 +02:00
Makefile Makefile: don't export GZIP environment variable 2019-08-04 19:10:53 +02:00
Makefile.legacy
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 Freenode IRC.

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