Skip to content

Commit d2393ae

Browse files
committed
doxygen: convert 4.tool
Signed-off-by: Chen Wang <[email protected]>
1 parent 803f2a1 commit d2393ae

File tree

6 files changed

+80
-75
lines changed

6 files changed

+80
-75
lines changed

documentation/4.tool/INDEX.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,5 @@
11
@page tool Tool
2+
3+
- @subpage env
4+
5+
- @subpage scons

documentation/Doxyfile

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -915,7 +915,8 @@ RECURSIVE = YES
915915

916916
EXCLUDE = ./0.doxygen/mainpage.h \
917917
./README.md \
918-
./2.quick-start/quick_start_qemu
918+
./2.quick-start/quick_start_qemu \
919+
./env/env-vscode.md
919920

920921
# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
921922
# directories that are symbolic links (a Unix file system feature) are excluded

documentation/INDEX.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@
1515
- @ref interrupt_management
1616
- @ref kernel_porting
1717

18-
**Tool**
18+
@subpage tool
1919

20-
- [User Manual of Env](env/env.md)
21-
- [SCons](scons/scons.md)
20+
- @ref env
21+
- @ref scons
2222

2323
**Device**
2424

documentation/env/env.md

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
# User Manual of Env
1+
@page env User Manual of Env
22

33
Env is a handy utility tool developed by RT-Thread team to build environment, graphical system configuration, and packages management for software projects that intend to run on RT-Thread operating system. Env tool come with source code builder, compilation environment and package management system.
44

55
It is a wrapper tool for build-in menuconfig, which is an open source GUI tool which is designed to tailor for ease of use for developers. It can also be used to configure the kernel configuration parameters, components and software packages so that developers can construct the system like lego blocks.
66

77
Env for Windows repository: https://github.com/RT-Thread/env-windows
88

9-
## Main Features
9+
# Main Features
1010

1111
- menuconfig provides graphical interface to interact with operational logic and configuration parameters
1212
- Each configuration option come with help session by default.
@@ -16,24 +16,24 @@ Env for Windows repository: https://github.com/RT-Thread/env-windows
1616
- Modular software packages and decoupling design make it easier to maintain.
1717
- It also featured with point and click to download additional software packages and dependencies directly from Internet.
1818

19-
## Download
19+
# Download
2020

