Reference article

【1】RT-Thread User's Manual

1 About SCons Building tools

Manual No 10 This is how the chapter describes it ：SCons It's a set of Python Open source building system written in language , Be similar to GNU Make. It uses different from the usual Makefile Of documents SConstruct and SConscript file . These documents are also Python Script , Be able to use standard Python Grammar to write . So in SConstruct、SConscript Can be called in the file Python The standard library carries out all kinds of complex processing , Not limited to Makefile Set the rules . stay SCons You can find detailed SCons User's Manual .

2 Download and install NotePad++ Text editing tools

1. Built in support for up to 27 Syntax high brightness display ( Including a variety of common source code 、 Script , Be able to support .nfo The file to view ), It also supports custom languages ;
2. Automatic detection of file types , Display nodes according to keywords , Nodes can be folded freely / open , You can also display indented Guides , The code is hierarchical ;
3. Can open double windows , In the sub window, multiple sub windows can be opened , Display scale ;
4. Provides some useful tools , Such as Adjacent banks swap positions 、 Macro functions , etc. ……
5. The number of bytes of the selected text can be displayed ( Instead of the number of words displayed in the general editor , This in some cases , For example, software localization is very convenient );
6. Regular matching string and batch replacement ;
7. Powerful plug-in mechanism , Expanded editing capabilities , Such as Zen Coding.

3 establish RT-Thread/bsp Application branch under

【3】 Save and compile

Compilation tips ： Each time you open the command terminal and enter the command into the working directory, it is time-consuming for people who type slowly , Creating a new batch file can save some time , Copy the following content into a notepad and rename it as xxx.bat Just file it .

echo RTT bat
E:  
cd \RTT\apingrtt\rt-thread-1.2.2\bsp\stm32f103ze-ek
::pause
cmd.exe

Then you can compile .

There is an error , Here's the picture ：

And on again keil MDK Of options, Here's the picture .

Compare the system variables , It is found that there is no RT_CC, therefore rtconfig.py The judgment condition in is false , and RT_ROOT=E:\RT_Thread It needs to be revised , Because here RTT_ROOT The variable value of is RTT Source root , This variable is at the top SConstruct It is used in the document , The modification result is shown in the figure below .

And then it's running scons --target=mdk4 -s, Here's the picture .

Use... Again keil Open the project file in this directory , Then open the options, have a look , Here's the picture .

The root directory has worked .

Enter at the command terminal stim32f103zet_v5(baiwei) Under the table of contents , function scons -c, Clear previous compilation results . And then run scons recompile , give the result as follows ：

【4】 The compiled output directory is set to not receive version monitoring .

Git Files in are ignored
1. Shared ignore new .gitignore file , It can be placed anywhere in the project directory ..gitignore Files can ignore themselves . Ignored files , Only valid for untracked files , Invalid for files that have been added to the version Library .
2. Exclusive ignore specific version libraries ：.git/info/exclude For local and global ：  git config --global core.excludefile ~/.gitignore
Grammar rules ignored ：

"#" Notation ;

With a slash “/” The beginning indicates the table of contents ;

With an asterisk “*” Match multiple characters , namely "*"  Represents any number of characters ;

With question mark “?” Pass on a single character , namely "?" Represents a character ;

In square brackets “[]” Contains a list of matches for a single character ;

With exclamation marks “!” Don't ignore ( track ) The file or directory to which to match ;

 ([abc]) Represents the range of optional characters

Besides ,git about .ignore Configuration files are rule-matched from top to bottom on a line basis , That means if the previous rule matches over a larger range , Then the following rules will not take effect ;

If the name is preceded by the path separator “/”, Indicates that the file ignored is in this directory .
If the last side of the name is “/” , Indicates that the entire directory is ignored , But files with the same name are not ignored .
By prefixing the name “!”, On behalf of not ignoring .
Examples are as follows ：
# This line is a comment
*.a                   # Ignore all .a Files with extensions
!lib.a                # however lib.a Don't ignore , Even if the previous setting ignores all .a
/TODO            # Only ignore this directory TODO file , Of subdirectories TODO Don't ignore
build/               # Ignore all build/ Files under directory , Be careful , Whether it's in the root directory /build/ Catalog , Or some subdirectory /child/build/ Catalog , Will be ignored ;
doc/*.txt           # Ignore as doc/notes.txt, But don't ignore such as doc/server/arch.txt