aboutsummaryrefslogtreecommitdiff
path: root/support/misc
Commit message (Collapse)AuthorAgeFilesLines
* Update for 2021.052021.05Gravatar Peter Korsgaard2021-06-061-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2021.02.2Gravatar Peter Korsgaard2021-05-121-1/+1
| | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 76b4f9e9b658d3a4a72266e4aa2e63aa7a3f54f9) [Peter: drop Makefile change] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2021.02.1Gravatar Peter Korsgaard2021-04-071-1/+1
| | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit bb10b0dfe690a77e137395ad91290d799bf018c5) [Peter: drop Makefile change] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/pkg-cmake.mk: don't unconditionally set CMAKE_CXX_COMPILERGravatar Fabrice Fontaine2021-04-021-4/+6
| | | | | | | | | | | | | | | | Don't unconditionally set CMAKE_CXX_COMPILER as it will raise a build failure on qpid-proton because "if the toolchain specifies a value for CMAKE_CXX_COMPILER, then CMake assumes the compiler works and goes straight ahead trying to use it": https://cmake.org/cmake/help/latest/module/CheckLanguage.html https://issues.apache.org/jira/browse/PROTON-2365 Fixes: - http://autobuild.buildroot.org/results/05f344151100219c159ca4d466a453df96bf07fa Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: rename placeholder] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* Update for 2021.022021.02Gravatar Peter Korsgaard2021-03-061-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2020.11.3Gravatar Peter Korsgaard2021-02-171-1/+1
| | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 610e67b1fc4ac44e0c4a7ba437c917ad6d63f481) [Peter: drop Makefile changes] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2020.11.2Gravatar Peter Korsgaard2021-01-311-1/+1
| | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 551cb630079316efe928d7c2eb0358a19e38fc48) [Peter: drop Makefile changes] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2020.11.1Gravatar Peter Korsgaard2020-12-271-1/+1
| | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 804a9e18656c1584b059129e0b5cebe2a2405fac) [Peter: drop Makefile changes] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2020.112020.11Gravatar Peter Korsgaard2020-12-021-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gitlab-ci: move before-script before scriptGravatar Yann E. MORIN2020-09-091-6/+6
| | | | | | | | | Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: handle the basic tests in scriptGravatar Yann E. MORIN2020-09-091-12/+3
| | | | | | | | | | | | | | | | Note that those tests were so far ignored only when requesting a single defconfig build, or a single runtime test build; everything else was trigerring thoses tests. However, it feels more natural that they are also ignored when all defconfigs build. or all runtime tests, are explictly requested. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: handle single runtime test in scriptGravatar Yann E. MORIN2020-09-091-9/+0
| | | | | | | | | Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: handle single defconfig in scriptGravatar Yann E. MORIN2020-09-091-11/+0
| | | | | | | | | Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: handle the run-time tests conditions in scriptGravatar Yann E. MORIN2020-09-091-9/+0
| | | | | | | | | | | | Note that we do not propagate the existing comment, because it is partially wrong; instead we just keep the per-condition comments. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: handle the defconfig build conditions in scriptGravatar Yann E. MORIN2020-09-091-9/+0
| | | | | | | | | | | | Note that we do not propagate the existing comment, because it is partially wrong; instead we just keep the per-condition comments. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: share the image version with the childGravatar Yann E. MORIN2020-09-091-5/+0
| | | | | | | | | | | | | | | Currently, the image name and version are duplicated in the main pipeline and the generated, child pipeline. This is a condition for a future gaffe, so let's use the image from the main pipeline when generating the child one. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* Merge branch 'next'Gravatar Peter Korsgaard2020-09-021-8/+1
|\ | | | | | | | | | | A number of merge conflicts, but hopefully they are all sorted out now. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
| * core: make it possible to check flake8 like we check packageGravatar Yann E. MORIN2020-09-011-8/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move the code to run check-flake8 into the Makefile, like we have for check-package, so that it is easy to run locally (and not wait for someone to report a failure from their Gitlab pipelines). Compared to the existing check from gitlab-ci.yml, the Makefile check differs in this respect: - don't explicitly find *.py files: they are supposed to also be found as a result of running 'file' on them; - use git ls-tree instead of find: this is supopsedly faster as it uses the index rather than readdir(); - don't output the count of warnings or errors: the output is a single integer, which is confusing when there are errors, and even more so when there are no, when it is simply '0'; - don't sort: the output is already stable and independent from the locale; - don't report the number of processed files: this information is rather useless, and getting a hold of it would be more challenging in this new code. Note: ideally, we would want to use --null, --zero, or similar options, with utilities that generates or parses a files listing. While git ls-tree and xargs do support it, it becomes a little bit tricky to use the --print0 option of file, and then grep in that output (it is not undoable, but would requires replacing grep+cut with some sed trickery). Since we do not expect our scripts names to contain funky chars (like \n or a colon), we just hand-wave away that issue (and the old code was doing the same assumption too). Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
* | Update for 2020.082020.08Gravatar Peter Korsgaard2020-09-011-1/+1
| | | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* | gitlab-ci: update the image versionGravatar Yann E. MORIN2020-08-151-1/+1
| | | | | | | | Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* | support/misc/gitlab-ci.yml.in: use python3 for flake8Gravatar Thomas Petazzoni2020-08-141-1/+1
|/ | | | | | | | | | | | | | | The pkg-stats script now uses Python3 only constructs (the "async" keyword) and therefore fails to pass the Python2 flake8 test. Let's use the Python3 flake8 instead. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/681711009 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: Titouan Christophe <titouan.christophe@railnova.eu> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: check all defconfigs on every pushGravatar Romain Naour2020-07-271-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The defconfig check has been introduced by the previous patch before the building each defconfig but those builds are done every week or more. Checking if a defconfig is valid can be done on every push in the repository since it take few seconds. This would allow to detect as soon as possible a problem in a defconfig and eventually avoid breaking the build while build testing all defconfig. Introduce a new job template ".defconfig_check" in gitlab-ci.yml.in and modify the generate-gitlab-ci-yml to create a job for each defconfig to run the test. Although, we could have used only one job to do all tests, using one job per defconfig allow to identify easily in gitlab which defconfig is falling. Tested: https://gitlab.com/kubu93/buildroot/pipelines/138331069 https://gitlab.com/kubu93/buildroot/pipelines/171223758 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab-ci: check generated config filesGravatar Romain Naour2020-07-271-0/+1
| | | | | | | | | | | | Use the script added by the previous patch to check generated config files. Tested on gitlab: https://gitlab.com/kubu93/buildroot/pipelines/137597966 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* gitlab: generate the gitlab-ci configuration before each buildGravatar Romain Naour2020-07-271-0/+123
| | | | | | | | | | | | | | | | Since Gitlab 12.9, Gitlab allow to trigger child pipeline with generated configuration file. See: https://gitlab.com/gitlab-org/gitlab/-/issues/35632 This allow us to stop updating the .gitlab-ci.yml file when a new defconfig is added to Buildroot. Remove check-gitlab-ci.yml job since it is now uneeded. Remove .gitlab-ci.yml make target. Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> [ann.morin.1998@free.fr: manual: no longer needed to update at all] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* package/meson: bump to version 0.55.0Gravatar James Hilliard2020-07-181-0/+4
| | | | | | | | | | | | | | Drop fix rpath patch which is no longer needed. Drop g-ir-scanner/g-ir-compiler override patch which is now upstream. Rebase remaining patches. Meson now requires single quotes for cross-compilation.conf, replace double quotes with single quotes. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* Makefile: make-4.3 now longer un-escapes \# in macrosGravatar Yaroslav Syrytsia2020-03-311-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | make-4.3 shipped with a backward incompatible change in how sharp signs are handled in macros. Previously, up to make 4.2, the sharp sign would always start a comment, unless backslash-escaped, even in a macro or a fucntion call. Now, the sharp sign is no longer starting a comment when it appears inside such a macro or function call. This behaviour was supposed to be in force since 3.81, but was not; 4.3 fixed the code to match the doc. As such, use of external toolchains is broken, as we use the sharp sign in the copy_toolchain_sysroot macro, in shell variable expansion to strip off any leading /: ${target\#/}. Fix that by applying the workaround suggested in the release annoucement [0], by using a variable to hold a sharp sign. [0] https://lists.gnu.org/archive/html/info-gnu/2020-01/msg00004.html Signed-off-by: Yaroslav Syrytsia <me@ys.lc> [yann.morin.1998@free.fr: - move the SHARP_SIGN definition out of Makefile and into support/ - expand the commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* Update for 2020.022020.02Gravatar Peter Korsgaard2020-03-081-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2019.112019.11Gravatar Peter Korsgaard2019-12-011-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2019.082019.08Gravatar Peter Korsgaard2019-09-011-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/cmake: Explicitly set CMAKE_SYSTEMGravatar Frank Vanbever2019-08-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some packages test for CMAKE_SYSTEM explicitly[1] CMAKE_SYSTEM is comprised of CMAKE_SYSTEM_NAME and CMAKE_SYSTEM_VERSION. It defaults to CMAKE_SYSTEM_NAME if CMAKE_SYSTEM_VERSION is not set[2] At the point CMAKE_SYSTEM_NAME is set to "Linux" CMAKE_SYSTEM is already constructed. Setting it explicitly ensures that it is the correct value. This is because we do set CMAKE_SYSTEM_NAME twice, in fact: - first in toolchainfile.cmake, so that we tell cmake to use the "Buildroot" platform, - second, in the Buildroot.cmake platform definition itself, so that we eventually behave like the Linux platform. We also set CMAKE_SYSTEM_VERSION to 1, and so the real CMAKE_SYSTEM value should be set to Linux-1 if we were to follow the documentation to the letter. However, for Linux, the version does not matter, and in some situations may even be harmful (that was reported in one of the commits that introduce Buildroot.cmake and toolchainfile.cmake). [1] Fluidsynth https://github.com/FluidSynth/fluidsynth/blob/0cd44d00e1ec9a905d51163efde7b70ff8ae0ba3/CMakeLists.txt#L80 [2] https://cmake.org/cmake/help/git-master/variable/CMAKE_SYSTEM.html#variable:CMAKE_SYSTEM Signed-off-by: Frank Vanbever <frank.vanbever@mind.be> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr> [Peter: update commit message with description from Yann] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2019.052019.05Gravatar Peter Korsgaard2019-06-021-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* infra/utils: add helper to generate comma-separated listsGravatar Yann E. MORIN2019-04-151-0/+4
| | | | | | | | | | | | | | | Add a helper macro that, from a space-separated list of items, returns a comma-separated list of the quoted items. This will be useful when we need to generate lists in JSON, later... Code suggested by Thomas P. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
* Update for 2019.022019.02Gravatar Peter Korsgaard2019-03-041-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* infra/pkg-cmake: use an obviously-invalid value for CMAKE_SYSTEM_VERSIONGravatar Yann E. MORIN2019-01-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In 36568732e4, we expanded toolchain.cmake to also define the value for CMAKE_SYSTEM_VERSION, as the cmake documentation states that it must be manually defined when doing cross-compilation [0]: When the CMAKE_SYSTEM_NAME variable is set explicitly to enable cross compiling then the value of CMAKE_SYSTEM_VERSION must also be set explicitly to specify the target system version. However, the fix in 36568732e4 uses the version of the kernel headers, assuming that would be the oldest kernel we could run on. Yet, this is not the case, because glibc (for example) has fallbacks to support running on kernels older than the headers it was built against. The cmake official wiki [1] additionally states: * CMAKE_SYSTEM_VERSION : optional, version of your target system, not used very much. Folllowed a little bit below, by: * CMAKE_TOOLCHAIN_FILE : absolute or relative path to a cmake script which sets up all the toolchain related variables mentioned above For instance for crosscompiling from Linux to Embedded Linux on PowerPC this file could look like this: # this one is important SET(CMAKE_SYSTEM_NAME Linux) #this one not so much SET(CMAKE_SYSTEM_VERSION 1) [...] Furthermore, using the kernel headers version can be a bit misleading (as it really looks like is is the correct version to use when it is not), while it is obvious that 1 is not really the output of `uname -r` and thus is definitely not misleading. Finally, random searches [2] about CMAKE_SYSTEM_VERSION, mostly only turns up issues related with Windows, Mac-OS, and to a lesser extent, Android (where it is forcibly set to 1), with issues realted to running under just Linux (as opposed to Adnroid) mostly non-existent. Consequently, we revert to using the value that is suggested in the cmake WiKi, i.e. 1, and which is basically what we also used as a workaround in the azure-iot-sdk-c paclkage up until d300b1d3b1. A case were we will need to have a real kernel version, is if we one day have a cmake-based pacakge that builds and installs a kernel module [3], because it will need the _running_ kernel version to install it in /lib/modules/VERSION/, but in that case it will anyway most probably not be the headers version. [0] https://cmake.org/cmake/help/v3.8/variable/CMAKE_SYSTEM_VERSION.html [1] https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/CrossCompiling [2] https://duckduckgo.com/?q=CMAKE_SYSTEM_VERSION [3] https://stackoverflow.com/questions/38205745/cmake-system-version-not-updated-for-new-kernel Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Samuel Martin <s.martin49@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/pkg-cmake: add CMAKE_SYSTEM_VERSION to toolchainfile.cmakeGravatar Arnout Vandecappelle (Essensium/Mind)2019-01-121-0/+1
| | | | | | | | | | | | | | | | | | | Quoting the CMake documentation: When the CMAKE_SYSTEM_NAME variable is set explicitly to enable cross compiling then the value of CMAKE_SYSTEM_VERSION must also be set explicitly to specify the target system version. Thus, we should also set CMAKE_SYSTEM_VERSION in toolchainfile.cmake. It is supposed to be set to the value of `uname -r` on the target. We don't have that exact value available (unless we build the kernel), but the value of BR2_TOOLCHAIN_HEADERS_AT_LEAST contains the (minimum) version of the kernel it will run on, so it should be OK for all practical purposes. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* Update for 2018.112018.11Gravatar Peter Korsgaard2018-12-011-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Merge branch 'next'Gravatar Peter Korsgaard2018-09-071-1/+1
|\ | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
| * support/misc: updating Vagrantfile to ubuntu 18.04Gravatar Angelo Compagnucci2018-08-131-1/+1
| | | | | | | | | | | | | | | | | | This patch updates the vagrant box to ubuntu bionic 64 and switches back to the official ubuntu image cause the issues with the official image are now solved. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* | Update for 2018.082018.08Gravatar Peter Korsgaard2018-09-061-1/+1
|/ | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/misc/toolchainfile.cmake.in: use TARGET_LDFLAGS for shared and ↵Gravatar Damien Thébault2018-07-191-0/+2
| | | | | | | | | | | | | | module libraries With cmake packages, we are only using TARGET_LDFLAGS for executables and not for shared libraries. This patch adds CMAKE_SHARED_LINKER_FLAGS and CMAKE_MODULE_LINKER_FLAGS to the cmake toolchain file so that buildroot TARGET_LDFLAGS are used for shared and module libraries. Signed-off-by: Damien Thébault <damien.thebault@vitec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* Update for 2018.052018.05Gravatar Peter Korsgaard2018-06-011-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2018.022018.02Gravatar Peter Korsgaard2018-03-041-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2017.112017.11Gravatar Peter Korsgaard2017-11-301-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Update for 2017.082017.08Gravatar Peter Korsgaard2017-09-021-1/+1
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/scripts: relocate-sdk.sh now uses a normal pipe to find stringsGravatar Wolfgang Grandegger2017-07-201-2/+2
| | | | | | | | The normal shell does not support the bashism "< <(...)". Therefore we use a normal pipe to find files containing a specific string. Signed-off-by: Wolfgang Grandegger <wg@grandegger.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* support/scripts: relocate-sdk.sh now creates sdk-location in share/buildrootGravatar Wolfgang Grandegger2017-07-201-1/+1
| | | | | | | | This is because $(HOST_DIR)/usr is gone. Signed-off-by: Wolfgang Grandegger <wg@grandegger.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* pkg-cmake: programs are now installed in $(HOST_DIR)/binGravatar Arnout Vandecappelle2017-07-051-1/+1
| | | | | | | | | | Remove the redundant usr/ component of the HOST_DIR paths. Since a previous commit added a symlink from $(HOST_DIR)/usr to $(HOST_DIR), everything keeps on working. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* pkg-cmake: move configuration files out of $(HOST_DIR)/usrGravatar Arnout Vandecappelle2017-07-051-2/+2
| | | | | | | | | | | Move toolchainfile.cmake and Buildroot.cmake from $(HOST_DIR)/usr/share/buildroot to $(HOST_DIR)/share/buildroot. Build-tested with a bunch of cmake packages. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* support/scripts: add relocate-sdk.sh script for SDK relocationGravatar Wolfgang Grandegger2017-07-041-0/+47
| | | | | | | | | | | | | | | | | It will install the script "relocate-sdk.sh" in the HOST_DIR allowing to adjust the path to the SDK directory in all text files after it has been moved to a new location. Signed-off-by: Wolfgang Grandegger <wg@grandegger.com> [Thomas: - Fix shebang to be /bin/sh instead of /bin/bash, suggested by Arnout - Use | instead of \ as a separator for sed expressions, suggested by Arnout, discussed with Wolfgang and others - Remove ./ at the beginning of LOCFILE, suggested by Arnout - Fix comment about the path check being made before doing the replacement, suggested by Arnout - Fix indentation, suggested by Arnout.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* support/misc/target-dir-warning.txt: fix typoGravatar Rahul Bedarkar2017-06-141-1/+1
| | | | | | | s/owernship/ownership/ Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>