2013-09-05 01:12:15 -06:00
|
|
|
# Makefile for buildroot
|
2001-12-21 17:56:11 -07:00
|
|
|
#
|
2005-02-07 15:19:26 -07:00
|
|
|
# Copyright (C) 1999-2005 by Erik Andersen <andersen@codepoet.org>
|
2014-01-08 09:12:04 -07:00
|
|
|
# Copyright (C) 2006-2014 by the Buildroot developers <buildroot@uclibc.org>
|
2017-01-27 05:26:32 -07:00
|
|
|
# Copyright (C) 2014-2017 by the Buildroot developers <buildroot@buildroot.org>
|
2001-12-21 17:56:11 -07:00
|
|
|
#
|
2002-04-26 05:45:55 -06:00
|
|
|
# This program is free software; you can redistribute it and/or modify
|
2004-10-08 19:06:03 -06:00
|
|
|
# it under the terms of the GNU General Public License as published by
|
|
|
|
# the Free Software Foundation; either version 2 of the License, or
|
|
|
|
# (at your option) any later version.
|
2001-12-21 17:56:11 -07:00
|
|
|
#
|
2004-10-08 19:06:03 -06:00
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
2002-04-26 05:45:55 -06:00
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
2004-10-08 19:06:03 -06:00
|
|
|
# General Public License for more details.
|
2009-01-26 12:42:47 -07:00
|
|
|
#
|
2004-10-08 19:06:03 -06:00
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program; if not, write to the Free Software
|
|
|
|
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
2004-09-02 18:49:43 -06:00
|
|
|
#
|
2003-10-18 05:09:54 -06:00
|
|
|
|
2004-10-08 19:06:03 -06:00
|
|
|
#--------------------------------------------------------------
|
|
|
|
# Just run 'make menuconfig', configure stuff, then run 'make'.
|
|
|
|
# You shouldn't need to mess with anything beyond this point...
|
|
|
|
#--------------------------------------------------------------
|
2010-10-31 10:35:09 -06:00
|
|
|
|
2016-11-05 15:05:08 -06:00
|
|
|
# Delete default rules. We don't use them. This saves a bit of time.
|
|
|
|
.SUFFIXES:
|
|
|
|
|
2016-06-18 22:12:06 -06:00
|
|
|
# we want bash as shell
|
|
|
|
SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
|
|
|
|
else if [ -x /bin/bash ]; then echo /bin/bash; \
|
|
|
|
else echo sh; fi; fi)
|
|
|
|
|
2016-10-17 15:05:42 -06:00
|
|
|
# Set O variable if not already done on the command line;
|
|
|
|
# or avoid confusing packages that can use the O=<dir> syntax for out-of-tree
|
|
|
|
# build by preventing it from being forwarded to sub-make calls.
|
|
|
|
ifneq ("$(origin O)", "command line")
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
O := $(CURDIR)/output
|
2016-10-17 15:05:42 -06:00
|
|
|
endif
|
|
|
|
|
|
|
|
# Check if the current Buildroot execution meets all the pre-requisites.
|
|
|
|
# If they are not met, Buildroot will actually do its job in a sub-make meeting
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
# its pre-requisites, which are:
|
2016-10-17 15:05:42 -06:00
|
|
|
# 1- Permissive enough umask:
|
|
|
|
# Wrong or too restrictive umask will prevent Buildroot and packages from
|
|
|
|
# creating files and directories.
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
# 2- Absolute canonical CWD (i.e. $(CURDIR)):
|
|
|
|
# Otherwise, some packages will use CWD as-is, others will compute its
|
|
|
|
# absolute canonical path. This makes harder tracking and fixing host
|
|
|
|
# machine path leaks.
|
|
|
|
# 3- Absolute canonical output location (i.e. $(O)):
|
|
|
|
# For the same reason as the one for CWD.
|
|
|
|
|
|
|
|
# Remove the trailing '/.' from $(O) as it can be added by the makefile wrapper
|
|
|
|
# installed in the $(O) directory.
|
|
|
|
# Also remove the trailing '/' the user can set when on the command line.
|
|
|
|
override O := $(patsubst %/,%,$(patsubst %.,%,$(O)))
|
|
|
|
# Make sure $(O) actually exists before calling realpath on it; this is to
|
|
|
|
# avoid empty CANONICAL_O in case on non-existing entry.
|
|
|
|
CANONICAL_O := $(shell mkdir -p $(O) >/dev/null 2>&1)$(realpath $(O))
|
|
|
|
|
|
|
|
CANONICAL_CURDIR = $(realpath $(CURDIR))
|
2016-10-17 15:05:42 -06:00
|
|
|
|
|
|
|
REQ_UMASK = 0022
|
|
|
|
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
# Make sure O= is passed (with its absolute canonical path) everywhere the
|
|
|
|
# toplevel makefile is called back.
|
|
|
|
EXTRAMAKEARGS := O=$(CANONICAL_O)
|
2016-10-17 15:05:42 -06:00
|
|
|
|
|
|
|
# Check Buildroot execution pre-requisites here.
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
ifneq ($(shell umask):$(CURDIR):$(O),$(REQ_UMASK):$(CANONICAL_CURDIR):$(CANONICAL_O))
|
2015-07-16 16:33:07 -06:00
|
|
|
.PHONY: _all $(MAKECMDGOALS)
|
2014-11-21 09:19:00 -07:00
|
|
|
|
2015-07-16 16:33:07 -06:00
|
|
|
$(MAKECMDGOALS): _all
|
|
|
|
@:
|
2014-11-21 09:19:00 -07:00
|
|
|
|
2015-07-16 16:33:07 -06:00
|
|
|
_all:
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
@umask $(REQ_UMASK) && \
|
|
|
|
$(MAKE) -C $(CANONICAL_CURDIR) --no-print-directory \
|
|
|
|
$(MAKECMDGOALS) $(EXTRAMAKEARGS)
|
2014-11-21 09:19:00 -07:00
|
|
|
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
else # umask / $(CURDIR) / $(O)
|
2014-11-21 09:19:00 -07:00
|
|
|
|
2014-10-11 11:34:42 -06:00
|
|
|
# This is our default rule, so must come first
|
|
|
|
all:
|
|
|
|
|
2010-10-31 10:35:10 -06:00
|
|
|
# Set and export the version string
|
2016-12-01 14:13:19 -07:00
|
|
|
export BR2_VERSION := 2017.02-git
|
2016-11-23 05:58:40 -07:00
|
|
|
# Actual time the release is cut (for reproducible builds)
|
|
|
|
BR2_VERSION_EPOCH = 1478206447
|
2010-10-31 10:35:10 -06:00
|
|
|
|
2015-07-14 15:30:39 -06:00
|
|
|
# Save running make version since it's clobbered by the make package
|
|
|
|
RUNNING_MAKE_VERSION := $(MAKE_VERSION)
|
|
|
|
|
2012-02-08 09:22:17 -07:00
|
|
|
# Check for minimal make version (note: this check will break at make 10.x)
|
2014-04-23 02:39:23 -06:00
|
|
|
MIN_MAKE_VERSION = 3.81
|
2015-07-14 15:30:39 -06:00
|
|
|
ifneq ($(firstword $(sort $(RUNNING_MAKE_VERSION) $(MIN_MAKE_VERSION))),$(MIN_MAKE_VERSION))
|
|
|
|
$(error You have make '$(RUNNING_MAKE_VERSION)' installed. GNU make >= $(MIN_MAKE_VERSION) is required)
|
2012-02-08 09:22:17 -07:00
|
|
|
endif
|
|
|
|
|
2014-02-14 02:55:08 -07:00
|
|
|
# Parallel execution of this Makefile is disabled because it changes
|
|
|
|
# the packages building order, that can be a problem for two reasons:
|
|
|
|
# - If a package has an unspecified optional dependency and that
|
|
|
|
# dependency is present when the package is built, it is used,
|
|
|
|
# otherwise it isn't (but compilation happily proceeds) so the end
|
|
|
|
# result will differ if the order is swapped due to parallel
|
|
|
|
# building.
|
|
|
|
# - Also changing the building order can be a problem if two packages
|
|
|
|
# manipulate the same file in the target directory.
|
|
|
|
#
|
|
|
|
# Taking into account the above considerations, if you still want to execute
|
|
|
|
# this top-level Makefile in parallel comment the ".NOTPARALLEL" line and
|
2015-07-01 02:10:46 -06:00
|
|
|
# use the -j<jobs> option when building, e.g:
|
|
|
|
# make -j$((`getconf _NPROCESSORS_ONLN`+1))
|
2010-10-31 10:35:09 -06:00
|
|
|
.NOTPARALLEL:
|
|
|
|
|
2009-11-30 09:29:01 -07:00
|
|
|
# absolute path
|
2016-03-09 15:58:43 -07:00
|
|
|
TOPDIR := $(CURDIR)
|
2014-04-23 02:39:23 -06:00
|
|
|
CONFIG_CONFIG_IN = Config.in
|
|
|
|
CONFIG = support/kconfig
|
|
|
|
DATE := $(shell date +%Y%m%d)
|
2003-09-26 15:18:46 -06:00
|
|
|
|
2010-10-31 10:35:12 -06:00
|
|
|
# Compute the full local version string so packages can use it as-is
|
|
|
|
# Need to export it, so it can be got from environment in children (eg. mconf)
|
2014-04-23 02:39:23 -06:00
|
|
|
export BR2_VERSION_FULL := $(BR2_VERSION)$(shell $(TOPDIR)/support/scripts/setlocalversion)
|
2010-10-31 10:35:12 -06:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
noconfig_targets := menuconfig nconfig gconfig xconfig config oldconfig randconfig \
|
2013-12-26 16:04:29 -07:00
|
|
|
defconfig %_defconfig allyesconfig allnoconfig silentoldconfig release \
|
2009-10-04 13:57:12 -06:00
|
|
|
randpackageconfig allyespackageconfig allnopackageconfig \
|
2016-11-15 04:03:20 -07:00
|
|
|
print-version olddefconfig distclean manual manual-html manual-split-html \
|
|
|
|
manual-pdf manual-text manual-epub
|
2006-12-02 12:01:10 -07:00
|
|
|
|
2015-04-26 03:51:14 -06:00
|
|
|
# Some global targets do not trigger a build, but are used to collect
|
|
|
|
# metadata, or do various checks. When such targets are triggered,
|
|
|
|
# some packages should not do their configuration sanity
|
|
|
|
# checks. Provide them a BR_BUILDING variable set to 'y' when we're
|
|
|
|
# actually building and they should do their sanity checks.
|
|
|
|
#
|
|
|
|
# We're building in two situations: when MAKECMDGOALS is empty
|
|
|
|
# (default target is to build), or when MAKECMDGOALS contains
|
|
|
|
# something else than one of the nobuild_targets.
|
2016-11-15 04:03:20 -07:00
|
|
|
nobuild_targets := source %-source source-check \
|
|
|
|
legal-info %-legal-info external-deps _external-deps \
|
|
|
|
clean distclean help show-targets graph-depends \
|
|
|
|
%-graph-depends %-show-depends %-show-version \
|
|
|
|
graph-build graph-size list-defconfigs \
|
|
|
|
savedefconfig printvars
|
2015-04-26 03:51:14 -06:00
|
|
|
ifeq ($(MAKECMDGOALS),)
|
|
|
|
BR_BUILDING = y
|
|
|
|
else ifneq ($(filter-out $(nobuild_targets),$(MAKECMDGOALS)),)
|
|
|
|
BR_BUILDING = y
|
|
|
|
endif
|
|
|
|
|
2016-11-02 19:55:16 -06:00
|
|
|
# We call make recursively to build packages. The command-line overrides that
|
|
|
|
# are passed to Buildroot don't apply to those package build systems. In
|
|
|
|
# particular, we don't want to pass down the O=<dir> option for out-of-tree
|
|
|
|
# builds, because the value specified on the command line will not be correct
|
|
|
|
# for packages.
|
|
|
|
MAKEOVERRIDES :=
|
|
|
|
|
2016-07-17 04:34:21 -06:00
|
|
|
# Include some helper macros and variables
|
|
|
|
include support/misc/utils.mk
|
2009-01-25 13:19:01 -07:00
|
|
|
|
2016-10-17 15:05:41 -06:00
|
|
|
# Set variables related to in-tree or out-of-tree build.
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
# Here, both $(O) and $(CURDIR) are absolute canonical paths.
|
|
|
|
ifeq ($(O),$(CURDIR)/output)
|
|
|
|
CONFIG_DIR := $(CURDIR)
|
2016-10-17 15:05:41 -06:00
|
|
|
NEED_WRAPPER =
|
|
|
|
else
|
|
|
|
CONFIG_DIR := $(O)
|
2014-04-23 02:39:23 -06:00
|
|
|
NEED_WRAPPER = y
|
2010-01-11 05:28:50 -07:00
|
|
|
endif
|
|
|
|
|
2013-10-02 14:06:40 -06:00
|
|
|
# bash prints the name of the directory on 'cd <dir>' if CDPATH is
|
|
|
|
# set, so unset it here to not cause problems. Notice that the export
|
2016-11-22 19:31:31 -07:00
|
|
|
# line doesn't affect the environment of $(shell ..) calls.
|
2014-04-23 02:39:23 -06:00
|
|
|
export CDPATH :=
|
2016-11-22 19:31:31 -07:00
|
|
|
|
|
|
|
BASE_DIR := $(CANONICAL_O)
|
2013-10-02 14:06:40 -06:00
|
|
|
$(if $(BASE_DIR),, $(error output directory "$(O)" does not exist))
|
|
|
|
|
core: introduce the BR2_EXTERNAL variable
This commit introduces the BR2_EXTERNAL environment variable, which
will allow to keep Buildroot customization (board-specific
configuration files or root filesystem overlays, package Config.in and
makefiles, as well as defconfigs) outside of the Buildroot tree.
This commit only introduces the variable itself, and ensures that it
is available within Config.in options. This allows us to use
$BR2_EXTERNAL in a 'source' statement in Config.in.
Following patches extend the usage of BR2_EXTERNAL to other areas
(packages and defconfigs).
In details, this commit:
* Introduces the BR2_EXTERNAL Kconfig option. This option has no
prompt, and is therefore not visible to the user and also not
stored in the .config file. It is automatically set to the value of
the BR2_EXTERNAL environment variable. The only purpose of this
BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
properly expanded when used inside Kconfig source statements.
* Calculates the BR2_EXTERNAL value to use. If passed on the command
line, then this value is taken in priority, and saved to a
.br-external hidden file in the output directory. If not passed on
the command line, then we read the .br-external file from the
output directory. This allows the user to not pass the BR2_EXTERNAL
value at each make invocation. If no BR2_EXTERNAL value is passed,
we define it to support/dummy-external, so that the kconfig code
finds an existing $(BR2_EXTERNAL)/package/Config.in file to
include.
* Passes the BR2_EXTERNAL into the *config environment, so that its
value is found when parsing/evaluating Config.in files and .config
values.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
Tested-by: "Samuel Martin" <s.martin49@gmail.com>
Acked-by: "Samuel Martin" <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-12-05 12:11:10 -07:00
|
|
|
|
|
|
|
# Handling of BR2_EXTERNAL.
|
|
|
|
#
|
|
|
|
# The value of BR2_EXTERNAL is stored in .br-external in the output directory.
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
# The location of the external.mk makefile fragments is computed in that file.
|
core: offload handling of BR2_EXTERNAL into the script
Currently, we treat the case where we have no br2-external tree
(BR2_EXTERNAL is empty) differently from the case where we do have one
(BR2_EXTERNAL is not empty).
There is now no reason to treat those two cases differently:
- the kconfig snippet is always generated appropriately (i.e. it would
include the br2-external tree if set, or include nothing otherwise);
- we no longer have a dummy br-external tree either.
Also, the Makefile code to handle BR2_EXTERNAL is currently quite
readable if at least a little bit tricky.
However, when we're going to add support for using multiple br2-external
trees simultaneously, this code would need to get much, much more complex.
To keep the Makefile (rather) simple, offload all of the handling of
BR2_EXTERNAL to the recently added br2-external helper script.
However, because of Makefiles idiosyncracies, we can't use a rule to
generate that Makefile fragment.
Instead, we use $(shell ...) to call the helper script, and include the
fragment twice: once before the $(shell ...) so we can grab a previously
defined BR2_EXTERNAL value, a second time to use the one passed on the
command line, if any.
Furthermore, we can't error out (e.g. on non-existent br2-external tree)
directly from the fragment or we'd get that error on subsequent calls,
with no chance to override it even from command line.
Instead, we use a variable in which we store the error, set it to empty
before the second inclusion, so that only the one newly generated, if
any, is taken into account.
Since we know the script will always be called from Makefile context
first, we know validation will occur in Makefile context first. So we
can assume that, if there is an error, it will be detected in Makefile
context. Consequently, if the script is called to generate the kconfig
fragment, validation has already occured, and there should be no error.
So we change the error function to generate Makefile code, so that
errors are caught as explained above.
Lastly, when the value of BR2_EXTERNAL changes, we want to 'forget'
about the previous value of the BR2_EXTERNAL_MK variable, especially in
the case where BR2_EXTERNAL is now set to empty, so that we do not try
to include it later. That's why we first generate empty version of
BR2_EXTERNAL_MK, and then assign it the new value, if any.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:15 -06:00
|
|
|
# On subsequent invocations of make, this file is read in. BR2_EXTERNAL can
|
|
|
|
# still be overridden on the command line, therefore the file is re-created
|
|
|
|
# every time make is run.
|
core: introduce the BR2_EXTERNAL variable
This commit introduces the BR2_EXTERNAL environment variable, which
will allow to keep Buildroot customization (board-specific
configuration files or root filesystem overlays, package Config.in and
makefiles, as well as defconfigs) outside of the Buildroot tree.
This commit only introduces the variable itself, and ensures that it
is available within Config.in options. This allows us to use
$BR2_EXTERNAL in a 'source' statement in Config.in.
Following patches extend the usage of BR2_EXTERNAL to other areas
(packages and defconfigs).
In details, this commit:
* Introduces the BR2_EXTERNAL Kconfig option. This option has no
prompt, and is therefore not visible to the user and also not
stored in the .config file. It is automatically set to the value of
the BR2_EXTERNAL environment variable. The only purpose of this
BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
properly expanded when used inside Kconfig source statements.
* Calculates the BR2_EXTERNAL value to use. If passed on the command
line, then this value is taken in priority, and saved to a
.br-external hidden file in the output directory. If not passed on
the command line, then we read the .br-external file from the
output directory. This allows the user to not pass the BR2_EXTERNAL
value at each make invocation. If no BR2_EXTERNAL value is passed,
we define it to support/dummy-external, so that the kconfig code
finds an existing $(BR2_EXTERNAL)/package/Config.in file to
include.
* Passes the BR2_EXTERNAL into the *config environment, so that its
value is found when parsing/evaluating Config.in files and .config
values.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
Tested-by: "Samuel Martin" <s.martin49@gmail.com>
Acked-by: "Samuel Martin" <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-12-05 12:11:10 -07:00
|
|
|
|
core: offload handling of BR2_EXTERNAL into the script
Currently, we treat the case where we have no br2-external tree
(BR2_EXTERNAL is empty) differently from the case where we do have one
(BR2_EXTERNAL is not empty).
There is now no reason to treat those two cases differently:
- the kconfig snippet is always generated appropriately (i.e. it would
include the br2-external tree if set, or include nothing otherwise);
- we no longer have a dummy br-external tree either.
Also, the Makefile code to handle BR2_EXTERNAL is currently quite
readable if at least a little bit tricky.
However, when we're going to add support for using multiple br2-external
trees simultaneously, this code would need to get much, much more complex.
To keep the Makefile (rather) simple, offload all of the handling of
BR2_EXTERNAL to the recently added br2-external helper script.
However, because of Makefiles idiosyncracies, we can't use a rule to
generate that Makefile fragment.
Instead, we use $(shell ...) to call the helper script, and include the
fragment twice: once before the $(shell ...) so we can grab a previously
defined BR2_EXTERNAL value, a second time to use the one passed on the
command line, if any.
Furthermore, we can't error out (e.g. on non-existent br2-external tree)
directly from the fragment or we'd get that error on subsequent calls,
with no chance to override it even from command line.
Instead, we use a variable in which we store the error, set it to empty
before the second inclusion, so that only the one newly generated, if
any, is taken into account.
Since we know the script will always be called from Makefile context
first, we know validation will occur in Makefile context first. So we
can assume that, if there is an error, it will be detected in Makefile
context. Consequently, if the script is called to generate the kconfig
fragment, validation has already occured, and there should be no error.
So we change the error function to generate Makefile code, so that
errors are caught as explained above.
Lastly, when the value of BR2_EXTERNAL changes, we want to 'forget'
about the previous value of the BR2_EXTERNAL_MK variable, especially in
the case where BR2_EXTERNAL is now set to empty, so that we do not try
to include it later. That's why we first generate empty version of
BR2_EXTERNAL_MK, and then assign it the new value, if any.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:15 -06:00
|
|
|
BR2_EXTERNAL_FILE = $(BASE_DIR)/.br-external.mk
|
core: introduce the BR2_EXTERNAL variable
This commit introduces the BR2_EXTERNAL environment variable, which
will allow to keep Buildroot customization (board-specific
configuration files or root filesystem overlays, package Config.in and
makefiles, as well as defconfigs) outside of the Buildroot tree.
This commit only introduces the variable itself, and ensures that it
is available within Config.in options. This allows us to use
$BR2_EXTERNAL in a 'source' statement in Config.in.
Following patches extend the usage of BR2_EXTERNAL to other areas
(packages and defconfigs).
In details, this commit:
* Introduces the BR2_EXTERNAL Kconfig option. This option has no
prompt, and is therefore not visible to the user and also not
stored in the .config file. It is automatically set to the value of
the BR2_EXTERNAL environment variable. The only purpose of this
BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
properly expanded when used inside Kconfig source statements.
* Calculates the BR2_EXTERNAL value to use. If passed on the command
line, then this value is taken in priority, and saved to a
.br-external hidden file in the output directory. If not passed on
the command line, then we read the .br-external file from the
output directory. This allows the user to not pass the BR2_EXTERNAL
value at each make invocation. If no BR2_EXTERNAL value is passed,
we define it to support/dummy-external, so that the kconfig code
finds an existing $(BR2_EXTERNAL)/package/Config.in file to
include.
* Passes the BR2_EXTERNAL into the *config environment, so that its
value is found when parsing/evaluating Config.in files and .config
values.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
Tested-by: "Samuel Martin" <s.martin49@gmail.com>
Acked-by: "Samuel Martin" <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-12-05 12:11:10 -07:00
|
|
|
-include $(BR2_EXTERNAL_FILE)
|
core: offload handling of BR2_EXTERNAL into the script
Currently, we treat the case where we have no br2-external tree
(BR2_EXTERNAL is empty) differently from the case where we do have one
(BR2_EXTERNAL is not empty).
There is now no reason to treat those two cases differently:
- the kconfig snippet is always generated appropriately (i.e. it would
include the br2-external tree if set, or include nothing otherwise);
- we no longer have a dummy br-external tree either.
Also, the Makefile code to handle BR2_EXTERNAL is currently quite
readable if at least a little bit tricky.
However, when we're going to add support for using multiple br2-external
trees simultaneously, this code would need to get much, much more complex.
To keep the Makefile (rather) simple, offload all of the handling of
BR2_EXTERNAL to the recently added br2-external helper script.
However, because of Makefiles idiosyncracies, we can't use a rule to
generate that Makefile fragment.
Instead, we use $(shell ...) to call the helper script, and include the
fragment twice: once before the $(shell ...) so we can grab a previously
defined BR2_EXTERNAL value, a second time to use the one passed on the
command line, if any.
Furthermore, we can't error out (e.g. on non-existent br2-external tree)
directly from the fragment or we'd get that error on subsequent calls,
with no chance to override it even from command line.
Instead, we use a variable in which we store the error, set it to empty
before the second inclusion, so that only the one newly generated, if
any, is taken into account.
Since we know the script will always be called from Makefile context
first, we know validation will occur in Makefile context first. So we
can assume that, if there is an error, it will be detected in Makefile
context. Consequently, if the script is called to generate the kconfig
fragment, validation has already occured, and there should be no error.
So we change the error function to generate Makefile code, so that
errors are caught as explained above.
Lastly, when the value of BR2_EXTERNAL changes, we want to 'forget'
about the previous value of the BR2_EXTERNAL_MK variable, especially in
the case where BR2_EXTERNAL is now set to empty, so that we do not try
to include it later. That's why we first generate empty version of
BR2_EXTERNAL_MK, and then assign it the new value, if any.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:15 -06:00
|
|
|
$(shell support/scripts/br2-external \
|
|
|
|
-m -o '$(BR2_EXTERNAL_FILE)' $(BR2_EXTERNAL))
|
|
|
|
BR2_EXTERNAL_ERROR =
|
|
|
|
include $(BR2_EXTERNAL_FILE)
|
|
|
|
ifneq ($(BR2_EXTERNAL_ERROR),)
|
|
|
|
$(error $(BR2_EXTERNAL_ERROR))
|
core: introduce the BR2_EXTERNAL variable
This commit introduces the BR2_EXTERNAL environment variable, which
will allow to keep Buildroot customization (board-specific
configuration files or root filesystem overlays, package Config.in and
makefiles, as well as defconfigs) outside of the Buildroot tree.
This commit only introduces the variable itself, and ensures that it
is available within Config.in options. This allows us to use
$BR2_EXTERNAL in a 'source' statement in Config.in.
Following patches extend the usage of BR2_EXTERNAL to other areas
(packages and defconfigs).
In details, this commit:
* Introduces the BR2_EXTERNAL Kconfig option. This option has no
prompt, and is therefore not visible to the user and also not
stored in the .config file. It is automatically set to the value of
the BR2_EXTERNAL environment variable. The only purpose of this
BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
properly expanded when used inside Kconfig source statements.
* Calculates the BR2_EXTERNAL value to use. If passed on the command
line, then this value is taken in priority, and saved to a
.br-external hidden file in the output directory. If not passed on
the command line, then we read the .br-external file from the
output directory. This allows the user to not pass the BR2_EXTERNAL
value at each make invocation. If no BR2_EXTERNAL value is passed,
we define it to support/dummy-external, so that the kconfig code
finds an existing $(BR2_EXTERNAL)/package/Config.in file to
include.
* Passes the BR2_EXTERNAL into the *config environment, so that its
value is found when parsing/evaluating Config.in files and .config
values.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
Tested-by: "Samuel Martin" <s.martin49@gmail.com>
Acked-by: "Samuel Martin" <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-12-05 12:11:10 -07:00
|
|
|
endif
|
|
|
|
|
2015-04-07 18:53:36 -06:00
|
|
|
# To make sure that the environment variable overrides the .config option,
|
2014-02-04 08:18:51 -07:00
|
|
|
# set this before including .config.
|
|
|
|
ifneq ($(BR2_DL_DIR),)
|
|
|
|
DL_DIR := $(BR2_DL_DIR)
|
|
|
|
endif
|
2015-10-15 07:24:39 -06:00
|
|
|
ifneq ($(BR2_CCACHE_DIR),)
|
|
|
|
BR_CACHE_DIR := $(BR2_CCACHE_DIR)
|
|
|
|
endif
|
2014-02-04 08:18:51 -07:00
|
|
|
|
2013-12-28 10:39:13 -07:00
|
|
|
# Need that early, before we scan packages
|
|
|
|
# Avoids doing the $(or...) everytime
|
2014-04-13 14:42:37 -06:00
|
|
|
BR_GRAPH_OUT := $(or $(BR2_GRAPH_OUT),pdf)
|
core: introduce the BR2_EXTERNAL variable
This commit introduces the BR2_EXTERNAL environment variable, which
will allow to keep Buildroot customization (board-specific
configuration files or root filesystem overlays, package Config.in and
makefiles, as well as defconfigs) outside of the Buildroot tree.
This commit only introduces the variable itself, and ensures that it
is available within Config.in options. This allows us to use
$BR2_EXTERNAL in a 'source' statement in Config.in.
Following patches extend the usage of BR2_EXTERNAL to other areas
(packages and defconfigs).
In details, this commit:
* Introduces the BR2_EXTERNAL Kconfig option. This option has no
prompt, and is therefore not visible to the user and also not
stored in the .config file. It is automatically set to the value of
the BR2_EXTERNAL environment variable. The only purpose of this
BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
properly expanded when used inside Kconfig source statements.
* Calculates the BR2_EXTERNAL value to use. If passed on the command
line, then this value is taken in priority, and saved to a
.br-external hidden file in the output directory. If not passed on
the command line, then we read the .br-external file from the
output directory. This allows the user to not pass the BR2_EXTERNAL
value at each make invocation. If no BR2_EXTERNAL value is passed,
we define it to support/dummy-external, so that the kconfig code
finds an existing $(BR2_EXTERNAL)/package/Config.in file to
include.
* Passes the BR2_EXTERNAL into the *config environment, so that its
value is found when parsing/evaluating Config.in files and .config
values.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
Tested-by: "Samuel Martin" <s.martin49@gmail.com>
Acked-by: "Samuel Martin" <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-12-05 12:11:10 -07:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
BUILD_DIR := $(BASE_DIR)/build
|
|
|
|
BINARIES_DIR := $(BASE_DIR)/images
|
|
|
|
TARGET_DIR := $(BASE_DIR)/target
|
2013-10-02 14:06:40 -06:00
|
|
|
# initial definition so that 'make clean' works for most users, even without
|
|
|
|
# .config. HOST_DIR will be overwritten later when .config is included.
|
2014-04-23 02:39:23 -06:00
|
|
|
HOST_DIR := $(BASE_DIR)/host
|
2015-02-05 14:19:56 -07:00
|
|
|
GRAPHS_DIR := $(BASE_DIR)/graphs
|
2014-04-23 02:39:23 -06:00
|
|
|
|
|
|
|
LEGAL_INFO_DIR = $(BASE_DIR)/legal-info
|
|
|
|
REDIST_SOURCES_DIR_TARGET = $(LEGAL_INFO_DIR)/sources
|
|
|
|
REDIST_SOURCES_DIR_HOST = $(LEGAL_INFO_DIR)/host-sources
|
|
|
|
LICENSE_FILES_DIR_TARGET = $(LEGAL_INFO_DIR)/licenses
|
|
|
|
LICENSE_FILES_DIR_HOST = $(LEGAL_INFO_DIR)/host-licenses
|
|
|
|
LEGAL_MANIFEST_CSV_TARGET = $(LEGAL_INFO_DIR)/manifest.csv
|
|
|
|
LEGAL_MANIFEST_CSV_HOST = $(LEGAL_INFO_DIR)/host-manifest.csv
|
|
|
|
LEGAL_WARNINGS = $(LEGAL_INFO_DIR)/.warnings
|
|
|
|
LEGAL_REPORT = $(LEGAL_INFO_DIR)/README
|
|
|
|
|
2016-07-17 04:34:25 -06:00
|
|
|
################################################################################
|
|
|
|
#
|
|
|
|
# staging and target directories do NOT list these as
|
|
|
|
# dependencies anywhere else
|
|
|
|
#
|
|
|
|
################################################################################
|
|
|
|
$(BUILD_DIR) $(TARGET_DIR) $(HOST_DIR) $(BINARIES_DIR) $(LEGAL_INFO_DIR) $(REDIST_SOURCES_DIR_TARGET) $(REDIST_SOURCES_DIR_HOST):
|
|
|
|
@mkdir -p $@
|
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
BR2_CONFIG = $(CONFIG_DIR)/.config
|
2013-01-13 04:52:20 -07:00
|
|
|
|
2008-03-28 01:31:28 -06:00
|
|
|
# Pull in the user's configuration file
|
|
|
|
ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
|
2014-02-04 08:18:52 -07:00
|
|
|
-include $(BR2_CONFIG)
|
2007-09-11 22:34:16 -06:00
|
|
|
endif
|
2003-01-19 00:49:24 -07:00
|
|
|
|
2016-06-14 09:31:10 -06:00
|
|
|
# timezone and locale may affect build output
|
|
|
|
ifeq ($(BR2_REPRODUCIBLE),y)
|
2016-11-23 05:58:57 -07:00
|
|
|
export TZ = UTC
|
|
|
|
export LANG = C
|
|
|
|
export LC_ALL = C
|
2016-11-23 05:58:42 -07:00
|
|
|
export GZIP = -n
|
2016-11-23 05:58:40 -07:00
|
|
|
BR2_VERSION_GIT_EPOCH = $(shell GIT_DIR=$(TOPDIR)/.git $(GIT) log -1 --format=%at)
|
|
|
|
export SOURCE_DATE_EPOCH = $(if $(wildcard $(TOPDIR)/.git),$(BR2_VERSION_GIT_EPOCH),$(BR2_VERSION_EPOCH))
|
2016-12-20 06:46:21 -07:00
|
|
|
DEPENDENCIES_HOST_PREREQ += host-fakedate
|
2016-06-14 09:31:10 -06:00
|
|
|
endif
|
|
|
|
|
2007-06-28 04:47:05 -06:00
|
|
|
# To put more focus on warnings, be less verbose as default
|
|
|
|
# Use 'make V=1' to see the full commands
|
2015-04-06 23:09:09 -06:00
|
|
|
ifeq ("$(origin V)", "command line")
|
|
|
|
KBUILD_VERBOSE = $(V)
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
|
|
|
ifndef KBUILD_VERBOSE
|
2014-04-23 02:39:23 -06:00
|
|
|
KBUILD_VERBOSE = 0
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
|
|
|
|
|
|
|
ifeq ($(KBUILD_VERBOSE),1)
|
2014-04-23 02:39:23 -06:00
|
|
|
Q =
|
2007-09-22 08:19:22 -06:00
|
|
|
ifndef VERBOSE
|
2014-04-23 02:39:23 -06:00
|
|
|
VERBOSE = 1
|
2007-09-22 08:19:22 -06:00
|
|
|
endif
|
2015-06-23 15:36:06 -06:00
|
|
|
export VERBOSE
|
2007-06-28 04:47:05 -06:00
|
|
|
else
|
2014-04-23 02:39:23 -06:00
|
|
|
Q = @
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
|
|
|
|
2009-01-01 14:20:35 -07:00
|
|
|
# kconfig uses CONFIG_SHELL
|
2014-04-23 02:39:23 -06:00
|
|
|
CONFIG_SHELL := $(SHELL)
|
2009-01-01 14:20:35 -07:00
|
|
|
|
2015-10-08 14:03:37 -06:00
|
|
|
export SHELL CONFIG_SHELL Q KBUILD_VERBOSE
|
2007-06-28 04:47:05 -06:00
|
|
|
|
|
|
|
ifndef HOSTAR
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTAR := ar
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
|
|
|
ifndef HOSTAS
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTAS := as
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
|
|
|
ifndef HOSTCC
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCC := gcc
|
|
|
|
HOSTCC := $(shell which $(HOSTCC) || type -p $(HOSTCC) || echo gcc)
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCC_NOCCACHE := $(HOSTCC)
|
2007-06-28 04:47:05 -06:00
|
|
|
ifndef HOSTCXX
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCXX := g++
|
|
|
|
HOSTCXX := $(shell which $(HOSTCXX) || type -p $(HOSTCXX) || echo g++)
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCXX_NOCCACHE := $(HOSTCXX)
|
2007-09-28 13:46:58 -06:00
|
|
|
ifndef HOSTCPP
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCPP := cpp
|
2007-09-28 13:46:58 -06:00
|
|
|
endif
|
2007-06-28 04:47:05 -06:00
|
|
|
ifndef HOSTLD
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTLD := ld
|
2007-06-28 04:47:05 -06:00
|
|
|
endif
|
2007-07-15 15:54:11 -06:00
|
|
|
ifndef HOSTLN
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTLN := ln
|
2007-07-15 15:54:11 -06:00
|
|
|
endif
|
2007-09-28 13:46:58 -06:00
|
|
|
ifndef HOSTNM
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTNM := nm
|
2007-09-28 13:46:58 -06:00
|
|
|
endif
|
2013-11-11 09:47:26 -07:00
|
|
|
ifndef HOSTOBJCOPY
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTOBJCOPY := objcopy
|
2013-11-11 09:47:26 -07:00
|
|
|
endif
|
|
|
|
ifndef HOSTRANLIB
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTRANLIB := ranlib
|
|
|
|
endif
|
|
|
|
HOSTAR := $(shell which $(HOSTAR) || type -p $(HOSTAR) || echo ar)
|
|
|
|
HOSTAS := $(shell which $(HOSTAS) || type -p $(HOSTAS) || echo as)
|
|
|
|
HOSTCPP := $(shell which $(HOSTCPP) || type -p $(HOSTCPP) || echo cpp)
|
|
|
|
HOSTLD := $(shell which $(HOSTLD) || type -p $(HOSTLD) || echo ld)
|
|
|
|
HOSTLN := $(shell which $(HOSTLN) || type -p $(HOSTLN) || echo ln)
|
|
|
|
HOSTNM := $(shell which $(HOSTNM) || type -p $(HOSTNM) || echo nm)
|
|
|
|
HOSTOBJCOPY := $(shell which $(HOSTOBJCOPY) || type -p $(HOSTOBJCOPY) || echo objcopy)
|
|
|
|
HOSTRANLIB := $(shell which $(HOSTRANLIB) || type -p $(HOSTRANLIB) || echo ranlib)
|
2016-12-04 14:37:24 -07:00
|
|
|
SED := $(shell which sed || type -p sed) -i -e
|
2008-07-06 01:34:41 -06:00
|
|
|
|
2015-04-09 05:28:55 -06:00
|
|
|
export HOSTAR HOSTAS HOSTCC HOSTCXX HOSTLD
|
2010-12-07 13:09:56 -07:00
|
|
|
export HOSTCC_NOCCACHE HOSTCXX_NOCCACHE
|
2007-06-28 04:47:05 -06:00
|
|
|
|
core: fix setting of HOSTARCH
Currently, we set HOSTARCH to the output of `uname -m`. This gives us
the architecture as seen by the running kernel. For example, we would
end up with 'x86_64' for a 64-bit kernel running on an x86_64 processor.
We use that value to determine whether we can run some binary tools,
like our pre-configured external toolchains.
However, one may be running a userland in a different bitness than that
of the running kernel. For example, one may run in a 32-bit chroot, even
though the kernel is running in 64-bit.
Up until recently, this was not an issue because the pre-configured
external toolchains were all requiring an i386 (x86 in Buildroot
parlance).
But since we introduced the latest Linaro toolchains, we now have
toolchains that require a 64-bit userland.
So, when running on a 64-bit kernel, we believe those toolchains are
available, even when the user is running a 32-bit userland. This causes
build failures for our autobuilders, like so:
http://autobuild.buildroot.org/results/9cd/9cdf10ec5b31144b2e03ea09cf128702339895b3/
with the following symptoms:
>>> toolchain-external undefined Configuring
Cannot execute cross-compiler '/home/test/autobuild/instance-3/output/host/opt/ext-toolchain/bin/aarch64-linux-gnu-gcc'
So, instead of relying on the output of `uname -r`, look for the host
gcc and extract the target it was configured to generate code for.
Fixes:
http://autobuild.buildroot.org/results/9cd/9cdf10ec5b31144b2e03ea09cf128702339895b3/ (aarch64)
http://autobuild.buildroot.org/results/888/8889aa7d9fb48370e4760a6edbc6d3ae945f02f2/ (arm)
and many more...
Besides fixing those issues, it will also allow us to add the 64-bit
variants of toolchains when they exist, like the upcoming Codescape
MTI and IMG toolchains for MIPS from Imagination Technologies.
[Peter: use HOSTCC_NOCCACHE]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-11-09 12:00:21 -07:00
|
|
|
# Determine the userland we are running on.
|
|
|
|
#
|
|
|
|
# Note that, despite its name, we are not interested in the actual
|
|
|
|
# architecture name. This is mostly used to determine whether some
|
|
|
|
# of the binary tools (e.g. pre-built external toolchains) can run
|
|
|
|
# on the current host. So we need to know if the userland we're
|
|
|
|
# running on can actually run those toolchains.
|
|
|
|
#
|
|
|
|
# For example, a 64-bit prebuilt toolchain will not run on a 64-bit
|
|
|
|
# kernel if the userland is 32-bit (e.g. in a chroot for example).
|
|
|
|
#
|
|
|
|
# So, we extract the first part of the tuple the host gcc was
|
|
|
|
# configured to generate code for; we assume this is our userland.
|
|
|
|
#
|
2016-01-20 14:53:19 -07:00
|
|
|
export HOSTARCH := $(shell LC_ALL=C $(HOSTCC_NOCCACHE) -v 2>&1 | \
|
core: fix setting of HOSTARCH
Currently, we set HOSTARCH to the output of `uname -m`. This gives us
the architecture as seen by the running kernel. For example, we would
end up with 'x86_64' for a 64-bit kernel running on an x86_64 processor.
We use that value to determine whether we can run some binary tools,
like our pre-configured external toolchains.
However, one may be running a userland in a different bitness than that
of the running kernel. For example, one may run in a 32-bit chroot, even
though the kernel is running in 64-bit.
Up until recently, this was not an issue because the pre-configured
external toolchains were all requiring an i386 (x86 in Buildroot
parlance).
But since we introduced the latest Linaro toolchains, we now have
toolchains that require a 64-bit userland.
So, when running on a 64-bit kernel, we believe those toolchains are
available, even when the user is running a 32-bit userland. This causes
build failures for our autobuilders, like so:
http://autobuild.buildroot.org/results/9cd/9cdf10ec5b31144b2e03ea09cf128702339895b3/
with the following symptoms:
>>> toolchain-external undefined Configuring
Cannot execute cross-compiler '/home/test/autobuild/instance-3/output/host/opt/ext-toolchain/bin/aarch64-linux-gnu-gcc'
So, instead of relying on the output of `uname -r`, look for the host
gcc and extract the target it was configured to generate code for.
Fixes:
http://autobuild.buildroot.org/results/9cd/9cdf10ec5b31144b2e03ea09cf128702339895b3/ (aarch64)
http://autobuild.buildroot.org/results/888/8889aa7d9fb48370e4760a6edbc6d3ae945f02f2/ (arm)
and many more...
Besides fixing those issues, it will also allow us to add the 64-bit
variants of toolchains when they exist, like the upcoming Codescape
MTI and IMG toolchains for MIPS from Imagination Technologies.
[Peter: use HOSTCC_NOCCACHE]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-11-09 12:00:21 -07:00
|
|
|
sed -e '/^Target: \([^-]*\).*/!d' \
|
|
|
|
-e 's//\1/' \
|
|
|
|
-e 's/i.86/x86/' \
|
|
|
|
-e 's/sun4u/sparc64/' \
|
|
|
|
-e 's/arm.*/arm/' \
|
|
|
|
-e 's/sa110/arm/' \
|
|
|
|
-e 's/ppc64/powerpc64/' \
|
|
|
|
-e 's/ppc/powerpc/' \
|
|
|
|
-e 's/macppc/powerpc/' \
|
|
|
|
-e 's/sh.*/sh/' )
|
|
|
|
|
2015-12-30 17:34:13 -07:00
|
|
|
HOSTCC_VERSION := $(shell $(HOSTCC_NOCCACHE) --version | \
|
|
|
|
sed -n -r 's/^.* ([0-9]*)\.([0-9]*)\.([0-9]*)[ ]*.*/\1 \2/p')
|
|
|
|
|
|
|
|
# For gcc >= 5.x, we only need the major version.
|
|
|
|
ifneq ($(firstword $(HOSTCC_VERSION)),4)
|
|
|
|
HOSTCC_VERSION := $(firstword $(HOSTCC_VERSION))
|
|
|
|
endif
|
|
|
|
|
2012-06-30 04:29:22 -06:00
|
|
|
# Make sure pkg-config doesn't look outside the buildroot tree
|
2015-01-02 16:58:47 -07:00
|
|
|
HOST_PKG_CONFIG_PATH := $(PKG_CONFIG_PATH)
|
2012-06-30 04:29:22 -06:00
|
|
|
unexport PKG_CONFIG_PATH
|
2012-12-02 04:13:04 -07:00
|
|
|
unexport PKG_CONFIG_SYSROOT_DIR
|
2013-09-11 06:15:15 -06:00
|
|
|
unexport PKG_CONFIG_LIBDIR
|
2012-06-30 04:29:22 -06:00
|
|
|
|
2012-07-01 22:21:14 -06:00
|
|
|
# Having DESTDIR set in the environment confuses the installation
|
|
|
|
# steps of some packages.
|
|
|
|
unexport DESTDIR
|
|
|
|
|
2013-07-11 08:37:33 -06:00
|
|
|
# Causes breakage with packages that needs host-ruby
|
|
|
|
unexport RUBYOPT
|
|
|
|
|
2014-08-15 07:40:34 -06:00
|
|
|
include package/pkg-utils.mk
|
2014-10-03 11:01:52 -06:00
|
|
|
include package/doc-asciidoc.mk
|
2014-08-15 07:40:34 -06:00
|
|
|
|
2007-09-29 07:58:30 -06:00
|
|
|
ifeq ($(BR2_HAVE_DOT_CONFIG),y)
|
2003-01-18 14:52:46 -07:00
|
|
|
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2007-06-19 09:19:27 -06:00
|
|
|
#
|
|
|
|
# Hide troublesome environment variables from sub processes
|
|
|
|
#
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2007-06-19 09:19:27 -06:00
|
|
|
unexport CROSS_COMPILE
|
|
|
|
unexport ARCH
|
2010-12-25 16:29:42 -07:00
|
|
|
unexport CC
|
2016-04-14 08:58:32 -06:00
|
|
|
unexport LD
|
|
|
|
unexport AR
|
2010-12-25 16:29:42 -07:00
|
|
|
unexport CXX
|
|
|
|
unexport CPP
|
2015-11-17 12:04:04 -07:00
|
|
|
unexport RANLIB
|
2010-12-25 16:29:42 -07:00
|
|
|
unexport CFLAGS
|
|
|
|
unexport CXXFLAGS
|
|
|
|
unexport GREP_OPTIONS
|
2014-01-26 15:58:02 -07:00
|
|
|
unexport TAR_OPTIONS
|
2011-12-12 02:25:50 -07:00
|
|
|
unexport CONFIG_SITE
|
2012-08-17 05:54:16 -06:00
|
|
|
unexport QMAKESPEC
|
2012-07-10 01:37:22 -06:00
|
|
|
unexport TERMINFO
|
2014-09-23 22:37:13 -06:00
|
|
|
unexport MACHINE
|
2015-07-25 13:07:39 -06:00
|
|
|
unexport O
|
2003-01-16 21:31:36 -07:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
GNU_HOST_NAME := $(shell support/gnuconfig/config.guess)
|
2010-04-10 15:17:25 -06:00
|
|
|
|
2015-04-12 10:37:48 -06:00
|
|
|
PACKAGES :=
|
2015-10-22 14:33:56 -06:00
|
|
|
PACKAGES_ALL :=
|
2007-07-23 05:29:38 -06:00
|
|
|
|
2009-09-30 09:39:44 -06:00
|
|
|
# silent mode requested?
|
2015-01-01 13:03:50 -07:00
|
|
|
QUIET := $(if $(findstring s,$(filter-out --%,$(MAKEFLAGS))),-q)
|
2009-09-30 09:39:44 -06:00
|
|
|
|
Remove the "project" feature
The "project" feature was designed to allow to several projects to be
built inside the same Buildroot source tree and allowing the toolchain
and non-configurable packages to be shared between the different
projects on the same architecture. While being interesting in theory,
this feature adds a level of complexity to Buildroot, both from an
user perspective and from a developer perspective, while one of the
main Buildroot strengh is to be simple. Moreover, this feature is only
seldomly used by our users.
From a user-level perspective, this for example allows to remove the
project_build_ARCH directory, which was very confusing. The
autotools-stamps directory is also removed, since these stamps are
back at their normal location.
Description of the changes involved :
* project/, directory removed
* Makefile
- Don't include project/Makefile.in and project/project.mk anymore
- Grab a copy of the contents of project/Makefile.in at the
location it was imported, but remove the definition related to
PROJECT_BUILD_DIR. The TARGET_DIR is now in
$(BUILD_DIR)/target_dir
- Remove the creation/removal of the $(PROJECT_BUILD_DIR) and
$(PROJECT_BUILD_DIR)/autotools-stamps directories
- Don't make world depends on target-host-info. This target was
defined by project/project.mk to customize /etc/issue,
/etc/hostname and create /etc/br-version depending on the
project definitions. We can of course imagine re-adding such a
feature later.
- Replace PROJECT_BUILD_DIR by BUILD_DIR everywhere
- Remove the update, log and lognr.$(PROJECT) target, they were
specific to the project feature.
* package/Makefile.autotools.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
- Move the INSTALL_TARGET and HOOK_POST_INSTALL stamps to the same
directory as the other stamps (i.e, in the package directory).
* package/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
* package/at/at.mk,
package/busybox/busybox.mk,
package/busybox/initramfs.mk,
package/customize/customize.mk,
package/linux-fusion/linux-fusion.mk,
package/ltp-testsuite/ltp-testsuite.mk,
package/nfs-utils/nfs-utils.mk,
target/cpio/cpioroot.mk,
target/cramfs/cramfs.mk,
target/device/Atmel/DataFlashBoot/DataflashBoot.mk,
target/device/Atmel/Makefile.in,
target/device/Atmel/at91bootstrap/at91bootstrap.mk,
target/device/KwikByte/Makefile.in,
target/ext2/ext2root.mk,
target/initramfs/initramfs.mk,
target/iso9660/iso9660.mk,
target/jffs2/jffs2root.mk,
target/linux/Makefile.in,
target/romfs/romfs.mk,
target/squashfs/squashfsroot.mk,
target/tar/tarroot.mk,
target/ubifs/ubifsroot.mk
- Replace PROJECT_BUILD_DIR by BUILD_DIR
* target/device/Config.in
- Do not include project/Config.in anymore
* target/linux/Makefile.in.advanced
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Store the stamps file in $(STAMP_DIR) instead of
$(PROJECT_BUILD_DIR)/autotools-stamps
* target/u-boot/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Remove $(PROJECT) from the U-Boot target binary name
- Remove the insertion in the configuration of the project name as
the hostname
- The u-boot-autoscript target now generates
$(U_BOOT_AUTOSCRIPT).img instead of
$(U_BOOT_AUTOSCRIPT).$(PROJECT)
* toolchain/gcc/gcc-uclibc-3.x.mk
toolchain/gcc/gcc-uclibc-4.x.mk
- Move the stamps files to $(STAMP_DIR)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-09-05 07:49:30 -06:00
|
|
|
# Strip off the annoying quoting
|
2014-04-23 02:39:23 -06:00
|
|
|
ARCH := $(call qstrip,$(BR2_ARCH))
|
2010-04-28 15:40:57 -06:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
KERNEL_ARCH := $(shell echo "$(ARCH)" | sed -e "s/-.*//" \
|
2010-10-17 15:32:37 -06:00
|
|
|
-e s/i.86/i386/ -e s/sun4u/sparc64/ \
|
2013-05-05 18:14:55 -06:00
|
|
|
-e s/arcle/arc/ \
|
2013-06-10 06:04:03 -06:00
|
|
|
-e s/arceb/arc/ \
|
2010-10-17 15:32:37 -06:00
|
|
|
-e s/arm.*/arm/ -e s/sa110/arm/ \
|
2015-03-18 03:49:48 -06:00
|
|
|
-e s/aarch64.*/arm64/ \
|
2011-02-06 22:49:11 -07:00
|
|
|
-e s/bfin/blackfin/ \
|
2017-01-24 23:35:07 -07:00
|
|
|
-e s/or1k/openrisc/ \
|
2010-10-17 15:32:37 -06:00
|
|
|
-e s/parisc64/parisc/ \
|
2014-05-25 00:59:22 -06:00
|
|
|
-e s/powerpc64.*/powerpc/ \
|
2010-10-17 15:32:37 -06:00
|
|
|
-e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
|
2014-03-19 06:01:05 -06:00
|
|
|
-e s/sh.*/sh/ \
|
|
|
|
-e s/microblazeel/microblaze/)
|
2010-10-17 15:32:37 -06:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
ZCAT := $(call qstrip,$(BR2_ZCAT))
|
|
|
|
BZCAT := $(call qstrip,$(BR2_BZCAT))
|
|
|
|
XZCAT := $(call qstrip,$(BR2_XZCAT))
|
|
|
|
TAR_OPTIONS = $(call qstrip,$(BR2_TAR_OPTIONS)) -xf
|
Remove the "project" feature
The "project" feature was designed to allow to several projects to be
built inside the same Buildroot source tree and allowing the toolchain
and non-configurable packages to be shared between the different
projects on the same architecture. While being interesting in theory,
this feature adds a level of complexity to Buildroot, both from an
user perspective and from a developer perspective, while one of the
main Buildroot strengh is to be simple. Moreover, this feature is only
seldomly used by our users.
From a user-level perspective, this for example allows to remove the
project_build_ARCH directory, which was very confusing. The
autotools-stamps directory is also removed, since these stamps are
back at their normal location.
Description of the changes involved :
* project/, directory removed
* Makefile
- Don't include project/Makefile.in and project/project.mk anymore
- Grab a copy of the contents of project/Makefile.in at the
location it was imported, but remove the definition related to
PROJECT_BUILD_DIR. The TARGET_DIR is now in
$(BUILD_DIR)/target_dir
- Remove the creation/removal of the $(PROJECT_BUILD_DIR) and
$(PROJECT_BUILD_DIR)/autotools-stamps directories
- Don't make world depends on target-host-info. This target was
defined by project/project.mk to customize /etc/issue,
/etc/hostname and create /etc/br-version depending on the
project definitions. We can of course imagine re-adding such a
feature later.
- Replace PROJECT_BUILD_DIR by BUILD_DIR everywhere
- Remove the update, log and lognr.$(PROJECT) target, they were
specific to the project feature.
* package/Makefile.autotools.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
- Move the INSTALL_TARGET and HOOK_POST_INSTALL stamps to the same
directory as the other stamps (i.e, in the package directory).
* package/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
* package/at/at.mk,
package/busybox/busybox.mk,
package/busybox/initramfs.mk,
package/customize/customize.mk,
package/linux-fusion/linux-fusion.mk,
package/ltp-testsuite/ltp-testsuite.mk,
package/nfs-utils/nfs-utils.mk,
target/cpio/cpioroot.mk,
target/cramfs/cramfs.mk,
target/device/Atmel/DataFlashBoot/DataflashBoot.mk,
target/device/Atmel/Makefile.in,
target/device/Atmel/at91bootstrap/at91bootstrap.mk,
target/device/KwikByte/Makefile.in,
target/ext2/ext2root.mk,
target/initramfs/initramfs.mk,
target/iso9660/iso9660.mk,
target/jffs2/jffs2root.mk,
target/linux/Makefile.in,
target/romfs/romfs.mk,
target/squashfs/squashfsroot.mk,
target/tar/tarroot.mk,
target/ubifs/ubifsroot.mk
- Replace PROJECT_BUILD_DIR by BUILD_DIR
* target/device/Config.in
- Do not include project/Config.in anymore
* target/linux/Makefile.in.advanced
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Store the stamps file in $(STAMP_DIR) instead of
$(PROJECT_BUILD_DIR)/autotools-stamps
* target/u-boot/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Remove $(PROJECT) from the U-Boot target binary name
- Remove the insertion in the configuration of the project name as
the hostname
- The u-boot-autoscript target now generates
$(U_BOOT_AUTOSCRIPT).img instead of
$(U_BOOT_AUTOSCRIPT).$(PROJECT)
* toolchain/gcc/gcc-uclibc-3.x.mk
toolchain/gcc/gcc-uclibc-4.x.mk
- Move the stamps files to $(STAMP_DIR)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-09-05 07:49:30 -06:00
|
|
|
|
2011-02-02 06:05:56 -07:00
|
|
|
# packages compiled for the host go here
|
2014-04-23 02:39:23 -06:00
|
|
|
HOST_DIR := $(call qstrip,$(BR2_HOST_DIR))
|
Remove the "project" feature
The "project" feature was designed to allow to several projects to be
built inside the same Buildroot source tree and allowing the toolchain
and non-configurable packages to be shared between the different
projects on the same architecture. While being interesting in theory,
this feature adds a level of complexity to Buildroot, both from an
user perspective and from a developer perspective, while one of the
main Buildroot strengh is to be simple. Moreover, this feature is only
seldomly used by our users.
From a user-level perspective, this for example allows to remove the
project_build_ARCH directory, which was very confusing. The
autotools-stamps directory is also removed, since these stamps are
back at their normal location.
Description of the changes involved :
* project/, directory removed
* Makefile
- Don't include project/Makefile.in and project/project.mk anymore
- Grab a copy of the contents of project/Makefile.in at the
location it was imported, but remove the definition related to
PROJECT_BUILD_DIR. The TARGET_DIR is now in
$(BUILD_DIR)/target_dir
- Remove the creation/removal of the $(PROJECT_BUILD_DIR) and
$(PROJECT_BUILD_DIR)/autotools-stamps directories
- Don't make world depends on target-host-info. This target was
defined by project/project.mk to customize /etc/issue,
/etc/hostname and create /etc/br-version depending on the
project definitions. We can of course imagine re-adding such a
feature later.
- Replace PROJECT_BUILD_DIR by BUILD_DIR everywhere
- Remove the update, log and lognr.$(PROJECT) target, they were
specific to the project feature.
* package/Makefile.autotools.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
- Move the INSTALL_TARGET and HOOK_POST_INSTALL stamps to the same
directory as the other stamps (i.e, in the package directory).
* package/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the
configure cache
* package/at/at.mk,
package/busybox/busybox.mk,
package/busybox/initramfs.mk,
package/customize/customize.mk,
package/linux-fusion/linux-fusion.mk,
package/ltp-testsuite/ltp-testsuite.mk,
package/nfs-utils/nfs-utils.mk,
target/cpio/cpioroot.mk,
target/cramfs/cramfs.mk,
target/device/Atmel/DataFlashBoot/DataflashBoot.mk,
target/device/Atmel/Makefile.in,
target/device/Atmel/at91bootstrap/at91bootstrap.mk,
target/device/KwikByte/Makefile.in,
target/ext2/ext2root.mk,
target/initramfs/initramfs.mk,
target/iso9660/iso9660.mk,
target/jffs2/jffs2root.mk,
target/linux/Makefile.in,
target/romfs/romfs.mk,
target/squashfs/squashfsroot.mk,
target/tar/tarroot.mk,
target/ubifs/ubifsroot.mk
- Replace PROJECT_BUILD_DIR by BUILD_DIR
* target/device/Config.in
- Do not include project/Config.in anymore
* target/linux/Makefile.in.advanced
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Store the stamps file in $(STAMP_DIR) instead of
$(PROJECT_BUILD_DIR)/autotools-stamps
* target/u-boot/Makefile.in
- Replace PROJECT_BUILD_DIR by BUILD_DIR
- Remove $(PROJECT) from the U-Boot target binary name
- Remove the insertion in the configuration of the project name as
the hostname
- The u-boot-autoscript target now generates
$(U_BOOT_AUTOSCRIPT).img instead of
$(U_BOOT_AUTOSCRIPT).$(PROJECT)
* toolchain/gcc/gcc-uclibc-3.x.mk
toolchain/gcc/gcc-uclibc-4.x.mk
- Move the stamps files to $(STAMP_DIR)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-09-05 07:49:30 -06:00
|
|
|
|
2014-04-14 16:31:04 -06:00
|
|
|
# Quotes are needed for spaces and all in the original PATH content.
|
2014-04-14 16:31:05 -06:00
|
|
|
BR_PATH = "$(HOST_DIR)/bin:$(HOST_DIR)/sbin:$(HOST_DIR)/usr/bin:$(HOST_DIR)/usr/sbin:$(PATH)"
|
2014-04-14 16:31:04 -06:00
|
|
|
|
2012-11-16 20:52:14 -07:00
|
|
|
# Location of a file giving a big fat warning that output/target
|
|
|
|
# should not be used as the root filesystem.
|
2014-04-23 02:39:23 -06:00
|
|
|
TARGET_DIR_WARNING_FILE = $(TARGET_DIR)/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM
|
2012-11-16 20:52:14 -07:00
|
|
|
|
2010-12-07 13:09:56 -07:00
|
|
|
ifeq ($(BR2_CCACHE),y)
|
2014-04-23 02:39:23 -06:00
|
|
|
CCACHE := $(HOST_DIR)/usr/bin/ccache
|
2015-10-15 07:24:39 -06:00
|
|
|
BR_CACHE_DIR ?= $(call qstrip,$(BR2_CCACHE_DIR))
|
2014-02-04 08:18:50 -07:00
|
|
|
export BR_CACHE_DIR
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCC := $(CCACHE) $(HOSTCC)
|
2010-12-07 13:09:56 -07:00
|
|
|
HOSTCXX := $(CCACHE) $(HOSTCXX)
|
2015-10-04 06:28:56 -06:00
|
|
|
else
|
|
|
|
export BR_NO_CCACHE
|
2010-12-07 13:09:56 -07:00
|
|
|
endif
|
|
|
|
|
2013-01-13 04:52:20 -07:00
|
|
|
# Scripts in support/ or post-build scripts may need to reference
|
|
|
|
# these locations, so export them so it is easier to use
|
2014-02-04 08:18:52 -07:00
|
|
|
export BR2_CONFIG
|
2016-06-14 09:31:10 -06:00
|
|
|
export BR2_REPRODUCIBLE
|
2013-01-13 04:52:20 -07:00
|
|
|
export TARGET_DIR
|
|
|
|
export STAGING_DIR
|
|
|
|
export HOST_DIR
|
|
|
|
export BINARIES_DIR
|
2013-01-14 02:02:29 -07:00
|
|
|
export BASE_DIR
|
2013-01-13 04:52:20 -07:00
|
|
|
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2007-06-02 03:05:40 -06:00
|
|
|
#
|
|
|
|
# You should probably leave this stuff alone unless you know
|
|
|
|
# what you are doing.
|
|
|
|
#
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2007-06-02 03:05:40 -06:00
|
|
|
|
2007-08-22 06:35:41 -06:00
|
|
|
all: world
|
2001-12-21 17:56:11 -07:00
|
|
|
|
2012-11-12 03:08:28 -07:00
|
|
|
# Include legacy before the other things, because package .mk files
|
|
|
|
# may rely on it.
|
|
|
|
include Makefile.legacy
|
|
|
|
|
2012-04-17 08:45:23 -06:00
|
|
|
include package/Makefile.in
|
2012-02-08 09:22:16 -07:00
|
|
|
include support/dependencies/dependencies.mk
|
|
|
|
|
2014-07-27 13:28:32 -06:00
|
|
|
include toolchain/*.mk
|
2013-10-08 12:17:01 -06:00
|
|
|
include toolchain/*/*.mk
|
2007-07-23 05:29:38 -06:00
|
|
|
|
2011-09-29 13:57:38 -06:00
|
|
|
# Include the package override file if one has been provided in the
|
|
|
|
# configuration.
|
2014-04-23 02:39:23 -06:00
|
|
|
PACKAGE_OVERRIDE_FILE = $(call qstrip,$(BR2_PACKAGE_OVERRIDE_FILE))
|
2011-09-29 13:57:38 -06:00
|
|
|
ifneq ($(PACKAGE_OVERRIDE_FILE),)
|
|
|
|
-include $(PACKAGE_OVERRIDE_FILE)
|
|
|
|
endif
|
|
|
|
|
2013-09-03 02:45:41 -06:00
|
|
|
include $(sort $(wildcard package/*/*.mk))
|
2005-02-09 20:06:39 -07:00
|
|
|
|
2010-11-07 11:33:11 -07:00
|
|
|
include boot/common.mk
|
|
|
|
include linux/linux.mk
|
2014-05-05 01:52:13 -06:00
|
|
|
include fs/common.mk
|
2010-11-07 11:33:11 -07:00
|
|
|
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
# If using a br2-external tree, the BR2_EXTERNAL_$(NAME)_PATH variables
|
|
|
|
# are also present in the .config file. Since .config is included after
|
|
|
|
# we defined them in the Makefile, the values for those variables are
|
|
|
|
# quoted. We just include the generated Makefile fragment .br2-external.mk
|
|
|
|
# a third time, which will set those variables to the un-quoted values.
|
core: introduce per br2-external NAME
This unique NAME is used to construct a per br2-external tree variable,
BR2_EXTERNAL_$(NAME)_PATH, which contains the path to the br2-external
tree.
This variable is available both from Kconfig (set in the Kconfig
snippet) and from the .mk files.
Also, display the NAME and its path as a comment in the menuconfig.
This will ultimately allow us to support multiple br2-external trees at
once, with that NAME (and thus BR2_EXTERNAL_$(NAME)) uniquely defining
which br2-external tree is being used.
The obvious outcome is that BR2_EXTERNAL should now no longer be used to
refer to the files in the br2-external tree; that location is now known
from the BR2_EXTERNAL_$(NAME)_PATH variable instead. This means we no
longer need to expose, and must stop from from exposing BR2_EXTERNAL as
a Kconfig variable.
Finally, this also fixes a latent bug in the pkg-generic infra, where we
would so far always refer to BR2_EXTERNAL (even if not set) to filter
the names of packages (to decide whether they are a bootloader, a
toolchain or a simple package).
Note: since the variables in the Makefile and in Kconfig are named the
same, the one we computed early on in the Makefile will be overridden by
the one in .config when we have it. Thus, even though they are set to
the same raw value, the one from .config is quoted and, being included
later in the Makefile, will take precedence, so we just re-include the
generated Makefile fragment a third time before includeing the
br2-external's Makefiles. That's unfortunate, but there is no easy way
around that as we do want the two variables to be named the same in
Makefile and Kconfig (and we can't ask the user to un-quote that variable
himself either), hence this little dirty triple-inclusion trick.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:17 -06:00
|
|
|
include $(BR2_EXTERNAL_FILE)
|
|
|
|
|
2016-10-14 08:39:14 -06:00
|
|
|
# Nothing to include if no BR2_EXTERNAL tree in use
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
include $(BR2_EXTERNAL_MKS)
|
2013-12-05 12:11:11 -07:00
|
|
|
|
pkg-generic: improve incorrectly used package detection
Currently, the check that packages we build are indeed enabled is done
at the time a package is configured.
This can come quite late in the build process, and does not provide
direct knowledge of the real culprit for the incorrect dependency.
However, we can improve these two issues quite easily, albeit at the
expense of a very slightly more complicated make code.
First, the check can not be done at the time we define the package, i.e.
in the inner-generic-pacakge, because all its dependencies might have
not been parsed yet, so we can't yet know whether it is enabled or not
(because we can't match the package name of the dependency to its
Kconfig variable yet).
But then, we know we have all packages definitions after we scanned the
the bundled packages, kernel, bootloaders and toolchains, as well as the
br2-external tree (if any).
So, at this location, we iterate through the list of enabled packages,
and check that the packages they each depend on are indeed enabled.
This allows us to:
1- do the check very early, before any build action,
2- report on the exact offending package very easily.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-12-31 17:01:23 -07:00
|
|
|
# Now we are sure we have all the packages scanned and defined. We now
|
|
|
|
# check for each package in the list of enabled packages, that all its
|
|
|
|
# dependencies are indeed enabled.
|
|
|
|
#
|
|
|
|
# Only trigger the check for default builds. If the user forces building
|
|
|
|
# a package, even if not enabled in the configuration, we want to accept
|
|
|
|
# it.
|
|
|
|
#
|
|
|
|
ifeq ($(MAKECMDGOALS),)
|
|
|
|
|
|
|
|
define CHECK_ONE_DEPENDENCY
|
|
|
|
ifeq ($$($(2)_TYPE),target)
|
|
|
|
ifeq ($$($(2)_IS_VIRTUAL),)
|
|
|
|
ifneq ($$($$($(2)_KCONFIG_VAR)),y)
|
|
|
|
$$(error $$($(2)_NAME) is in the dependency chain of $$($(1)_NAME) that \
|
|
|
|
has added it to its _DEPENDENCIES variable without selecting it or \
|
|
|
|
depending on it from Config.in)
|
|
|
|
endif
|
|
|
|
endif
|
|
|
|
endif
|
|
|
|
endef
|
|
|
|
|
|
|
|
$(foreach pkg,$(call UPPERCASE,$(PACKAGES)),\
|
|
|
|
$(foreach dep,$(call UPPERCASE,$($(pkg)_FINAL_ALL_DEPENDENCIES)),\
|
|
|
|
$(eval $(call CHECK_ONE_DEPENDENCY,$(pkg),$(dep))$(sep))))
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2013-06-30 13:29:06 -06:00
|
|
|
dirs: $(BUILD_DIR) $(STAGING_DIR) $(TARGET_DIR) \
|
2014-03-17 02:22:33 -06:00
|
|
|
$(HOST_DIR) $(BINARIES_DIR)
|
2007-08-14 01:45:01 -06:00
|
|
|
|
2014-02-04 08:18:52 -07:00
|
|
|
$(BUILD_DIR)/buildroot-config/auto.conf: $(BR2_CONFIG)
|
2013-12-16 05:49:28 -07:00
|
|
|
$(MAKE1) $(EXTRAMAKEARGS) HOSTCC="$(HOSTCC_NOCCACHE)" HOSTCXX="$(HOSTCXX_NOCCACHE)" silentoldconfig
|
Ensure that all config-related files are generated before the build
The previous commit has removed calls to conf_write_autoconf(), which
is the function that generates the KCONFIG_AUTOCONF,
KCONFIG_AUTOHEADER, KCONFIG_TRISTATE files and the split config (with
one file per config item). Therefore, those things were not generated
anymore before the build.
In order to get them generated before the build, we use the same
mechanism as the kernel: run a silentoldconfig when the .config file
is newer than the KCONFIG_AUTOCONF file.
In Buildroot, all those elements are not really used today, except the
split config which is used a little bit in the toolchain build, in a
try to make sure the toolchain gets rebuilt properly when the
configuration changes. It does not seem that this work has been
completed.
However, as we want to keep the same behaviour as previously, we have
to generate all those elements before starting the build.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 23:27:09 -06:00
|
|
|
|
|
|
|
prepare: $(BUILD_DIR)/buildroot-config/auto.conf
|
|
|
|
|
2014-02-14 02:55:06 -07:00
|
|
|
world: target-post-image
|
2013-01-14 15:02:00 -07:00
|
|
|
|
|
|
|
.PHONY: all world toolchain dirs clean distclean source outputmakefile \
|
2015-03-21 13:49:45 -06:00
|
|
|
legal-info legal-info-prepare legal-info-clean printvars help \
|
2015-04-26 03:51:03 -06:00
|
|
|
list-defconfigs target-finalize target-post-image source-check
|
2001-12-21 17:56:11 -07:00
|
|
|
|
2015-11-26 15:13:41 -07:00
|
|
|
# Populating the staging with the base directories is handled by the skeleton package
|
2002-04-26 05:45:55 -06:00
|
|
|
$(STAGING_DIR):
|
2015-11-26 15:13:41 -07:00
|
|
|
@mkdir -p $(STAGING_DIR)
|
2010-12-31 04:39:05 -07:00
|
|
|
@ln -snf $(STAGING_DIR) $(BASE_DIR)/staging
|
2001-12-21 17:56:11 -07:00
|
|
|
|
infra: centralize rsync exclude list for VCS files
Buildroot has three places where rsync is used:
1. to copy the target skeleton
2. to copy the rootfs overlay(s)
3. to copy overridden package sources
In all of these cases, we want to exclude version control files by default.
Place 1 and 2 used an identical set of explicit --exclude options, while
place 3 used the option --cvs-exclude. This last option, however, not only
excludes version control files, but also binary files (.o, .so) and any file
or directory named 'core' (a problem for the linux kernel that has several
directories with this name). Moreover, the exact list of excluded files when
using --cvs-exclude depends on the version of rsync.
This patch creates one global variable RSYNC_VCS_EXCLUSIONS that can be used
by the various rsync commands. It excludes the version control files of
svn, git, hg, cvs and bzr.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-07 03:41:22 -07:00
|
|
|
RSYNC_VCS_EXCLUSIONS = \
|
|
|
|
--exclude .svn --exclude .git --exclude .hg --exclude .bzr \
|
|
|
|
--exclude CVS
|
|
|
|
|
2012-06-21 13:34:50 -06:00
|
|
|
STRIP_FIND_CMD = find $(TARGET_DIR)
|
|
|
|
ifneq (,$(call qstrip,$(BR2_STRIP_EXCLUDE_DIRS)))
|
|
|
|
STRIP_FIND_CMD += \( $(call finddirclauses,$(TARGET_DIR),$(call qstrip,$(BR2_STRIP_EXCLUDE_DIRS))) \) -prune -o
|
|
|
|
endif
|
2014-02-04 08:36:18 -07:00
|
|
|
STRIP_FIND_CMD += -type f \( -perm /111 -o -name '*.so*' \)
|
2014-04-30 13:29:02 -06:00
|
|
|
# file exclusions:
|
|
|
|
# - libpthread.so: a non-stripped libpthread shared library is needed for
|
|
|
|
# proper debugging of pthread programs using gdb.
|
2015-10-06 13:51:36 -06:00
|
|
|
# - ld.so: a non-stripped dynamic linker library is needed for valgrind
|
2014-04-30 13:29:02 -06:00
|
|
|
# - kernel modules (*.ko): do not function properly when stripped like normal
|
|
|
|
# applications and libraries. Normally kernel modules are already excluded
|
|
|
|
# by the executable permission check above, so the explicit exclusion is only
|
|
|
|
# done for kernel modules with incorrect permissions.
|
2015-10-06 13:51:36 -06:00
|
|
|
STRIP_FIND_CMD += -not \( $(call findfileclauses,libpthread*.so* ld-*.so* *.ko $(call qstrip,$(BR2_STRIP_EXCLUDE_FILES))) \) -print0
|
2012-06-21 13:34:50 -06:00
|
|
|
|
2014-06-27 06:15:57 -06:00
|
|
|
ifeq ($(BR2_ECLIPSE_REGISTER),y)
|
|
|
|
define TOOLCHAIN_ECLIPSE_REGISTER
|
|
|
|
./support/scripts/eclipse-register-toolchain `readlink -f $(O)` \
|
|
|
|
$(notdir $(TARGET_CROSS)) $(BR2_ARCH)
|
|
|
|
endef
|
|
|
|
TARGET_FINALIZE_HOOKS += TOOLCHAIN_ECLIPSE_REGISTER
|
|
|
|
endif
|
|
|
|
|
2014-06-27 06:15:58 -06:00
|
|
|
# Generate locale data. Basically, we call the localedef program
|
|
|
|
# (built by the host-localedef package) for each locale. The input
|
|
|
|
# data comes preferably from the toolchain, or if the toolchain does
|
|
|
|
# not have them (Linaro toolchains), we use the ones available on the
|
|
|
|
# host machine.
|
|
|
|
ifeq ($(BR2_TOOLCHAIN_USES_GLIBC),y)
|
2014-11-13 15:17:23 -07:00
|
|
|
GLIBC_GENERATE_LOCALES = $(call qstrip,$(BR2_GENERATE_LOCALE))
|
|
|
|
ifneq ($(GLIBC_GENERATE_LOCALES),)
|
2015-04-12 10:37:48 -06:00
|
|
|
PACKAGES += host-localedef
|
2014-06-27 06:15:58 -06:00
|
|
|
|
2014-11-13 15:17:23 -07:00
|
|
|
define GENERATE_GLIBC_LOCALES
|
2014-06-27 06:15:58 -06:00
|
|
|
$(Q)mkdir -p $(TARGET_DIR)/usr/lib/locale/
|
2014-11-13 15:17:23 -07:00
|
|
|
$(Q)for locale in $(GLIBC_GENERATE_LOCALES) ; do \
|
2014-06-27 06:15:58 -06:00
|
|
|
inputfile=`echo $${locale} | cut -f1 -d'.'` ; \
|
|
|
|
charmap=`echo $${locale} | cut -f2 -d'.' -s` ; \
|
|
|
|
if test -z "$${charmap}" ; then \
|
|
|
|
charmap="UTF-8" ; \
|
|
|
|
fi ; \
|
|
|
|
echo "Generating locale $${inputfile}.$${charmap}" ; \
|
|
|
|
I18NPATH=$(STAGING_DIR)/usr/share/i18n:/usr/share/i18n \
|
|
|
|
$(HOST_DIR)/usr/bin/localedef \
|
|
|
|
--prefix=$(TARGET_DIR) \
|
|
|
|
--$(call LOWERCASE,$(BR2_ENDIAN))-endian \
|
|
|
|
-i $${inputfile} -f $${charmap} \
|
|
|
|
$${locale} ; \
|
|
|
|
done
|
|
|
|
endef
|
2014-11-13 15:17:23 -07:00
|
|
|
TARGET_FINALIZE_HOOKS += GENERATE_GLIBC_LOCALES
|
2014-06-27 06:15:58 -06:00
|
|
|
endif
|
|
|
|
endif
|
|
|
|
|
2014-04-29 09:32:34 -06:00
|
|
|
ifeq ($(BR2_ENABLE_LOCALE_PURGE),y)
|
|
|
|
LOCALE_WHITELIST = $(BUILD_DIR)/locales.nopurge
|
|
|
|
LOCALE_NOPURGE = $(call qstrip,$(BR2_ENABLE_LOCALE_WHITELIST))
|
|
|
|
|
2015-07-13 17:45:28 -06:00
|
|
|
# This piece of junk does the following:
|
|
|
|
# First collect the whitelist in a file.
|
|
|
|
# Then go over all the locale dirs and for each subdir, check if it exists
|
|
|
|
# in the whitelist file. If it doesn't, kill it.
|
|
|
|
# Finally, specifically for X11, regenerate locale.dir from the whitelist.
|
2014-06-27 06:15:55 -06:00
|
|
|
define PURGE_LOCALES
|
2014-04-29 09:32:34 -06:00
|
|
|
rm -f $(LOCALE_WHITELIST)
|
2014-06-18 03:23:30 -06:00
|
|
|
for i in $(LOCALE_NOPURGE) locale-archive; do echo $$i >> $(LOCALE_WHITELIST); done
|
2014-04-29 09:32:34 -06:00
|
|
|
|
2015-07-13 15:00:34 -06:00
|
|
|
for dir in $(wildcard $(addprefix $(TARGET_DIR),/usr/share/locale /usr/share/X11/locale /usr/lib/locale)); \
|
2014-04-29 09:32:34 -06:00
|
|
|
do \
|
2015-07-13 17:45:27 -06:00
|
|
|
for langdir in $$dir/*; \
|
2014-04-29 09:32:34 -06:00
|
|
|
do \
|
2016-03-08 14:02:15 -07:00
|
|
|
if [ -e "$${langdir}" ]; \
|
|
|
|
then \
|
|
|
|
grep -qx "$${langdir##*/}" $(LOCALE_WHITELIST) || rm -rf $$langdir; \
|
|
|
|
fi \
|
2014-04-29 09:32:34 -06:00
|
|
|
done; \
|
|
|
|
done
|
2015-07-13 17:45:28 -06:00
|
|
|
if [ -d $(TARGET_DIR)/usr/share/X11/locale ]; \
|
|
|
|
then \
|
|
|
|
for lang in $(LOCALE_NOPURGE); \
|
|
|
|
do \
|
|
|
|
if [ -f $(TARGET_DIR)/usr/share/X11/locale/$$lang/XLC_LOCALE ]; \
|
|
|
|
then \
|
|
|
|
echo "$$lang/XLC_LOCALE: $$lang"; \
|
|
|
|
fi \
|
|
|
|
done > $(TARGET_DIR)/usr/share/X11/locale/locale.dir; \
|
|
|
|
fi
|
2014-04-29 09:32:34 -06:00
|
|
|
endef
|
2014-06-27 06:15:55 -06:00
|
|
|
TARGET_FINALIZE_HOOKS += PURGE_LOCALES
|
2014-04-29 09:32:34 -06:00
|
|
|
endif
|
|
|
|
|
2014-02-20 07:26:18 -07:00
|
|
|
$(TARGETS_ROOTFS): target-finalize
|
|
|
|
|
2015-04-12 10:37:48 -06:00
|
|
|
target-finalize: $(PACKAGES)
|
2014-05-12 08:19:27 -06:00
|
|
|
@$(call MESSAGE,"Finalizing target directory")
|
2014-06-27 06:15:55 -06:00
|
|
|
$(foreach hook,$(TARGET_FINALIZE_HOOKS),$($(hook))$(sep))
|
2012-10-02 02:52:15 -06:00
|
|
|
rm -rf $(TARGET_DIR)/usr/include $(TARGET_DIR)/usr/share/aclocal \
|
2013-03-06 00:14:26 -07:00
|
|
|
$(TARGET_DIR)/usr/lib/pkgconfig $(TARGET_DIR)/usr/share/pkgconfig \
|
|
|
|
$(TARGET_DIR)/usr/lib/cmake $(TARGET_DIR)/usr/share/cmake
|
|
|
|
find $(TARGET_DIR)/usr/{lib,share}/ -name '*.cmake' -print0 | xargs -0 rm -f
|
2016-11-09 03:57:27 -07:00
|
|
|
find $(TARGET_DIR)/lib/ $(TARGET_DIR)/usr/lib/ $(TARGET_DIR)/usr/libexec/ \
|
2015-09-15 07:27:06 -06:00
|
|
|
\( -name '*.a' -o -name '*.la' \) -print0 | xargs -0 rm -f
|
2010-07-24 13:29:56 -06:00
|
|
|
ifneq ($(BR2_PACKAGE_GDB),y)
|
|
|
|
rm -rf $(TARGET_DIR)/usr/share/gdb
|
2015-07-12 09:25:57 -06:00
|
|
|
endif
|
|
|
|
ifneq ($(BR2_PACKAGE_BASH),y)
|
|
|
|
rm -rf $(TARGET_DIR)/usr/share/bash-completion
|
|
|
|
endif
|
|
|
|
ifneq ($(BR2_PACKAGE_ZSH),y)
|
|
|
|
rm -rf $(TARGET_DIR)/usr/share/zsh
|
2010-07-24 13:29:56 -06:00
|
|
|
endif
|
2009-04-07 15:04:31 -06:00
|
|
|
rm -rf $(TARGET_DIR)/usr/man $(TARGET_DIR)/usr/share/man
|
|
|
|
rm -rf $(TARGET_DIR)/usr/info $(TARGET_DIR)/usr/share/info
|
2010-04-10 14:42:45 -06:00
|
|
|
rm -rf $(TARGET_DIR)/usr/doc $(TARGET_DIR)/usr/share/doc
|
2010-05-05 04:09:36 -06:00
|
|
|
rm -rf $(TARGET_DIR)/usr/share/gtk-doc
|
2016-11-22 13:53:33 -07:00
|
|
|
rmdir $(TARGET_DIR)/usr/share 2>/dev/null || true
|
2015-03-18 09:10:29 -06:00
|
|
|
$(STRIP_FIND_CMD) | xargs -0 $(STRIPCMD) 2>/dev/null || true
|
2010-11-17 16:55:43 -07:00
|
|
|
|
2012-11-20 00:18:11 -07:00
|
|
|
# See http://sourceware.org/gdb/wiki/FAQ, "GDB does not see any threads
|
|
|
|
# besides the one in which crash occurred; or SIGTRAP kills my program when
|
|
|
|
# I set a breakpoint"
|
|
|
|
ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
|
2016-11-09 03:57:27 -07:00
|
|
|
find $(TARGET_DIR)/lib/ -type f -name 'libpthread*.so*' | \
|
2013-08-20 05:03:03 -06:00
|
|
|
xargs -r $(STRIPCMD) $(STRIP_STRIP_DEBUG)
|
2012-11-20 00:18:11 -07:00
|
|
|
endif
|
|
|
|
|
2015-10-06 13:51:36 -06:00
|
|
|
# Valgrind needs ld.so with enough information, so only strip
|
|
|
|
# debugging symbols.
|
2016-11-09 03:57:27 -07:00
|
|
|
find $(TARGET_DIR)/lib/ -type f -name 'ld-*.so*' | \
|
2015-10-06 13:51:36 -06:00
|
|
|
xargs -r $(STRIPCMD) $(STRIP_STRIP_DEBUG)
|
2016-01-01 14:23:39 -07:00
|
|
|
test -f $(TARGET_DIR)/etc/ld.so.conf && \
|
|
|
|
{ echo "ERROR: we shouldn't have a /etc/ld.so.conf file"; exit 1; } || true
|
|
|
|
test -d $(TARGET_DIR)/etc/ld.so.conf.d && \
|
|
|
|
{ echo "ERROR: we shouldn't have a /etc/ld.so.conf.d directory"; exit 1; } || true
|
2010-08-30 14:52:18 -06:00
|
|
|
mkdir -p $(TARGET_DIR)/etc
|
2012-02-14 04:58:25 -07:00
|
|
|
( \
|
|
|
|
echo "NAME=Buildroot"; \
|
|
|
|
echo "VERSION=$(BR2_VERSION_FULL)"; \
|
|
|
|
echo "ID=buildroot"; \
|
|
|
|
echo "VERSION_ID=$(BR2_VERSION)"; \
|
|
|
|
echo "PRETTY_NAME=\"Buildroot $(BR2_VERSION)\"" \
|
|
|
|
) > $(TARGET_DIR)/etc/os-release
|
2009-09-30 09:40:24 -06:00
|
|
|
|
2013-04-08 00:50:16 -06:00
|
|
|
@$(foreach d, $(call qstrip,$(BR2_ROOTFS_OVERLAY)), \
|
|
|
|
$(call MESSAGE,"Copying overlay $(d)"); \
|
2016-04-23 13:18:29 -06:00
|
|
|
rsync -a --ignore-times --keep-dirlinks $(RSYNC_VCS_EXCLUSIONS) \
|
2014-11-21 09:19:01 -07:00
|
|
|
--chmod=u=rwX,go=rX --exclude .empty --exclude '*~' \
|
2013-04-08 00:50:16 -06:00
|
|
|
$(d)/ $(TARGET_DIR)$(sep))
|
2013-02-05 00:16:00 -07:00
|
|
|
|
2012-11-17 05:01:22 -07:00
|
|
|
@$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_BUILD_SCRIPT)), \
|
2013-04-08 00:50:14 -06:00
|
|
|
$(call MESSAGE,"Executing post-build script $(s)"); \
|
2014-03-10 14:51:33 -06:00
|
|
|
$(EXTRA_ENV) $(s) $(TARGET_DIR) $(call qstrip,$(BR2_ROOTFS_POST_SCRIPT_ARGS))$(sep))
|
2009-07-08 14:46:58 -06:00
|
|
|
|
2014-02-28 13:05:27 -07:00
|
|
|
target-post-image: $(TARGETS_ROOTFS) target-finalize
|
2013-02-07 04:58:43 -07:00
|
|
|
@$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_IMAGE_SCRIPT)), \
|
2013-04-08 00:50:15 -06:00
|
|
|
$(call MESSAGE,"Executing post-image script $(s)"); \
|
2014-03-10 14:51:33 -06:00
|
|
|
$(EXTRA_ENV) $(s) $(BINARIES_DIR) $(call qstrip,$(BR2_ROOTFS_POST_SCRIPT_ARGS))$(sep))
|
2013-02-07 04:58:43 -07:00
|
|
|
|
2015-04-26 03:51:12 -06:00
|
|
|
source: $(foreach p,$(PACKAGES),$(p)-all-source)
|
2002-04-26 05:45:55 -06:00
|
|
|
|
2015-04-26 03:51:01 -06:00
|
|
|
_external-deps: $(foreach p,$(PACKAGES),$(p)-all-external-deps)
|
2008-03-04 05:19:16 -07:00
|
|
|
external-deps:
|
2015-04-26 03:51:01 -06:00
|
|
|
@$(MAKE1) -Bs $(EXTRAMAKEARGS) _external-deps | sort -u
|
2008-03-04 05:19:16 -07:00
|
|
|
|
2015-04-26 03:51:03 -06:00
|
|
|
# check if download URLs are outdated
|
2015-04-26 03:51:06 -06:00
|
|
|
source-check: $(foreach p,$(PACKAGES),$(p)-all-source-check)
|
2015-04-26 03:51:03 -06:00
|
|
|
|
2012-05-17 11:33:00 -06:00
|
|
|
legal-info-clean:
|
|
|
|
@rm -fr $(LEGAL_INFO_DIR)
|
|
|
|
|
|
|
|
legal-info-prepare: $(LEGAL_INFO_DIR)
|
|
|
|
@$(call MESSAGE,"Collecting legal info")
|
2013-11-12 01:47:58 -07:00
|
|
|
@$(call legal-license-file,buildroot,COPYING,COPYING,HOST)
|
2014-07-21 07:46:31 -06:00
|
|
|
@$(call legal-manifest,PACKAGE,VERSION,LICENSE,LICENSE FILES,SOURCE ARCHIVE,SOURCE SITE,TARGET)
|
|
|
|
@$(call legal-manifest,PACKAGE,VERSION,LICENSE,LICENSE FILES,SOURCE ARCHIVE,SOURCE SITE,HOST)
|
|
|
|
@$(call legal-manifest,buildroot,$(BR2_VERSION_FULL),GPLv2+,COPYING,not saved,not saved,HOST)
|
2012-05-17 11:33:00 -06:00
|
|
|
@$(call legal-warning,the Buildroot source code has not been saved)
|
2014-02-04 08:18:52 -07:00
|
|
|
@cp $(BR2_CONFIG) $(LEGAL_INFO_DIR)/buildroot.config
|
2012-05-17 11:33:00 -06:00
|
|
|
|
2015-04-12 10:37:50 -06:00
|
|
|
legal-info: dirs legal-info-clean legal-info-prepare $(foreach p,$(PACKAGES),$(p)-all-legal-info) \
|
2013-11-12 01:47:59 -07:00
|
|
|
$(REDIST_SOURCES_DIR_TARGET) $(REDIST_SOURCES_DIR_HOST)
|
2012-05-17 11:33:00 -06:00
|
|
|
@cat support/legal-info/README.header >>$(LEGAL_REPORT)
|
|
|
|
@if [ -r $(LEGAL_WARNINGS) ]; then \
|
|
|
|
cat support/legal-info/README.warnings-header \
|
|
|
|
$(LEGAL_WARNINGS) >>$(LEGAL_REPORT); \
|
|
|
|
cat $(LEGAL_WARNINGS); fi
|
|
|
|
@rm -f $(LEGAL_WARNINGS)
|
2016-05-07 10:14:36 -06:00
|
|
|
@(cd $(LEGAL_INFO_DIR); \
|
|
|
|
find * -type f -exec sha256sum {} + | LC_ALL=C sort -k2 \
|
|
|
|
>.legal-info.sha256; \
|
|
|
|
mv .legal-info.sha256 legal-info.sha256)
|
|
|
|
@echo "Legal info produced in $(LEGAL_INFO_DIR)"
|
2012-05-17 11:33:00 -06:00
|
|
|
|
2010-05-13 11:20:33 -06:00
|
|
|
show-targets:
|
2015-04-12 10:37:51 -06:00
|
|
|
@echo $(PACKAGES) $(TARGETS_ROOTFS)
|
2010-05-13 11:20:33 -06:00
|
|
|
|
2013-12-28 10:39:11 -07:00
|
|
|
graph-build: $(O)/build/build-time.log
|
2015-02-05 14:19:56 -07:00
|
|
|
@install -d $(GRAPHS_DIR)
|
2013-12-28 10:39:11 -07:00
|
|
|
$(foreach o,name build duration,./support/scripts/graph-build-time \
|
|
|
|
--type=histogram --order=$(o) --input=$(<) \
|
2015-02-05 14:19:56 -07:00
|
|
|
--output=$(GRAPHS_DIR)/build.hist-$(o).$(BR_GRAPH_OUT) \
|
2014-02-23 08:59:11 -07:00
|
|
|
$(if $(BR2_GRAPH_ALT),--alternate-colors)$(sep))
|
2013-12-28 10:39:11 -07:00
|
|
|
$(foreach t,packages steps,./support/scripts/graph-build-time \
|
|
|
|
--type=pie-$(t) --input=$(<) \
|
2015-02-05 14:19:56 -07:00
|
|
|
--output=$(GRAPHS_DIR)/build.pie-$(t).$(BR_GRAPH_OUT) \
|
2014-02-23 08:59:11 -07:00
|
|
|
$(if $(BR2_GRAPH_ALT),--alternate-colors)$(sep))
|
2013-12-28 10:39:11 -07:00
|
|
|
|
2014-06-17 03:33:54 -06:00
|
|
|
graph-depends-requirements:
|
2014-06-13 06:17:19 -06:00
|
|
|
@dot -? >/dev/null 2>&1 || \
|
2014-06-17 03:33:54 -06:00
|
|
|
{ echo "ERROR: The 'dot' program from Graphviz is needed for graph-depends" >&2; exit 1; }
|
|
|
|
|
|
|
|
graph-depends: graph-depends-requirements
|
2015-02-05 14:19:56 -07:00
|
|
|
@$(INSTALL) -d $(GRAPHS_DIR)
|
2014-01-07 15:46:04 -07:00
|
|
|
@cd "$(CONFIG_DIR)"; \
|
2014-05-16 15:05:13 -06:00
|
|
|
$(TOPDIR)/support/scripts/graph-depends $(BR2_GRAPH_DEPS_OPTS) \
|
2016-10-23 11:19:44 -06:00
|
|
|
--direct -o $(GRAPHS_DIR)/$(@).dot
|
2016-02-07 14:34:26 -07:00
|
|
|
dot $(BR2_GRAPH_DOT_OPTS) -T$(BR_GRAPH_OUT) \
|
|
|
|
-o $(GRAPHS_DIR)/$(@).$(BR_GRAPH_OUT) \
|
|
|
|
$(GRAPHS_DIR)/$(@).dot
|
2013-12-28 10:39:12 -07:00
|
|
|
|
2015-10-17 07:33:44 -06:00
|
|
|
graph-size:
|
|
|
|
$(Q)mkdir -p $(GRAPHS_DIR)
|
|
|
|
$(Q)$(TOPDIR)/support/scripts/size-stats --builddir $(BASE_DIR) \
|
|
|
|
--graph $(GRAPHS_DIR)/graph-size.$(BR_GRAPH_OUT) \
|
|
|
|
--file-size-csv $(GRAPHS_DIR)/file-size-stats.csv \
|
|
|
|
--package-size-csv $(GRAPHS_DIR)/package-size-stats.csv
|
|
|
|
|
2016-02-07 14:34:29 -07:00
|
|
|
check-dependencies:
|
|
|
|
@cd "$(CONFIG_DIR)"; \
|
|
|
|
$(TOPDIR)/support/scripts/graph-depends -C
|
|
|
|
|
2007-09-29 07:58:30 -06:00
|
|
|
else # ifeq ($(BR2_HAVE_DOT_CONFIG),y)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
|
|
|
all: menuconfig
|
|
|
|
|
2013-02-05 00:16:02 -07:00
|
|
|
endif # ifeq ($(BR2_HAVE_DOT_CONFIG),y)
|
|
|
|
|
2004-10-08 19:06:03 -06:00
|
|
|
# configuration
|
|
|
|
# ---------------------------------------------------------------------------
|
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
HOSTCFLAGS = $(CFLAGS_FOR_BUILD)
|
2007-07-09 12:23:20 -06:00
|
|
|
export HOSTCFLAGS
|
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
.PHONY: prepare-kconfig
|
2016-07-17 04:34:26 -06:00
|
|
|
prepare-kconfig: outputmakefile $(BUILD_DIR)/.br2-external.in
|
2016-07-17 04:34:24 -06:00
|
|
|
|
2010-06-20 15:05:32 -06:00
|
|
|
$(BUILD_DIR)/buildroot-config/%onf:
|
|
|
|
mkdir -p $(@D)/lxdialog
|
2015-01-02 16:58:47 -07:00
|
|
|
PKG_CONFIG_PATH="$(HOST_PKG_CONFIG_PATH)" $(MAKE) CC="$(HOSTCC_NOCCACHE)" HOSTCC="$(HOSTCC_NOCCACHE)" \
|
|
|
|
obj=$(@D) -C $(CONFIG) -f Makefile.br $(@F)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2013-02-05 00:16:02 -07:00
|
|
|
DEFCONFIG = $(call qstrip,$(BR2_DEFCONFIG))
|
|
|
|
|
|
|
|
# We don't want to fully expand BR2_DEFCONFIG here, so Kconfig will
|
|
|
|
# recognize that if it's still at its default $(CONFIG_DIR)/defconfig
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
COMMON_CONFIG_ENV = \
|
2013-02-05 00:16:02 -07:00
|
|
|
BR2_DEFCONFIG='$(call qstrip,$(value BR2_DEFCONFIG))' \
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
KCONFIG_AUTOCONFIG=$(BUILD_DIR)/buildroot-config/auto.conf \
|
|
|
|
KCONFIG_AUTOHEADER=$(BUILD_DIR)/buildroot-config/autoconf.h \
|
Ensure that all config-related files are generated before the build
The previous commit has removed calls to conf_write_autoconf(), which
is the function that generates the KCONFIG_AUTOCONF,
KCONFIG_AUTOHEADER, KCONFIG_TRISTATE files and the split config (with
one file per config item). Therefore, those things were not generated
anymore before the build.
In order to get them generated before the build, we use the same
mechanism as the kernel: run a silentoldconfig when the .config file
is newer than the KCONFIG_AUTOCONF file.
In Buildroot, all those elements are not really used today, except the
split config which is used a little bit in the toolchain build, in a
try to make sure the toolchain gets rebuilt properly when the
configuration changes. It does not seem that this work has been
completed.
However, as we want to keep the same behaviour as previously, we have
to generate all those elements before starting the build.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 23:27:09 -06:00
|
|
|
KCONFIG_TRISTATE=$(BUILD_DIR)/buildroot-config/tristate.config \
|
2014-02-04 08:18:52 -07:00
|
|
|
BR2_CONFIG=$(BR2_CONFIG) \
|
2015-12-30 17:34:13 -07:00
|
|
|
HOST_GCC_VERSION="$(HOSTCC_VERSION)" \
|
2016-07-17 04:34:26 -06:00
|
|
|
BUILD_DIR=$(BUILD_DIR) \
|
2015-04-10 17:49:02 -06:00
|
|
|
SKIP_LEGACY=
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
xconfig: $(BUILD_DIR)/buildroot-config/qconf prepare-kconfig
|
2010-11-24 07:30:54 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) $< $(CONFIG_CONFIG_IN)
|
2009-07-20 11:17:10 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
gconfig: $(BUILD_DIR)/buildroot-config/gconf prepare-kconfig
|
2010-11-24 07:30:54 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) srctree=$(TOPDIR) $< $(CONFIG_CONFIG_IN)
|
2010-06-05 13:09:05 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
menuconfig: $(BUILD_DIR)/buildroot-config/mconf prepare-kconfig
|
2010-11-24 07:30:54 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) $< $(CONFIG_CONFIG_IN)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
nconfig: $(BUILD_DIR)/buildroot-config/nconf prepare-kconfig
|
2010-11-24 07:30:54 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) $< $(CONFIG_CONFIG_IN)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
config: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) $< $(CONFIG_CONFIG_IN)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2015-04-10 17:49:02 -06:00
|
|
|
# For the config targets that automatically select options, we pass
|
|
|
|
# SKIP_LEGACY=y to disable the legacy options. However, in that case
|
|
|
|
# no values are set for the legacy options so a subsequent oldconfig
|
|
|
|
# will query them. Therefore, run an additional olddefconfig.
|
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
oldconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) $< --oldconfig $(CONFIG_CONFIG_IN)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
randconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y $< --randconfig $(CONFIG_CONFIG_IN)
|
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
allyesconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y $< --allyesconfig $(CONFIG_CONFIG_IN)
|
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
allnoconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y $< --allnoconfig $(CONFIG_CONFIG_IN)
|
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
randpackageconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2014-02-04 08:18:52 -07:00
|
|
|
@grep -v BR2_PACKAGE_ $(BR2_CONFIG) > $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y \
|
2010-01-11 05:28:50 -07:00
|
|
|
KCONFIG_ALLCONFIG=$(CONFIG_DIR)/.config.nopkg \
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
$< --randconfig $(CONFIG_CONFIG_IN)
|
2010-01-11 05:28:50 -07:00
|
|
|
@rm -f $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2009-10-04 13:57:12 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
allyespackageconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2014-02-04 08:18:52 -07:00
|
|
|
@grep -v BR2_PACKAGE_ $(BR2_CONFIG) > $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y \
|
2010-01-11 05:28:50 -07:00
|
|
|
KCONFIG_ALLCONFIG=$(CONFIG_DIR)/.config.nopkg \
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
$< --allyesconfig $(CONFIG_CONFIG_IN)
|
2010-01-11 05:28:50 -07:00
|
|
|
@rm -f $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2009-10-04 13:57:12 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
allnopackageconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2014-02-04 08:18:52 -07:00
|
|
|
@grep -v BR2_PACKAGE_ $(BR2_CONFIG) > $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) SKIP_LEGACY=y \
|
2010-01-11 05:28:50 -07:00
|
|
|
KCONFIG_ALLCONFIG=$(CONFIG_DIR)/.config.nopkg \
|
Factorize environment variables for config utilities
Instead of duplicating the definition of KCONFIG_AUTOCONFIG,
KCONFIG_AUTOHEADER and BUILDROOT_CONFIG, let's define them in a
COMMON_CONFIG_ENV variable, which is used by all the xconfig, gconfig,
menuconfig, nconfig, config, oldconfig, randconfig, allyesconfig,
allnoconfig, randpackageconfig, allyespackageconfig,
allnopackageconfig, defconfig, %_defconfig targets.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 10:29:27 -06:00
|
|
|
$< --allnoconfig $(CONFIG_CONFIG_IN)
|
2010-01-11 05:28:50 -07:00
|
|
|
@rm -f $(CONFIG_DIR)/.config.nopkg
|
2015-04-10 17:49:02 -06:00
|
|
|
@$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN) >/dev/null
|
2009-10-04 13:57:12 -06:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
silentoldconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
Ensure that all config-related files are generated before the build
The previous commit has removed calls to conf_write_autoconf(), which
is the function that generates the KCONFIG_AUTOCONF,
KCONFIG_AUTOHEADER, KCONFIG_TRISTATE files and the split config (with
one file per config item). Therefore, those things were not generated
anymore before the build.
In order to get them generated before the build, we use the same
mechanism as the kernel: run a silentoldconfig when the .config file
is newer than the KCONFIG_AUTOCONF file.
In Buildroot, all those elements are not really used today, except the
split config which is used a little bit in the toolchain build, in a
try to make sure the toolchain gets rebuilt properly when the
configuration changes. It does not seem that this work has been
completed.
However, as we want to keep the same behaviour as previously, we have
to generate all those elements before starting the build.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-21 23:27:09 -06:00
|
|
|
$(COMMON_CONFIG_ENV) $< --silentoldconfig $(CONFIG_CONFIG_IN)
|
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
olddefconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2013-04-04 05:24:25 -06:00
|
|
|
$(COMMON_CONFIG_ENV) $< --olddefconfig $(CONFIG_CONFIG_IN)
|
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
defconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2013-02-05 00:16:02 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) $< --defconfig$(if $(DEFCONFIG),=$(DEFCONFIG)) $(CONFIG_CONFIG_IN)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-07-17 04:34:22 -06:00
|
|
|
define percent_defconfig
|
2015-02-02 08:34:46 -07:00
|
|
|
# Override the BR2_DEFCONFIG from COMMON_CONFIG_ENV with the new defconfig
|
2016-07-17 04:34:24 -06:00
|
|
|
%_defconfig: $(BUILD_DIR)/buildroot-config/conf $(1)/configs/%_defconfig prepare-kconfig
|
2016-07-17 04:34:22 -06:00
|
|
|
@$$(COMMON_CONFIG_ENV) BR2_DEFCONFIG=$(1)/configs/$$@ \
|
|
|
|
$$< --defconfig=$(1)/configs/$$@ $$(CONFIG_CONFIG_IN)
|
|
|
|
endef
|
core: allow a br2-external tree to override a defconfig
Currently, it is not possible for a br2-external tree to override a
defconfig bundled in Buildroot, nor is it possible to override one from
a previous br2-external tree in the stack.
However, it is interesting that a latter br2-external tree be able to
override a defconfig:
- the ones bundled in Buildroot are minimalist, and almost always
build a toolchain, so a br2-external tree may want to provide a
"better" defconfig (better, in the sense "suited for the project");
- similarly for a defconfig from a previous br2-external tree.
But we can't do that, as the rules for the defconfigs are generated in
the order the br2-external trees are specified, all after the bundled
defconfigs. Those rule are patten-matching rules, which means that the
first one to match is used, and the following ones are ignored.
Add a new utility macro, 'reverse', inspired from GMSL, that does what
it says: reverse a list of words.
Use that macro to reverse the list of br2-external trees, so that the
latters win over the formers, and even over bundled ones.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Samuel Martin <s.martin49@gmail.com>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:22 -06:00
|
|
|
$(eval $(foreach d,$(call reverse,$(TOPDIR) $(BR2_EXTERNAL_DIRS)),$(call percent_defconfig,$(d))$(sep)))
|
2013-12-05 12:11:12 -07:00
|
|
|
|
2016-07-17 04:34:24 -06:00
|
|
|
savedefconfig: $(BUILD_DIR)/buildroot-config/conf prepare-kconfig
|
2013-02-05 00:16:02 -07:00
|
|
|
@$(COMMON_CONFIG_ENV) $< \
|
|
|
|
--savedefconfig=$(if $(DEFCONFIG),$(DEFCONFIG),$(CONFIG_DIR)/defconfig) \
|
|
|
|
$(CONFIG_CONFIG_IN)
|
2015-06-04 02:16:33 -06:00
|
|
|
@$(SED) '/BR2_DEFCONFIG=/d' $(if $(DEFCONFIG),$(DEFCONFIG),$(CONFIG_DIR)/defconfig)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2013-02-05 00:16:02 -07:00
|
|
|
.PHONY: defconfig savedefconfig
|
2009-11-20 06:05:48 -07:00
|
|
|
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2004-10-08 19:06:03 -06:00
|
|
|
#
|
|
|
|
# Cleanup and misc junk
|
|
|
|
#
|
2013-06-07 04:13:46 -06:00
|
|
|
################################################################################
|
2010-09-26 02:56:12 -06:00
|
|
|
|
|
|
|
# outputmakefile generates a Makefile in the output directory, if using a
|
|
|
|
# separate output directory. This allows convenient use of make in the
|
|
|
|
# output directory.
|
|
|
|
outputmakefile:
|
|
|
|
ifeq ($(NEED_WRAPPER),y)
|
2011-08-31 15:35:02 -06:00
|
|
|
$(Q)$(TOPDIR)/support/scripts/mkmakefile $(TOPDIR) $(O)
|
2010-09-26 02:56:12 -06:00
|
|
|
endif
|
|
|
|
|
2016-07-17 04:34:26 -06:00
|
|
|
# Even though the target is a real file, we mark it as PHONY as we
|
|
|
|
# want it to be re-generated each time make is invoked, in case the
|
|
|
|
# value of BR2_EXTERNAL is changed.
|
|
|
|
.PHONY: $(BUILD_DIR)/.br2-external.in
|
|
|
|
$(BUILD_DIR)/.br2-external.in: $(BUILD_DIR)
|
core: offload handling of BR2_EXTERNAL into the script
Currently, we treat the case where we have no br2-external tree
(BR2_EXTERNAL is empty) differently from the case where we do have one
(BR2_EXTERNAL is not empty).
There is now no reason to treat those two cases differently:
- the kconfig snippet is always generated appropriately (i.e. it would
include the br2-external tree if set, or include nothing otherwise);
- we no longer have a dummy br-external tree either.
Also, the Makefile code to handle BR2_EXTERNAL is currently quite
readable if at least a little bit tricky.
However, when we're going to add support for using multiple br2-external
trees simultaneously, this code would need to get much, much more complex.
To keep the Makefile (rather) simple, offload all of the handling of
BR2_EXTERNAL to the recently added br2-external helper script.
However, because of Makefiles idiosyncracies, we can't use a rule to
generate that Makefile fragment.
Instead, we use $(shell ...) to call the helper script, and include the
fragment twice: once before the $(shell ...) so we can grab a previously
defined BR2_EXTERNAL value, a second time to use the one passed on the
command line, if any.
Furthermore, we can't error out (e.g. on non-existent br2-external tree)
directly from the fragment or we'd get that error on subsequent calls,
with no chance to override it even from command line.
Instead, we use a variable in which we store the error, set it to empty
before the second inclusion, so that only the one newly generated, if
any, is taken into account.
Since we know the script will always be called from Makefile context
first, we know validation will occur in Makefile context first. So we
can assume that, if there is an error, it will be detected in Makefile
context. Consequently, if the script is called to generate the kconfig
fragment, validation has already occured, and there should be no error.
So we change the error function to generate Makefile code, so that
errors are caught as explained above.
Lastly, when the value of BR2_EXTERNAL changes, we want to 'forget'
about the previous value of the BR2_EXTERNAL_MK variable, especially in
the case where BR2_EXTERNAL is now set to empty, so that we do not try
to include it later. That's why we first generate empty version of
BR2_EXTERNAL_MK, and then assign it the new value, if any.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:15 -06:00
|
|
|
$(Q)support/scripts/br2-external -k -o "$(@)" $(BR2_EXTERNAL)
|
2016-07-17 04:34:26 -06:00
|
|
|
|
2015-11-04 14:42:39 -07:00
|
|
|
# printvars prints all the variables currently defined in our
|
|
|
|
# Makefiles. Alternatively, if a non-empty VARS variable is passed,
|
|
|
|
# only the variables matching the make pattern passed in VARS are
|
|
|
|
# displayed.
|
2013-05-28 16:41:11 -06:00
|
|
|
printvars:
|
|
|
|
@$(foreach V, \
|
2015-11-04 14:42:39 -07:00
|
|
|
$(sort $(if $(VARS),$(filter $(VARS),$(.VARIABLES)),$(.VARIABLES))), \
|
2013-05-28 16:41:11 -06:00
|
|
|
$(if $(filter-out environment% default automatic, \
|
|
|
|
$(origin $V)), \
|
|
|
|
$(info $V=$($V) ($(value $V)))))
|
|
|
|
|
2004-10-08 19:06:03 -06:00
|
|
|
clean:
|
2013-09-30 05:09:27 -06:00
|
|
|
rm -rf $(TARGET_DIR) $(BINARIES_DIR) $(HOST_DIR) \
|
2014-03-17 02:22:33 -06:00
|
|
|
$(BUILD_DIR) $(BASE_DIR)/staging \
|
2015-02-05 14:19:56 -07:00
|
|
|
$(LEGAL_INFO_DIR) $(GRAPHS_DIR)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
|
|
|
distclean: clean
|
2016-11-22 19:23:02 -07:00
|
|
|
ifeq ($(O),$(CURDIR)/output)
|
2009-11-20 06:05:48 -07:00
|
|
|
rm -rf $(O)
|
|
|
|
endif
|
2016-09-11 07:55:46 -06:00
|
|
|
rm -rf $(TOPDIR)/dl $(BR2_CONFIG) $(CONFIG_DIR)/.config.old $(CONFIG_DIR)/..config.tmp \
|
2015-10-22 14:34:00 -06:00
|
|
|
$(CONFIG_DIR)/.auto.deps $(BR2_EXTERNAL_FILE)
|
2004-10-08 19:06:03 -06:00
|
|
|
|
2016-04-16 15:20:17 -06:00
|
|
|
help:
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo 'Cleaning:'
|
2009-11-20 06:05:48 -07:00
|
|
|
@echo ' clean - delete all files created by build'
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo ' distclean - delete all non-source files (including .config)'
|
|
|
|
@echo
|
|
|
|
@echo 'Build:'
|
|
|
|
@echo ' all - make world'
|
2013-01-14 15:02:00 -07:00
|
|
|
@echo ' toolchain - build toolchain'
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo
|
|
|
|
@echo 'Configuration:'
|
|
|
|
@echo ' menuconfig - interactive curses-based configurator'
|
2011-02-01 00:41:01 -07:00
|
|
|
@echo ' nconfig - interactive ncurses-based configurator'
|
2009-10-04 13:42:54 -06:00
|
|
|
@echo ' xconfig - interactive Qt-based configurator'
|
2010-06-05 13:09:05 -06:00
|
|
|
@echo ' gconfig - interactive GTK-based configurator'
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo ' oldconfig - resolve any unresolved symbols in .config'
|
2013-04-04 05:24:25 -06:00
|
|
|
@echo ' silentoldconfig - Same as oldconfig, but quietly, additionally update deps'
|
|
|
|
@echo ' olddefconfig - Same as silentoldconfig but sets new symbols to their default value'
|
2009-10-04 13:42:54 -06:00
|
|
|
@echo ' randconfig - New config with random answer to all options'
|
|
|
|
@echo ' defconfig - New config with default answer to all options'
|
2012-04-28 01:14:50 -06:00
|
|
|
@echo ' BR2_DEFCONFIG, if set, is used as input'
|
2015-02-11 06:14:49 -07:00
|
|
|
@echo ' savedefconfig - Save current config to BR2_DEFCONFIG (minimal config)'
|
2009-10-04 13:42:54 -06:00
|
|
|
@echo ' allyesconfig - New config where all options are accepted with yes'
|
|
|
|
@echo ' allnoconfig - New config where all options are answered with no'
|
2009-10-04 13:57:12 -06:00
|
|
|
@echo ' randpackageconfig - New config with random answer to package options'
|
|
|
|
@echo ' allyespackageconfig - New config where pkg options are accepted with yes'
|
|
|
|
@echo ' allnopackageconfig - New config where package options are answered with no'
|
2015-03-21 13:49:47 -06:00
|
|
|
@echo
|
|
|
|
@echo 'Package-specific:'
|
|
|
|
@echo ' <pkg> - Build and install <pkg> and all its dependencies'
|
|
|
|
@echo ' <pkg>-source - Only download the source files for <pkg>'
|
|
|
|
@echo ' <pkg>-extract - Extract <pkg> sources'
|
|
|
|
@echo ' <pkg>-patch - Apply patches to <pkg>'
|
|
|
|
@echo ' <pkg>-depends - Build <pkg>'\''s dependencies'
|
|
|
|
@echo ' <pkg>-configure - Build <pkg> up to the configure step'
|
|
|
|
@echo ' <pkg>-build - Build <pkg> up to the build step'
|
2016-10-23 09:28:51 -06:00
|
|
|
@echo ' <pkg>-show-depends - List packages on which <pkg> depends'
|
|
|
|
@echo ' <pkg>-show-rdepends - List packages which have <pkg> as a dependency'
|
2015-03-21 13:49:47 -06:00
|
|
|
@echo ' <pkg>-graph-depends - Generate a graph of <pkg>'\''s dependencies'
|
2016-10-23 11:19:44 -06:00
|
|
|
@echo ' <pkg>-graph-rdepends - Generate a graph of <pkg>'\''s reverse dependencies'
|
2015-03-21 13:49:47 -06:00
|
|
|
@echo ' <pkg>-dirclean - Remove <pkg> build directory'
|
|
|
|
@echo ' <pkg>-reconfigure - Restart the build from the configure step'
|
|
|
|
@echo ' <pkg>-rebuild - Restart the build from the build step'
|
2016-06-04 10:30:48 -06:00
|
|
|
$(foreach p,$(HELP_PACKAGES), \
|
|
|
|
@echo $(sep) \
|
|
|
|
@echo '$($(p)_NAME):' $(sep) \
|
|
|
|
$($(p)_HELP_CMDS)$(sep))
|
2011-10-10 02:46:40 -06:00
|
|
|
@echo
|
|
|
|
@echo 'Documentation:'
|
2013-09-19 04:47:14 -06:00
|
|
|
@echo ' manual - build manual in all formats'
|
2011-10-10 02:46:40 -06:00
|
|
|
@echo ' manual-html - build manual in HTML'
|
|
|
|
@echo ' manual-split-html - build manual in split HTML'
|
|
|
|
@echo ' manual-pdf - build manual in PDF'
|
2013-10-18 14:31:26 -06:00
|
|
|
@echo ' manual-text - build manual in text'
|
2011-10-10 02:46:40 -06:00
|
|
|
@echo ' manual-epub - build manual in ePub'
|
2013-12-28 10:39:11 -07:00
|
|
|
@echo ' graph-build - generate graphs of the build times'
|
2013-12-28 10:39:12 -07:00
|
|
|
@echo ' graph-depends - generate graph of the dependency tree'
|
2015-10-17 07:33:44 -06:00
|
|
|
@echo ' graph-size - generate stats of the filesystem size'
|
2015-04-23 15:04:06 -06:00
|
|
|
@echo ' list-defconfigs - list all defconfigs (pre-configured minimal systems)'
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo
|
|
|
|
@echo 'Miscellaneous:'
|
|
|
|
@echo ' source - download all sources needed for offline-build'
|
2012-06-21 13:38:42 -06:00
|
|
|
@echo ' source-check - check selected packages for valid download URLs'
|
2008-03-04 05:19:16 -07:00
|
|
|
@echo ' external-deps - list external packages used'
|
2012-05-17 11:33:00 -06:00
|
|
|
@echo ' legal-info - generate info about license compliance'
|
2007-07-08 06:20:58 -06:00
|
|
|
@echo
|
2011-02-01 00:41:01 -07:00
|
|
|
@echo ' make V=0|1 - 0 => quiet build (default), 1 => verbose build'
|
|
|
|
@echo ' make O=dir - Locate all output files in "dir", including .config'
|
|
|
|
@echo
|
2015-03-21 13:49:46 -06:00
|
|
|
@echo 'For further details, see README, generate the Buildroot manual, or consult'
|
|
|
|
@echo 'it on-line at http://buildroot.org/docs.html'
|
|
|
|
@echo
|
|
|
|
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
# List the defconfig files
|
|
|
|
# $(1): base directory
|
|
|
|
# $(2): br2-external name, empty for bundled
|
|
|
|
define list-defconfigs
|
|
|
|
@first=true; \
|
|
|
|
for defconfig in $(1)/configs/*_defconfig; do \
|
|
|
|
[ -f "$${defconfig}" ] || continue; \
|
|
|
|
if $${first}; then \
|
|
|
|
if [ "$(2)" ]; then \
|
2016-10-14 08:39:23 -06:00
|
|
|
printf 'External configs in "$(call qstrip,$(2))":\n'; \
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
else \
|
|
|
|
printf "Built-in configs:\n"; \
|
|
|
|
fi; \
|
|
|
|
first=false; \
|
|
|
|
fi; \
|
|
|
|
defconfig="$${defconfig##*/}"; \
|
|
|
|
printf " %-35s - Build for %s\n" "$${defconfig}" "$${defconfig%_defconfig}"; \
|
|
|
|
done; \
|
|
|
|
$${first} || printf "\n"
|
|
|
|
endef
|
|
|
|
|
|
|
|
# We iterate over BR2_EXTERNAL_NAMES rather than BR2_EXTERNAL_DIRS,
|
|
|
|
# because we want to display the name of the br2-external tree.
|
2015-03-21 13:49:46 -06:00
|
|
|
list-defconfigs:
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
$(call list-defconfigs,$(TOPDIR))
|
|
|
|
$(foreach name,$(BR2_EXTERNAL_NAMES),\
|
2016-10-14 08:39:23 -06:00
|
|
|
$(call list-defconfigs,$(BR2_EXTERNAL_$(name)_PATH),\
|
|
|
|
$(BR2_EXTERNAL_$(name)_DESC))$(sep))
|
2007-06-25 04:56:13 -06:00
|
|
|
|
2014-04-23 02:39:23 -06:00
|
|
|
release: OUT = buildroot-$(BR2_VERSION)
|
2010-11-03 17:00:00 -06:00
|
|
|
|
2012-02-03 14:03:29 -07:00
|
|
|
# Create release tarballs. We need to fiddle a bit to add the generated
|
|
|
|
# documentation to the git output
|
2010-11-03 17:00:00 -06:00
|
|
|
release:
|
2013-09-17 05:42:07 -06:00
|
|
|
git archive --format=tar --prefix=$(OUT)/ HEAD > $(OUT).tar
|
2013-10-18 14:31:26 -06:00
|
|
|
$(MAKE) O=$(OUT) manual-html manual-text manual-pdf
|
2015-07-17 04:20:35 -06:00
|
|
|
$(MAKE) O=$(OUT) manual-clean
|
2012-02-03 14:03:29 -07:00
|
|
|
tar rf $(OUT).tar $(OUT)
|
|
|
|
gzip -9 -c < $(OUT).tar > $(OUT).tar.gz
|
|
|
|
bzip2 -9 -c < $(OUT).tar > $(OUT).tar.bz2
|
|
|
|
rm -rf $(OUT) $(OUT).tar
|
2009-01-15 12:36:06 -07:00
|
|
|
|
2012-03-11 05:16:39 -06:00
|
|
|
print-version:
|
|
|
|
@echo $(BR2_VERSION_FULL)
|
|
|
|
|
2012-04-17 08:45:22 -06:00
|
|
|
include docs/manual/manual.mk
|
core: add support for multiple br2-external trees
Currently, we only support at most one br2-external tree. Being able
to use more than one br2-external tree can be very useful.
A use-case would be for having a br2-external to contain the basic
packages, basic board defconfigs and board files, provided by one team
responsible for the "board-bringup", while other teams consume that
br2-external as a base, and complements it each with their own set of
packages, defconfigs and extra board files.
Another use-case would be for third-parties to provide their own
Buildroot packaging in a br2-external tree, along-side the archives for
their stuff.
Finally, another use-case is to be able to add FLOSS packages in a
br2-external tree, and proprietary packages in another. This allows
to not touch the Buildroot tree at all, and still be able to get in
compliance by providing only that br2-external tree(s) that contains
FLOSS packages, leaving aside the br2-external tree(s) with the
proprietary bits.
What we do is to treat BR2_EXTERNAL as a colon-separated (space-
separated also work, and we use that internally) list of paths, on which
we iterate to construct:
- the list of all br2-external names, BR2_EXTERNAL_NAMES,
- the per-br2-external tree BR2_EXTERNAL_$(NAME) variables, which
point each to the actual location of the corresponding tree,
- the list of paths to all the external.mk files, BR2_EXTERNAL_MKS,
- the space-separated list of absolute paths to the external trees,
BR2_EXTERNAL_DIRS.
Once we have all those variables, we replace references to BR2_EXTERNAL
with either one of those.
This cascades into how we display the list of defconfigs, so that it is
easy to see what br2-external tree provides what defconfigs. As
suggested by Arnout, tweak the comment from "User-provided configs" to
"External configs", on the assumption that some br2-external trees could
be provided by vendors, so not necessarily user-provided. Ditto the menu
in Kconfig, changed from "User-provided options" to "External options".
Now, when more than one br2-external tree is used, each gets its own
sub-menu in the "User-provided options" menu. The sub-menu is labelled
with that br2-external tree's name and the sub-menu's first item is a
comment with the path to that br2-external tree.
If there's only one br2-external tree, then there is no sub-menu; there
is a single comment that contains the name and path to the br2-external
tree.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Cc: Julien CORJON <corjon.j@ecagroup.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 08:39:20 -06:00
|
|
|
-include $(foreach dir,$(BR2_EXTERNAL_DIRS),$(dir)/docs/*/*.mk)
|
2011-10-10 02:46:40 -06:00
|
|
|
|
2009-10-04 13:57:12 -06:00
|
|
|
.PHONY: $(noconfig_targets)
|
2014-11-21 09:19:00 -07:00
|
|
|
|
core: re-enter make if $(CURDIR) or $(O) are not canonical paths
When $(CURDIR) and/or $(O) contain symlinks in their paths, they can be
resolved differently, depending on each package build-system (whether it
uses the given paths or get the absolute canonical ones).
Using absolute canonical paths will help achieving reproducible builds and
will make easier tracking down host machine paths leaking into the host,
target or staging trees.
So, this change ensures the build takes place with the CURDIR and O
variables are set to their absolute canonical paths.
In order to recall the toplevel makefile with absolute canonical paths
for $(CURDIR) and $(O), we need to:
1- Compute the absolute canonical paths for $(CURDIR) and $(O) that will
be passed to the sub-make. This is achieved using the 'realpath' make
primitive. However, some care must be taken when manipulating O:
- the out-of-tree makefile wrapper happens a trailing "/.", we need
to strip this part away to not break the comparison driving the
sub-make call;
- the user can leave a trailing '/' to $(O);
- according to [1,2], realpath returns an empty string in case of
non-existing entry. So, to avoid passing an empty O= variable to
sub-make, it is necessary to define the output directory and create
it prior to call realpath on it (because on the first invocation,
$(O) usually does not yet exists), hence the trick doing the mkdir
right before calling realpath.
2- Update EXTRAMAKEARGS with the absolute canonical $(O) and use it
when call recalling the top-level makefile with umask and paths
correctly set.
3- Lastly, update the condition for setting the CONFIG_DIR and
NEED_WRAPPER variables.
Note:
* This change takes care of the makefile wrapper installed in $(O) to
avoid unneeded make recursion.
[1] https://www.gnu.org/software/make/manual/html_node/File-Name-Functions.html
[2] http://man7.org/linux/man-pages/man3/realpath.3.html
Reported-by: Matthew Weber <matt@thewebers.ws>
Cc: Matthew Weber <matt@thewebers.ws>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-17 15:05:43 -06:00
|
|
|
endif #umask / $(CURDIR) / $(O)
|