Line 81: |
Line 81: |
| sudo apt install nodejs | | sudo apt install nodejs |
| | | |
− | sudo apt install npm | + | sudo apt install npm *v12.22.9* |
| | | |
| sudo apt install build-essential ccache ecj fastjar file flex g++ gawk \ gettext git java-propose-classpath java-wrappers jq libelf-dev \ libffi-dev libncurses5-dev libncursesw5-dev libssl-dev libtool \ python python2.7-dev python3 python3-dev python3-distutils \ python3-setuptools rsync subversion swig time u-boot-tools \ unzip wget xsltproc zlib1g-dev bison | | sudo apt install build-essential ccache ecj fastjar file flex g++ gawk \ gettext git java-propose-classpath java-wrappers jq libelf-dev \ libffi-dev libncurses5-dev libncursesw5-dev libssl-dev libtool \ python python2.7-dev python3 python3-dev python3-distutils \ python3-setuptools rsync subversion swig time u-boot-tools \ unzip wget xsltproc zlib1g-dev bison |
Line 155: |
Line 155: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |
Line 187: |
Line 187: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |
Line 212: |
Line 212: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |
Line 241: |
Line 241: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |
Line 279: |
Line 279: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |
Line 315: |
Line 315: |
| After making changes and saving them to the directory, we may build compile using the following commands: | | After making changes and saving them to the directory, we may build compile using the following commands: |
| | | |
− | 1- ./scripts/feeds update -a
| + | ./scripts/feeds update -a |
| | | |
− | 2- make clean
| + | make clean |
| | | |
− | 3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
| + | Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues. |
| | | |
| The firmware can then be found in the directory listed below *Depends on the target*: | | The firmware can then be found in the directory listed below *Depends on the target*: |