mirror of
https://github.com/apache/nuttx.git
synced 2026-09-20 04:47:58 +08:00
Remove instructures to CD to tools/ before running ./configure.sh
Squashed commit of the following:
configs/*/README.txt: Replace each occurrence of './configure.sh' with 'tools/configure.sh'
configs/*/README.txt: Remove 'cd ..' after each './configure.sh'
configs/*/README.txt: Remove 'cd -' after each './configure.sh'
configs/*/README.txt: Remove 'cd tools' before each './configure.sh'
configs/README.txt: Remove instruction to CD tools/ before running configure.sh.
This commit is contained in:
Gregory Nutt
@@ -274,8 +274,7 @@ NuttX buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh amber/<sub-dir>
|
||||
tools/configure.sh amber/<sub-dir>
|
||||
|
||||
NOTE: you also must copy avr-libc header files into the NuttX include
|
||||
directory with command perhaps like:
|
||||
@@ -489,9 +488,7 @@ Common Configuration Notes
|
||||
1. Each Amber Web Server configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh amber/<subdir>
|
||||
cd -
|
||||
tools/configure.sh amber/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -715,7 +715,7 @@ Configurations
|
||||
This re-configuration should be done before making NuttX or else the
|
||||
subsequent 'make' will fail. If you have already attempted building
|
||||
NuttX then you will have to 1) 'make distclean' to remove the old
|
||||
configuration, 2) 'cd tools; ./configure.sh sam3u-ek/ksnh' to start
|
||||
configuration, 2) 'tools/configure.sh sam3u-ek/ksnh' to start
|
||||
with a fresh configuration, and 3) perform the configuration changes
|
||||
above.
|
||||
|
||||
|
||||
@@ -48,9 +48,7 @@ Configurations
|
||||
1. Each Arduino MEGA2560 configuration is maintained in a sub-directory
|
||||
and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh arduino-mega2560/<subdir>
|
||||
cd -
|
||||
tools/configure.sh arduino-mega2560/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -431,9 +431,7 @@ Common Configuration Notes
|
||||
1. Each Atmel AVR32DEV configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh avr32dev1/<subdir>
|
||||
cd -
|
||||
tools/configure.sh avr32dev1/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -377,9 +377,7 @@ Configurations
|
||||
Each Bambino-200e configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh bambino-200e/<subdir>
|
||||
cd -
|
||||
tools/configure.sh bambino-200e/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -13,8 +13,7 @@ Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh c5471evm/<sub-dir>
|
||||
tools/configure.sh c5471evm/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -130,9 +129,7 @@ Common Configuration Notes
|
||||
1. Each C5471 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh c5471evm/<subdir>
|
||||
cd -
|
||||
tools/configure.sh c5471evm/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -160,9 +160,7 @@ Configurations
|
||||
Each Clicker2 configuration is maintained in a sub-directory and can be
|
||||
selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh clicker2-stm32/<subdir>
|
||||
cd -
|
||||
tools/configure.sh clicker2-stm32/<subdir>
|
||||
|
||||
Before building, make sure the PATH environment variable includes the
|
||||
correct path to the directory than holds your toolchain binaries.
|
||||
|
||||
@@ -468,9 +468,7 @@ Configurations
|
||||
Each Cloudctrl configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh shenzhou/<subdir>
|
||||
cd -
|
||||
tools/configure.sh shenzhou/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
@@ -545,14 +543,12 @@ Where <subdir> is one of the following:
|
||||
|
||||
1. Intall the nxwm configuration
|
||||
|
||||
$ cd ~/nuttx-code/tools
|
||||
$ ./configure.sh shenzhou/nxwm
|
||||
$ cd ~/nuttx-code
|
||||
$ tools/configure.sh shenzhou/nxwm
|
||||
|
||||
2. Make the build context (only)
|
||||
|
||||
$ cd ..
|
||||
$ make context
|
||||
...
|
||||
|
||||
3. Install the nxwm unit test
|
||||
|
||||
|
||||
@@ -121,8 +121,7 @@ NuttX Buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh demo9s12nec64/<sub-dir>
|
||||
tools/configure.sh demo9s12nec64/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -364,9 +363,7 @@ Common Configuration Notes
|
||||
1. Each Freescale HCS12 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh demo9s12nec64/<subdir>
|
||||
cd -
|
||||
tools/configure.sh demo9s12nec64/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -656,9 +656,7 @@ Configurations
|
||||
Each DK-TM4C129X configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh dk-tm4c129x/<subdir>
|
||||
cd -
|
||||
tools/configure.sh dk-tm4c129x/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -150,8 +150,7 @@ NuttX buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh ea3131/<sub-dir>
|
||||
tools/configure.sh ea3131/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -206,8 +205,7 @@ Image Format
|
||||
Then, to build the NuttX binary ready to load with the bootloader, just
|
||||
following these steps:
|
||||
|
||||
- cd tools/ # Configure Nuttx
|
||||
- ./configure.sh ea3131/nsh # (using the nsh configuration for this example)
|
||||
- tools/configure.sh ea3131/nsh # (using the nsh configuration for this example)
|
||||
- cd .. # Set up environment
|
||||
- make # Make NuttX. This will produce nuttx.bin
|
||||
- mklpc.sh # Make the bootloader binary (nuttx.lpc)
|
||||
@@ -597,9 +595,7 @@ Common Configuration Notes
|
||||
1. Each EA3131 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh ea3131/<subdir>
|
||||
cd -
|
||||
tools/configure.sh ea3131/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -149,8 +149,7 @@ NuttX buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh ea3152/<sub-dir>
|
||||
tools/configure.sh ea3152/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -205,11 +204,10 @@ Image Format
|
||||
Then, to build the NuttX binary ready to load with the bootloader, just
|
||||
following these steps:
|
||||
|
||||
- cd tools/ # Configure Nuttx
|
||||
- ./configure.sh ea3152/ostest # (using the ostest configuration for this example)
|
||||
- cd .. # Set up environment
|
||||
- make # Make NuttX. This will produce nuttx.bin
|
||||
- mklpc.sh # Make the bootloader binary (nuttx.lpc)
|
||||
- tools/configure.sh ea3152/ostest # (using the ostest configuration for this example)
|
||||
- cd .. # Set up environment
|
||||
- make # Make NuttX. This will produce nuttx.bin
|
||||
- mklpc.sh # Make the bootloader binary (nuttx.lpc)
|
||||
|
||||
NOTES:
|
||||
|
||||
@@ -400,9 +398,7 @@ Configurations
|
||||
Each EA3152 configuration is maintained in a sub-directory and can be
|
||||
selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh ea3152/<subdir>
|
||||
cd -
|
||||
tools/configure.sh ea3152/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -193,9 +193,7 @@ Common Configuration Notes
|
||||
1. Each Eagle-100 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh eagle100/<subdir>
|
||||
cd -
|
||||
tools/configure.sh eagle100/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -231,9 +231,7 @@ CONFIGURATIONS
|
||||
Each EFM32 Gecko Starter Kit configuration is maintained in a sub-directory
|
||||
and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh efm32-g8xx-stk/<subdir>
|
||||
cd -
|
||||
tools/configure.sh efm32-g8xx-stk/<subdir>
|
||||
|
||||
If this is a Windows native build, then configure.bat should be used
|
||||
instead of configure.sh:
|
||||
|
||||
@@ -183,9 +183,7 @@ Configurations
|
||||
Each EFM32 Giant Gecko Starter Kit configuration is maintained in a sub-
|
||||
directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh efm32gg-stk3700/<subdir>
|
||||
cd -
|
||||
tools/configure.sh efm32gg-stk3700/<subdir>
|
||||
|
||||
If this is a Windows native build, then configure.bat should be used
|
||||
instead of configure.sh:
|
||||
|
||||
@@ -197,9 +197,7 @@ Configurations
|
||||
Each Stellaris EKK-LM3S9b96 Evaluation Kit configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh ekk-lm3s9b96/<subdir>
|
||||
cd -
|
||||
tools/configure.sh ekk-lm3s9b96/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -575,9 +575,7 @@ Configurations
|
||||
Each ESP32 core configuration is maintained in sub-directories and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh esp32-core/<subdir>
|
||||
cd -
|
||||
tools/configure.sh esp32-core/<subdir>
|
||||
make oldconfig
|
||||
|
||||
Before building, make sure the PATH environment variable includes the
|
||||
|
||||
@@ -78,9 +78,7 @@ Variations on the basic ez80f910200kitg configuration are maintained
|
||||
in subdirectories. To configure any specific configuration, do the
|
||||
following steps:
|
||||
|
||||
cd <nuttx-top-directory>/tools
|
||||
./configure.sh ez80f910200kitg/<sub-directory>
|
||||
cd <nuttx-top-directory>
|
||||
tools/configure.sh ez80f910200kitg/<sub-directory>
|
||||
make
|
||||
|
||||
Where <sub-directory> is the specific board configuration that you
|
||||
|
||||
@@ -82,9 +82,7 @@ Common Configuration Notes
|
||||
in subdirectories. To configure any specific configuration, do the
|
||||
following steps:
|
||||
|
||||
cd <nuttx-top-directory>/tools
|
||||
./configure.sh ez80f910200zco/<sub-directory>
|
||||
cd <nuttx-top-directgory>
|
||||
tools/configure.sh ez80f910200zco/<sub-directory>
|
||||
make
|
||||
|
||||
Where <sub-directory> is the specific board configuration that you
|
||||
|
||||
@@ -563,9 +563,7 @@ Configurations
|
||||
Each M3 Wildfire configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh fire-stm32v2/<subdir>
|
||||
cd -
|
||||
tools/configure.sh fire-stm32v2/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -818,9 +818,7 @@ Configurations
|
||||
Each Freedom K64F configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-k64f/<subdir>
|
||||
cd -
|
||||
tools/configure.sh freedom-k64f/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -825,9 +825,7 @@ Configurations
|
||||
Each Freedom K66F configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-K66F/<subdir>
|
||||
cd -
|
||||
tools/configure.sh freedom-K66F/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -44,8 +44,7 @@ NuttX Buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-kl25z/<sub-dir>
|
||||
tools/configure.sh freedom-kl25z/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -282,9 +281,7 @@ Configurations
|
||||
Each FREEDOM-KL25Z configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-kl25z/<subdir>
|
||||
cd -
|
||||
tools/configure.sh freedom-kl25z/<subdir>
|
||||
|
||||
If this is a Windows native build, then configure.bat should be used
|
||||
instead of configure.sh:
|
||||
|
||||
@@ -44,8 +44,7 @@ NuttX Buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-kl26z/<sub-dir>
|
||||
tools/configure.sh freedom-kl26z/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -260,9 +259,7 @@ Configurations
|
||||
Each FREEDOM-KL26Z configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh freedom-kl26z/<subdir>
|
||||
cd -
|
||||
tools/configure.sh freedom-kl26z/<subdir>
|
||||
|
||||
If this is a Windows native build, then configure.bat should be used
|
||||
instead of configure.sh:
|
||||
|
||||
@@ -357,9 +357,7 @@ NOTES:
|
||||
Each HY-MiniSTM32V configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh hymini-stm32v/<subdir>
|
||||
cd -
|
||||
tools/configure.sh hymini-stm32v/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ Basic configuration & build steps
|
||||
different from the default in your PATH variable).
|
||||
|
||||
- Configures nuttx creating .config file in the nuttx directory.
|
||||
$ cd tools && ./configure.sh indium-f7/f7nn-nsh && cd ..
|
||||
$ tools/configure.sh indium-f7/f7nn-nsh
|
||||
- Refreshes the .config file with the latest available configurations.
|
||||
$ make oldconfig
|
||||
- Select the features you want in the build.
|
||||
@@ -202,8 +202,8 @@ f7xx-nsh:
|
||||
see additional README.txt files in the NuttX tools repository.
|
||||
|
||||
b. If this is the intall configuration then Execute
|
||||
'cd tools && ./configure.sh indium-f7/nsh && cd ..'
|
||||
in nuttx/ in order to start configuration process.
|
||||
'tools/configure.sh indium-f7/nsh' in nuttx/ in order to start the
|
||||
configuration process.
|
||||
Caution: Doing this step more than once will overwrite .config with
|
||||
the contents of the indium-f7/nsh/defconfig file.
|
||||
|
||||
@@ -264,8 +264,8 @@ f7xx-evalos:
|
||||
see additional README.txt files in the NuttX tools repository.
|
||||
|
||||
b. If this is the intall configuration then Execute
|
||||
'cd tools && ./configure.sh indium-f7/evalos && cd ..'
|
||||
in nuttx/ in order to start configuration process.
|
||||
'tools/configure.sh indium-f7/evalos' in nuttx/ in order to start
|
||||
configuration process.
|
||||
Caution: Doing this step more than once will overwrite .config with
|
||||
the contents of the indium-f7/evalos/defconfig file.
|
||||
|
||||
|
||||
@@ -313,9 +313,7 @@ Configurations
|
||||
Each KwikStik-K40 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh kwikstik-k40/<subdir>
|
||||
cd -
|
||||
tools/configure.sh kwikstik-k40/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -172,9 +172,7 @@ Configurations
|
||||
Each LaunchXL-TMS50704 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh launchxl-tms57004/<subdir>
|
||||
cd -
|
||||
tools/configure.sh launchxl-tms57004/<subdir>
|
||||
|
||||
Before building, make sure the PATH environment variable includes the
|
||||
correct path to the directory than holds your toolchain binaries.
|
||||
|
||||
@@ -248,9 +248,7 @@ host operations. To make these modifications, do the following:
|
||||
1. First configure to build the NSH configuration from the top-level
|
||||
NuttX directory:
|
||||
|
||||
cd tools
|
||||
./configure lincoln60/nsh
|
||||
cd ..
|
||||
|
||||
2. Then edit the top-level .config file to enable USB host. Make the
|
||||
following changes:
|
||||
@@ -277,9 +275,7 @@ Configurations
|
||||
Each Lincoln 60 configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lincoln60/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lincoln60/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -202,9 +202,7 @@ Configurations
|
||||
Each Stellaris MDL-S2E Reference Design configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lm3s6432-s2e/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lm3s6432-s2e/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -340,9 +340,7 @@ Configurations
|
||||
Each Stellaris LM3S6965 Evaluation Kit configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lm3s6965-ek/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lm3s6965-ek/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -260,9 +260,7 @@ Configurations
|
||||
Each Stellaris LM3S8962 Evaluation Kit configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lm3s8962-ek/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lm3s8962-ek/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -469,9 +469,7 @@ Configurations
|
||||
Each LM4F120 LaunchPad configuration is maintained in a
|
||||
sub-directory and can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lm4f120-launchpad/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lm4f120-launchpad/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -629,9 +629,7 @@ Configurations
|
||||
Each LPC4330-Xplorer configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lpc4330-xplorer/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lpc4330-xplorer/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -668,9 +668,7 @@ Configurations
|
||||
Each LPC4337-ws configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh LPC4337-ws/<subdir>
|
||||
cd -
|
||||
tools/configure.sh LPC4337-ws/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -665,9 +665,7 @@ Configurations
|
||||
Each LPC4357-EVB configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lpc4357-evb/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lpc4357-evb/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -668,9 +668,7 @@ Configurations
|
||||
Each LPC4370-Link2 configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh LPC4370-Link2/<subdir>
|
||||
cd -
|
||||
tools/configure.sh LPC4370-Link2/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -508,9 +508,7 @@ Configurations
|
||||
Each LPCXpresso configuration is maintained in a sub-directory and can be
|
||||
selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lpcxpresso-lpc1115/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lpcxpresso-lpc1115/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -560,9 +560,7 @@ Configurations
|
||||
Each LPCXpresso configuration is maintained in a sub-directory and can be
|
||||
selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh lpcxpresso-lpc1768/<subdir>
|
||||
cd -
|
||||
tools/configure.sh lpcxpresso-lpc1768/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -108,9 +108,7 @@ Configurations
|
||||
Each Maple configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh maple/<subdir>
|
||||
cd -
|
||||
tools/configure.sh maple/<subdir>
|
||||
|
||||
Before building, make sure the PATH environment variable includes the
|
||||
correct path to the directory than holds your toolchain binaries.
|
||||
|
||||
@@ -211,9 +211,7 @@ USB Host Configuration
|
||||
1. First configure to build the NSH configuration from the top-level
|
||||
NuttX directory:
|
||||
|
||||
cd tools
|
||||
./configure mbed/nsh
|
||||
cd ..
|
||||
|
||||
2. Then edit the top-level .config file to enable USB host. Make the
|
||||
following changes using 'make menuconfig':
|
||||
@@ -250,9 +248,7 @@ Configurations
|
||||
Each mbed configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh mbed/<subdir>
|
||||
cd -
|
||||
tools/configure.sh mbed/<subdir>
|
||||
|
||||
Where <subdir> is one of the mbed subdirectories described in the
|
||||
following paragraph.
|
||||
|
||||
@@ -212,9 +212,7 @@ USB Host Configuration
|
||||
1. First configure to build the NSH configuration from the top-level
|
||||
NuttX directory:
|
||||
|
||||
cd tools
|
||||
./configure mcb1700/nsh
|
||||
cd ..
|
||||
|
||||
2. Then edit the top-level .config file to enable USB host. Make the
|
||||
following changes using 'make menuconfig':
|
||||
@@ -251,9 +249,7 @@ Configurations
|
||||
Each mcb1700 configuration is maintained in a sub-directory and can be selected
|
||||
as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh mcb1700/<subdir>
|
||||
cd -
|
||||
tools/configure.sh mcb1700/<subdir>
|
||||
|
||||
Where <subdir> is one of the mcb1700 subdirectories described in the
|
||||
following paragraph.
|
||||
|
||||
@@ -89,8 +89,7 @@ NuttX buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh eagle100/<sub-dir>
|
||||
tools/configure.sh eagle100/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -316,9 +315,7 @@ Configurations
|
||||
1. Each NXP LPC214x configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh mcu123-lpc214x/<subdir>
|
||||
cd -
|
||||
tools/configure.sh mcu123-lpc214x/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -287,8 +287,7 @@ NuttX buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh micropendous3/<sub-dir>
|
||||
tools/configure.sh micropendous3/<sub-dir>
|
||||
|
||||
NOTE: you also must copy avr-libc header files into the NuttX include
|
||||
directory with command perhaps like:
|
||||
@@ -509,9 +508,7 @@ Common Configuration Notes
|
||||
1. Each Micropendous3 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh micropendous3/<subdir>
|
||||
cd -
|
||||
tools/configure.sh micropendous3/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -475,9 +475,7 @@ Configurations
|
||||
Each Mikroe-STM32F4 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh mikroe-stm32f4/<subdir>
|
||||
cd -
|
||||
tools/configure.sh mikroe-stm32f4/<subdir>
|
||||
|
||||
If this is a Windows native build, then configure.bat should be used
|
||||
instead of configure.sh:
|
||||
|
||||
@@ -838,9 +838,7 @@ Configurations
|
||||
Each PIC32MX configuration is maintained in a sub-directory and can be
|
||||
selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh mirtoo/<subdir>
|
||||
cd -
|
||||
tools/configure.sh mirtoo/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
@@ -20,8 +20,7 @@ Buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh misoc/<sub-dir>
|
||||
tools/configure.sh misoc/<sub-dir>
|
||||
make oldconfig context
|
||||
|
||||
2. Clone the latest buildroot package into <some-dir>/buildroot
|
||||
|
||||
@@ -248,9 +248,7 @@ Common Configuration Notes
|
||||
1. Each MoteinoMEGA configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh moteino-mega/<subdir>
|
||||
cd -
|
||||
tools/configure.sh moteino-mega/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -228,8 +228,7 @@ NuttX Buildroot Toolchain
|
||||
|
||||
1. You must have already configured Nuttx in <some-dir>/nuttx.
|
||||
|
||||
cd tools
|
||||
./configure.sh ne64badge/<sub-dir>
|
||||
tools/configure.sh ne64badge/<sub-dir>
|
||||
|
||||
2. Download the latest buildroot package into <some-dir>
|
||||
|
||||
@@ -471,9 +470,7 @@ Common Configuration Notes
|
||||
1. Each Freescale HCS12 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh ne64badge/<subdir>
|
||||
cd -
|
||||
tools/configure.sh ne64badge/<subdir>
|
||||
|
||||
Where <subdir> is one of the configuration sub-directories described in
|
||||
the following paragraph.
|
||||
|
||||
@@ -232,9 +232,7 @@ Configurations
|
||||
Each nr5m100-nexys4 configuration is maintained in a sub-directory and
|
||||
can be selected as follow:
|
||||
|
||||
cd tools
|
||||
./configure.sh nr5m100-nexys4/<subdir>
|
||||
cd -
|
||||
tools/configure.sh nr5m100-nexys4/<subdir>
|
||||
|
||||
Where <subdir> is one of the following:
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user