Create a new. txt file. Enter the following content in it:
Del *. bak/s
Del *. DDK/s
Del *. EDK/s
Del *. LST/s
Del *. LNP/s
Del *. MPF/s
Del *. MPJ/s
Del *. OBJ/s
Del *. OMF/s
: Del *. Opt/S: jlink settings cannot be deleted.
Del *. PLG/s
Del *. Rpt/s
Del *. tmp/s
Del *. _ I/s
Del *. CRF/s
Del *. o/s
Del *. D/S
Del *. axf/s
Del *. TRA/s
Del *. dep/s
Del jlinklog.txt/s
Del *. iex/s
Del *. htm/s
Del *. SCT/s
Del *. MAP/s
Exit
Then, close the. txt file and change the suffix to. bat. Then copy the. BAT file to the main folder of one of our routines, as shown in (my name is keilkill. BAT ):
Then we open the project in the user and compile it once. We can see N more junk files (250, total size nearly 20 m), as shown in:
Then, click keilkill. bat in the directory at the upper level. A DoS dialog box is displayed, and the pop-up dialog box will disappear. Open the user folder and check it out, as shown in:
At this time, we found that many of the files have been killed, and only a few useful files are left. the total size is 232kb, much less than before. now, you can package the folder and send it to others, which can save a lot of traffic. it can also save space on your hard disk.
What's amazing about. bat? You can use a text tool to open it as needed. BAT file, add or delete some statements in it to suit you. of course, the premise is that you are right. BAT must have a little understanding. specific Learning,HereFor more information, see. the flexible use of BAT to help us do things can save a lot of repetitive work. if you have time to learn more, I also read it last night. I think it is very good. I will introduce it to you here.
(Transcription openedv)
Use. BAT (batch processing) to delete useless files generated by Keil Compilation