2121
- [Download the Env tool](https://github.com/RT-Thread/env-windows/releases), e.g. `env-windows-v1.3.5.7z`.
2222
- Extract the .7z file and the path shouldn't contain any non-ascii or space characters.
2323

24-
## User Guide of Env
24+
# User Guide of Env
2525

26-
### Open the control Console
26+
## Open the control Console
2727

2828
The rt-thread software package environment is mainly based on the command line console so that the rt-thread development environment can be set up by minimizing the modification of configuration files.
2929

3030
There are two ways to open the console:
3131

32-
#### 1. click the Env directory executable file
32+
### 1. click the Env directory executable file
3333

3434
To enter the Env directory, you can run `env.exe` in this directory. If it fails to open, you can try to use `env.bat`.
3535

36-
#### 2. open the Env console from the right-click menu in the folder
36+
### 2. open the Env console from the right-click menu in the folder
3737

3838
Add Env to the right-click menu:
3939

@@ -49,23 +49,23 @@ Follow the steps from the image to launch the Env console from the right-click m
4949

5050
> Due to the need for the environment variables of the Env process to be set, the anti-virus software may misreport at the first startup. If the anti-virus software misreport is encountered, allow Env related programs to run, and then add related programs to the white list.
5151
52-
### Compile
52+
## Compile
5353

5454
Scons is a compile building tool used by RT-Thread to compile RT-Threads using the scons related commands.
5555

56-
#### Step One: Switch to the BSP root directory
56+
### Step One: Switch to the BSP root directory
5757

5858
If you use Method 1 to open Env console, you need to switch to the target BSP using the `cd` command.
5959

6060
For example, the target BSP is `rt-thread\bsp\stm32\stm32f103-dofly-lyc8`:
6161

6262
![stm32f429-apollo project directory](figures/cd_cmd.png)
6363

64-
#### Step Two: Compile the BSP
64+
### Step Two: Compile the BSP
6565

6666
Env for Windows carries Python2.7 & Scons . To compile BSP, just use the default ARM_GCC toolchain by running `scons` or `scons -j12` (12 CPU cores compiling) command in the target BSP directory.
6767

68-
Env for Windows carries ARM GCC toolchain by default. When users compile ARM BSPs, users can directly type `scons` or `scons -j12` command to compile the BSP. However, if the BSP is other architecture, e.g. RISC-V, users need to use `scons --exec-path='C:\xxx\sdk-toolchain-RISC-V-GCC-WCH-1.0.0\bin' -j12` command to specify the toolchain when compiling.
68+
Env for Windows carries ARM GCC toolchain by default. When users compile ARM BSPs, users can directly type `scons` or `scons -j12` command to compile the BSP. However, if the BSP is other architecture, e.g. RISC-V, users need to use `scons --exec-path='C:\\xxx\\sdk-toolchain-RISC-V-GCC-WCH-1.0.0\\bin' -j12` command to specify the toolchain when compiling.
6969

7070
![compilation project using scons command](figures/use_scons.png)
7171

@@ -82,30 +82,30 @@ scons --target=mdk4
8282
scons --target=mdk5
8383
```
8484

85-
For more scons tutorials, please refer to [*Scons*](../scons/scons.md).
85+
For more scons tutorials, please refer to @ref scons.
8686

87-
### BSP configuration: menuconfig
87+
## BSP configuration: menuconfig
8888

8989
Menuconfig is a graphical configuration tool that RT-Thread uses to configure and tailor the entire system.
9090

91-
#### Instruction for Shortcuts
91+
### Instruction for Shortcuts
9292

9393
Go to the BSP root directory and open the interface by entering `menuconfig`. The menuconfig common shortcuts are as shown:
9494

9595
![Commonly-used Shortcuts for menuconfig](figures/hotkey.png)
9696

97-
#### Modify Settings
97+
### Modify Settings
9898

9999
There are many types of configuration items in menuconfig, and the modification methods are different. The common types are:
100100

101101
- On/Off Type: Use the space bar to select or close
102102
- Value, string type: After pressing the Enter key, a dialog box will appear, and the configuration items will be modified in the dialog box.
103103

104-
#### Save Settings
104+
### Save Settings
105105

106106
After selecting the configuration item, press `ESC` to exit, and select `Save` to automatically generate the `rtconfig.h` file. At this point, using the `scons` command again will recompile the project according to the new rtconfig.h file.
107107

108-
### Package Management
108+
## Package Management
109109

110110
RT-Thread provides a package management platform where the officially available or developer-supplied packages are stored. The platform provides developers with a choice of reusable software packages that are an important part of RT-Thread.
111111

@@ -141,7 +141,7 @@ optional arguments:
141141
--printenv print environmental variables to check
142142
```
143143

144-
#### Download, update, and delete packages
144+
### Download, update, and delete packages
145145

146146
Before downloading and updating the software package, you need to **open** the target package in `menuconfig`.
147147

@@ -155,13 +155,13 @@ Find the package you need and open, then save and exit menuconfig. The package w
155155
- **update**: if the selected package has a latest update on the server and the version is selected **latest**, then enter `pkgs --update` , the package will be updated in local;
156156
- **delete**: if a software package is not needed, deselect it in menuconfig and then use `pkgs --update` command. Then locally downloaded but unselected packages will be deleted.
157157

158-
#### Update local package information and index
158+
### Update local package information and index
159159

160160
As the package system grows, more and more packages will be added, so the list of packages in menuconfig may be **unsynchronized** with the server. This can be fixed by using `pkgs --upgrade` or `pkgs --upgrade-force` command (recommended), which not only synchronizes updates to local software packages [information and index](https://github.com/RT-Thread/packages), which are recommended for regular use. If there is a upgrade failure or merge failure, please use `pkgs --upgrade-force` command to force upgrade the local software packages index (recommended to use).
161161

162162
If wants to upgrade the [Env script](https://github.com/RT-Thread/env) as well, please use `pkgs --upgrade-script-force` command. This command not only can upgrade the software packages index, but also can upgrade the Env script.
163163

164-
### Env Tool Configuration
164+
## Env Tool Configuration
165165

166166
- The new version of the Env tool includes an automatic update package and an option to automatically generate mdk/iar projects. The default is not enabled. It can be configured using `menuconfig -s/--setting` .
167167

@@ -180,21 +180,21 @@ The three options are:
180180
- **Send usage data for improve product**: For user number statistic.
181181

182182

183-
## Use Env in Your Project
183+
# Use Env in Your Project
184184

185-
### How to Modify Options in Menuconfig
185+
## How to Modify Options in Menuconfig
186186

187187
If you want to add a macro definition in the configuration item of menuconfig, you can modify the `Kconfig` file under BSP. The modification method can search Kconfig syntax on the Internet for detailed documentation, or refer to the Kconfig file in RT-Thread or The Kconfig file in the BSP that supports menuconfig.
188188

189-
### To Add menuconfig function to New Project
189+
## To Add menuconfig function to New Project
190190

191191
New project here refers to a newly developed project that has not yet generated `.config` and `rtconfig.h`. Because these two files are only created when menuconfig is first saved. The specific process is as follows:
192192

193193
1. Copy the kconfig file from the BSP that already supports the menuconfig function to the new project root directory.
194194
2. Note that modifying the RTT_ROOT value in Kconfig is the directory where RT-Thread is located, otherwise RTT_ROOT may be not found.
195195
3. Start the configuration with the menuconfig command.
196196

197-
### To Add menuconfig function to old Project
197+
## To Add menuconfig function to old Project
198198

199199
Old project here refers to the development that has been going on for a while, and there is a modified `rtconfig.h` file in the project, but there is no project configured with menuconfig. The specific process is as follows:
200200

@@ -205,53 +205,53 @@ Old project here refers to the development that has been going on for a while, a
205205
5. Use the menuconfig command to configure the old project we want to modify. Menuconfig will read the `.config` file generated in the second step and generate a new `.config` file and rtconfig.h file based on the configuration parameters of the old project.
206206
6. Check the old and new rtconfig.h files. If there are any inconsistencies, you can use the menuconfig command to adjust the configuration items.
207207

208-
## Notes for Using Env
208+
# Notes for Using Env
209209

210210
- For the first time, Env is recommended to go to the official website to download the latest version of the Env tool. The new version of Env will have better compatibility and also support automatic update commands.
211211
- You can use the Env built-in command `pkgs --upgrade` or `pkgs --upgrade-force` (recommended to use) to update the package list and Env's function code to minimize the problems you have fixed.
212212
- Do not have Chinese or spaces in the routes of Env.
213213
- Do not have Chinese or spaces in the routes where the BSP project is located.
214214

215-
## FAQs
215+
# FAQs
216216

217-
### Q: It prompts that the git command cannot be found.
217+
## Q: It prompts that the git command cannot be found.
218218

219219
'git' is not recognized as an internal or external command, possible program or batch file.
220220

221221
**A:** Git is not installed. You need to install git and add environment variables.
222222

223-
### Q: It prompts that the CMD command cannot be found.
223+
## Q: It prompts that the CMD command cannot be found.
224224

225225
**A:** Right-click–>> Property—>> Advanced System Settings—>> Environment Variable, Add `C:\Windows\System32` to system environment variables.
226226

227-
### Q: Prompt "no module named site" when running python.
227+
## Q: Prompt "no module named site" when running python.
228228

229229
**A:** Computer right button –>> Properties—>> Advanced System Settings—>> Environment Variable, in the user variable of the administrator, create a new variable named PYTHONHOME, and the variable value is: `F:\git_repositories\env\tools\Python27` (the installation route of Python in Env), do not add ";" afterwards, otherwise it will be invalid. If add PYTHONHOME can not solve theproblem, try to add PYTHONPATH in the same way.
230230

231-
### Q: What types of projects can I generate under Env?
231+
## Q: What types of projects can I generate under Env?
232232

233233
**A:**
234234

235235
1. Currently, you can use the scons tool to generate mdk/iar projects under Env. There is no automatic generation of eclipse projects.
236236
2. Generally, using gcc's toolchain, using an editor such as source insight or VS Code to edit the code and compile with `scons` command.
237237

238-
### Q:How can my own BSP support menuconfig?
238+
## Q: How can my own BSP support menuconfig?
239239

240240
**A:** You can refer to this chapter **Use Env in Your Project**.
241241

242-
### Q: What is the difference between the pkgs --upgrade/--upgrade-force command and the pkgs --update command?
242+
## Q: What is the difference between the pkgs --upgrade/--upgrade-force command and the pkgs --update command?
243243

244244
**A:**
245245

246246
1. The `pkgs --upgrade/--upgrade-force` command is used to upgrade the Env script itself and the list of packages. You cannot select a recently updated package without the latest package list.
247247
2. The `pkgs --update` command is used to update the package itself. For example, if you selected json and mqtt packages in menuconfig, you did not download them when you exit menuconfig. You need to use the `pkgs --update` command, at which point Env will download the package you selected and add it to your project.
248248
3. The new version of Env supports the `menuconfig -s/--setting` command. If you don't want to use the `pkgs --update` command after replacing the package, configure Env after using the `menuconfig -s/--setting` command. Select each time you use menuconfig. After the package is automatically updated.
249249

250-
### Q: Prompt "can't find file Kconfig" while using menuconfig.
250+
## Q: Prompt "can't find file Kconfig" while using menuconfig.
251251

252252
**A:** The Kconfig file is missing from the current working BSP directory. Please refer *To Add menuconfig function to New Project* and *To Add menuconfig function to Old Project*.
253253

254-
### Q: There's unintelligible texts appear in Env.
254+
## Q: There's unintelligible texts appear in Env.
255255

256256
**A:** First check if there is a Chinese route.
257257

File renamed without changes.

0 commit comments

Comments
 (0)