From d00778205cfb9b5864ce59ccf0191d2f67fd4f75 Mon Sep 17 00:00:00 2001 From: Garrett Brown Date: Tue, 3 Jul 2018 13:13:37 -0700 Subject: Fix typo --- project/BuildDependencies/scripts/get_formed.cmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project/BuildDependencies/scripts/get_formed.cmd b/project/BuildDependencies/scripts/get_formed.cmd index f0603f4e77..92fcb80a8c 100644 --- a/project/BuildDependencies/scripts/get_formed.cmd +++ b/project/BuildDependencies/scripts/get_formed.cmd @@ -35,7 +35,7 @@ FOR /F "eol=; tokens=1" %%f IN (%SCRIPT_PATH%\0_package.native-%NATIVEPLATFORM%. CALL :processFile %%f REM Apparently there's a quirk in cmd so this means if error level => 1 IF ERRORLEVEL 1 ( - ECHO One ore more packages failed to download + ECHO One or more packages failed to download EXIT /B 7 ) ) -- cgit v1.2.3 From 1d3e706702d5d733a1bfd060435953cff61fc596 Mon Sep 17 00:00:00 2001 From: Garrett Brown Date: Thu, 5 Jul 2018 14:48:11 -0700 Subject: [docs/README.*] Fix typo in .bashrc export --- docs/README.Android.md | 2 +- docs/README.Linux.md | 2 +- docs/README.RaspberryPi.md | 2 +- docs/README.iOS.md | 2 +- docs/README.macOS.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/README.Android.md b/docs/README.Android.md index 7e19ee5695..013e0c7b72 100644 --- a/docs/README.Android.md +++ b/docs/README.Android.md @@ -181,7 +181,7 @@ Build tools and dependencies: make -j$(getconf _NPROCESSORS_ONLN) ``` -**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). +**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). **WARNING:** Look for the `Dependencies built successfully.` success message. If in doubt run a single threaded `make` command until the message appears. If the single make fails, clean the specific library by issuing `make -C target/ distclean` and run `make`again. diff --git a/docs/README.Linux.md b/docs/README.Linux.md index 7ccb333e62..d1eec2d493 100644 --- a/docs/README.Linux.md +++ b/docs/README.Linux.md @@ -153,7 +153,7 @@ cmake ../kodi -DCMAKE_INSTALL_PREFIX=/usr/local -DCORE_PLATFORM_NAME=gbm -DGBM_R ``` cmake --build . -- VERBOSE=1 -j$(getconf _NPROCESSORS_ONLN) ``` -**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). +**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). After the build process completes successfully you can test your shiny new Kodi build while in the build directory: ``` diff --git a/docs/README.RaspberryPi.md b/docs/README.RaspberryPi.md index a2f7105919..d2521ca4e6 100644 --- a/docs/README.RaspberryPi.md +++ b/docs/README.RaspberryPi.md @@ -107,7 +107,7 @@ Build tools and dependencies: make -j$(getconf _NPROCESSORS_ONLN) ``` -**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). +**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). **[back to top](#table-of-contents)** | **[back to section top](#4-build-tools-and-dependencies)** diff --git a/docs/README.iOS.md b/docs/README.iOS.md index e686bf3ded..84d584e40f 100644 --- a/docs/README.iOS.md +++ b/docs/README.iOS.md @@ -103,7 +103,7 @@ Build tools and dependencies: make -j$(getconf _NPROCESSORS_ONLN) ``` -**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). +**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). **WARNING:** Look for the `Dependencies built successfully.` success message. If in doubt run a single threaded `make` command until the message appears. If the single make fails, clean the specific library by issuing `make -C target/ distclean` and run `make`again. diff --git a/docs/README.macOS.md b/docs/README.macOS.md index c7598c05c8..58e2fc4df8 100644 --- a/docs/README.macOS.md +++ b/docs/README.macOS.md @@ -103,7 +103,7 @@ Build tools and dependencies: make -j$(getconf _NPROCESSORS_ONLN) ``` -**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). +**TIP:** By adding `-j` to the make command, you can choose how many concurrent jobs will be used and expedite the build process. It is recommended to use `-j$(getconf _NPROCESSORS_ONLN)` to compile on all available processor cores. The build machine can also be configured to do this automatically by adding `export MAKEFLAGS="-j$(getconf _NPROCESSORS_ONLN)"` to your shell config (e.g. `~/.bashrc`). **WARNING:** Look for the `Dependencies built successfully.` success message. If in doubt run a single threaded `make` command until the message appears. If the single make fails, clean the specific library by issuing `make -C target/ distclean` and run `make`again. -- cgit v1.2.3