Various types of files in Delphi

The 1.dpr:delphi project file contains the Pascal code. Engineering files for Application Systems
2.pas:pascal file, the source code of the Pascal unit, can be either a form-related unit or a separate unit.
3.dfm:delphi form file, a binary file that describes the properties of a form or data module and its components. Form interface file with the same name as the Pas file, and
and one by one corresponds, defines the properties of the form properties and artifacts,
4.BPG Borland Project Group Project package, DPR collection of multiple project files
5 (). DOF Delphi option file, including compilation information, is a text file piece that you can look at
6 (). CFG Project configuration file compiler readable profile
7 (). DSK Desktop Setting file saves the desktop at the mercy of the project file, the last saved desktop state can be restored the next time you open
8 (). DSM integrated development Environment IDE's temporary save file, sometimes the IDE always error, you can delete this file, the system will regenerate
9.RES Resource File Windows resource files, you can define the cursor, bitmap, icon resources, you can use Imageeditor edit
(There are some examples in the blog)
10.DCU Delphi Compile Unit compiled cell file, which is required when the program is connected
11.DLL dymanic-link Libraries Windows dynamic link library
12.EXE executable file compilation of generated executables
source code for 13.DPK Delphi packge source package file
14.BPL Borland Package Library, a special DLL file for code reuse and reducing the length of executable files
(). ~*: Delphi-generated backup files should not appear in the version control Library///And in the release code, and you can try using these files if you modify a file for some reason and do not save it.
16.bmp/wmf/emf/gif/jpg/pcx/png/tiff/ico/cur/ani: Graphics/icons/cursor files, these files need to be in the source code library if they are used.
(). BPG: Project group file (Borland project), text format, need to enter the source code library, BPG file is actually makefile format//?makefile format, to compile BPG file can use make tool// ?, the syntax is as follows:
make-f%filename%
18.BPL: Runtime package file, is a Borland definition of the special format of the DLL, simply said that the difference between the common DLL is BPL some common parts only use the same reference, and DLL uses multiple copies, So the difference between the BPL and some aspects of the DLL is very significant.
whether this type of file into the source code base needs to be judged according to its purpose, in general, the source code compiled BPL do not need to enter the library, but if this BPL is the IDE's extension, you may also need to enter the library, in addition, if the third-party component does not provide the source code only provides this file, then this file will need to
Bpr/bpf/bpj/h/cpp; BCB (Borland C + + Builder) related files, if the project uses BCB, you need to go to the source code base, but we should not need these files in our project.
(). Cab:activex Control Package file, if it is a third-party control used by the project, you need to enter the source code library.
20.cfg: The configuration file when compiling the project. The Dcc32.exe program compiles the project using the CFG file in the order of: first use the Dcc32.exe with the Dcc32.cfg file in the same directory, and then use the file to be compiled with the dcc32.cfg file in the same directory, and finally use the same name as the file to be compiled with the same CFG file, In order to ensure the identity of the results compiled in different machine environments, this file needs to be in the source code repository.
(). Dci:code insight files, which save code templates, typically do not need to be in the source code library.
DCP: A binary image file containing the header information of the package and the Dcu/dpu file of the unit file in the package, the difference between the DCP and the BPL can be understood by the difference between DCU and Dll/exe, Delphi compiles the package's DCP files for use with the package's files, which can be generated from the source code, generally without the need to enter the source code base.
(). dct:component template file, if the project uses the Component template, you need to enter the source code base.
24.DCU/DPU: The binary image file corresponding to the unit, DPU is the DCU format under the Linux system. DCU/DPU is a binary intermediate format for PAS, and the corresponding DFM/XFM file is not linked into DCU/DPU. In general, you do not need to enter the source code library unless it is provided in the DCU form of a third-party library.
(). ddp/dti:D iagram file. Delphi 7 provides the diagram feature, which can be used in a graphical description in a cell file, which has no effect on compiling the source code, but if the diagram feature is used, this file may be useful for understanding the unit, and in our project it should not need to be in the source code library. Even if these files are available, it may be because the switch to the Diagram page card was generated.
26.dfm/xfm: Form file. Xfm is the form file used by the cross platform source code. DFM/XFM has two formats, one is a binary format, one is a text format, in order to facilitate version control, need to use text format, text format also has a variety of formats, DELPHI7 text format DFM/XFM save such as Chinese, such as the use of Unicode encoded values, and Delphi7 before the use of the direct is ANSI,DELPHI7 support to open the original format of the DFM file. Need to enter the source code base.
27.dll/so: Dynamic link library file. So is a dynamic link library file under Linux. If it is compiled dll/so file, do not need to enter the source code base, if the project is used to the third party libraries needs to enter the source code base.
(). Dmt:menu template files, generally without the need to enter the source code base.
29.dof/kof:D elphi option files (Project options file) when compiling the project, KOF is a DOF file under the Linux platform. This file contains information about the project->options of Delphi, as well as information about the compilation configuration, including directories, links, versions, conditional switches, and so on. In general, DOF is a superset of the same name CFG file (the DOF is not the same as the CFG format). Text format, in order to ensure the identity of the results compiled in different machine environments, this file needs to enter the source code base.
30.DPC/PCE: Package collection File and package collection edit file. Delphi supports the incorporation of multiple packages into one file, which makes it easy to distribute multiple packages to other developers using this format to easily configure the IDE environment. This file needs to be in the source code library.
31.dpk/dpkw: Package file. DPKW is a dpk file under a cross-platform. The package file lists the packages that the package contains, the package that the package depends on, and the package description information, package compilation options, and so on. Text format, need to enter the source code base.
32.DPR: Engineering documents. Text format, need to enter the source code base.
33.DRC: Package resource files that provide the resources needed for packages such as component icons. Binary format, if the DCR used by the package is required to enter the source code base.
(). drl/dro:repository file. Delphi provides repository features that enable developers to share development templates, use repository functions rationally to speed up development, and develop groups to configure shared repository to use repository. If you do not use the repository feature, you do not need to enter the source code base.
35.dsk:D esktop file. Saves the IDE's layout (which may also include a browse mark, depending on the IDE's settings), to prevent the developer from setting the IDE layout. Text format, this file should not be entered into the source code library.
36.exe: Executable file. such as non-third-party components, no need to enter the source code base.
37.hlp/cnt/toc/chm: Help file. Need to enter the source code base.
(). IDL: Interface Definition language file. IDL defines interfaces, and COM and CORBA development are often used in IDL. Text format, need to enter the source code base.
39.inc:include file. Not the same as the C + + include. Can be embedded in the Delphi source code file, Delphi compilation is when $i to include files equivalent to copy an inc file content to the current location, generally used to extract some duplicate each cell needs to define the content, or to define a common compiler indicator word condition, You can even use the Delphi Inc mechanism to implement the C + + paradigm (unfortunately, operator overloading is not supported). Text format, need to enter the source code base.
(). Inf/reg: Registration file. Text format, need to enter the source code base.
41.ini: Initialize the configuration file. If this is the initial configuration file, you need to go to the source code base, if it is a run-time generated configuration file, you do not need to enter the source code base.
42.int: The interface section of the unit defines the file. A file that extracts the interface portion of a Delphi unit, such as a C + + header file, but is only defined for the Developer Reference Unit interface and does not participate in compilation. Text format, no need to enter the source code base.
() Lib: Import the library file. For C + + use of DLL import library files, Delphi does not need Lib files. If you need to use some DLLs for C + + developers, you need to provide the appropriate LIB file. into the source code library.
44.log: Log file. Text format, no need to enter the source code base.
(). Map: Executable file layout file. Text format, no need to enter the source code base.
46.mdb/dbf/gd*/db/mdx/dbt/ndx/mb/val/qbe/px/x*/y*: Desktop database file. According to the engineering decision whether to need to enter the source code base.
47.obj/o: Target file. Binary format, such as the source code "linked to the target file, need to enter the source code base."
48.ocx:activex the control file. Binary formats, such as third-party controls used for source code, need to be in the source code library.
49.pas: Unit file. Text format, need to enter the source code base.
50.rc: Resource script file. Become a res file after compiling with Brcc32.exe. Text format, need to enter the source code base.
51.res: Resource file. Contains the program's main icon, string table, icon, graphics, and so on. binary format, need to enter the source code base.
(). RPS/DFN: Multi-lingual translation documents. Delphii de provides a multi-lingual support mechanism. DFN is a binary format, and if the project is internationalized with this mechanism provided by Delphi, these files need to be put into the source code repository.
(). RSM: Debug symbol information file. Some additional debugging tools require debugging symbolic information, and if you want to support these tools, you need to provide an RSM file. Binary format, no need to enter the source code base.
(). sql/tql:sql statements and SQL template files. binary format, need to enter the source code base.
(). STAT: Engineering Statistics information file. Text format, no need to enter the source code base.
(). TDS: External debug Symbol table file. No need to enter the source code base.
(). Todo:todo list file. No need to enter the source code base.
58.UPG: Upgrade information file. No need to enter source code
 
59.DDP: File is the Delphi Diagram portfolio Shorthand, is used to save the Code Editor diagram//information. Generally a project to test individual only need Dpr,dfm,pas file, if there is cfg,res also a test (after two files rarely used)
60.dof: For Project Options file (generally useless).

Various types of files in Delphi (RPM)