File Extensions of Files Generated by RAD Studio

From RAD Studio
Jump to: navigation, search

Go Up to File Types Index


The following table lists the extensions of files generated by RAD Studio.

Note: MSBuild requires that the extension for all project files end in 'proj' (that is, MSBuild uses the mask *.*proj).

The following table explains the different values of the "Keep in VCS?" column of the table above:

Value Description

Yes

You must keep this file under version control.

No

You should not keep this file under version control.

Optionally

You can keep this file under version control if you want all your team to use it, but you can also keep it to yourself.

For example, if you want all your team members to use the same CodeGuard options for your project, you can keep the generated .cgi file under version control. If you want to let each team member to have their own CodeGuard settings for your project, do not add the .cgi file to your version control system.

Unless buildable

You should only keep this file under version control if the file is required to build your application and your project does not build it.

For example, you must keep binary library files from third parties if you do not have their sources or if your project does not build those libraries. However, if your project builds a library, you do not need to keep the resulting binary of that library in your version control system.

File Extension Description Keep in VCS? 
a

Static library file (ELF-format) produced by either the Clang-enhanced C++ compilers or the BCCOSX compiler, such as package static library files.

For more information, see:

Unless buildable 

apk

Android application package file. See Deploying Your Signed Android Application.

No 

bdsproj

Project options file for BDS 2006 and earlier (replaced by .dproj and .cbproj).

Yes 

bdsgroup

Project group for BDS 2006 and earlier products.

Yes 

bpi

Package import library file.

Unless buildable 

bpl

Package shared library file.

No 

cbproj

C++ project file. Contains the current settings for project options, such as compiler and linker settings, directories, conditional directives, and command-line parameters. (Set these options using Project > Options.) When compiled, produces .exe, .dll or .ocx file.

Yes 

cfg

Project configuration file used for command-line compiles, as follows:

  • dcc32.cfg is for dcc32.exe
  • dcc64.cfg is for dcc64.exe
  • dccosx.cfg is for dccosx.exe

For 32-bit Windows, for example, the Delphi compiler searches for a dcc32.cfg in the compiler executable directory, then for dcc32.cfg in the current directory, and then finally searches for projectname.cfg in the project directory. You can type dcc32 projectname on the command line and compile the project with the same options specified in the IDE.

Optionally 

cgi

The CG32.cgi file is the configuration information for CodeGuard, a utility used for tracking memory overwrites in statically linked C++ executables. See Using CodeGuard.

Optionally 

cgl

CodeGuard generates a log file, <project_name>.cgl. See CodeGuard Overview.

No 

cpp

C++ implementation file.

Yes 

csm

C++ precompiled header file in earlier versions of C++Builder, such as C++Builder 5.

Optionally 

d

C++ dependency file.

No 

dcp

Delphi compiled package file.

Unless buildable 

dcu

Delphi compiled unit file.

No 

dct

Any change to component templates that you make on RAD Studio is stored in C:\Users\<username>\AppData\Roaming\Embarcadero\BDS\19.0\bds.dct.

No 

deployproj

Deployment Manager configuration file for your project.

Yes 

dfm

A Windows VCL form file.

Yes 

dll

A dynamically linked library file. For more information, see Creating Packages and DLLs.

Unless buildable 

dpk

Delphi package source file.

Yes 

dpr

Delphi project source; when compiled, produces .exe, .dll, or .ocx file.

Yes 

dproj

Delphi project file created by the IDE. Contains the current settings for project options, such as compiler and linker settings, directories, conditional directives, and command-line parameters. Set these options using Project > Options. This file is not used when compiling a project from the command line using the command line compiler.

Yes 

drc

Delphi resource string file.

No 

dres

Delphi compiled resource file. This extension is used when you add a resource to a project, such as an icon or image. The .dres file is only used at link time.

No 

dsk

File used to save the project desktop when the Autosave Project desktop option is enabled on Tools > Options > Environment Options.

No 

dst

File used to save the desktop speed setting as set in the IDE toolbar desktop combo box.

No 

dSYM

dSYM debug file.

Unless buildable 

dylib

A dynamic library (.dll) or a package (.bpl) compiled for the OS X platform. See Multi-Device Applications Index and Output Files for Multi-Device Targets.

Unless buildable 

dylib.rsm

Remote debug symbol file for Delphi for OS X. See .rsm.

Unless buildable 

entitlements

Apple application entitlement file.

No 

exe

Windows executable file.

Unless buildable 

exe.incr

Incremental build information.

Unless buildable
Optionally 

fmx

Multi-device form file. See Creating a FireMonkey Application.

Yes 

fsf

FireMonkey binary style file. Similar to .style file. See Customizing FireMonkey Applications with Styles.

Unless buildable 

groupproj

Project group.

Yes 

h

C++ header file.

Yes 

hpp

C++ header file.

Yes 

i

C++ preprocessor output (not saved by default). Each C++ implementation file and all of its included C++ header files are preprocessed into an .i file.

No 

identcache

Information used for refactoring.

No 

ilc
ild
ilf
ilr
ils

C++ incremental linking state file.

No 

info.plist

Apple application information file.

No 

ipa

Application archive file for an iOS app. Generated for the Ad hoc and the Application Store platform configurations. See Deploying Your iOS Application for Ad hoc Distribution and Deploying Your iOS Application for Submission to the App Store.

No 

lib

Can be any of the following:

Unless buildable 

local

User-specific project options.

No 

map

Map debug file.

No 

nfn

A file maintained by the Translation Tools, containing translated strings and other data displayed in the Translation Manager. There is a separate .nfn file for each form in your application and each target language.

Optionally 

o

C++ object file or compiled translation unit.

Unless buildable 

obj

C++ object file or compiled translation unit.

Unless buildable 

ocx

OLE Control eXtension (OCX), created by the Active Form wizard.

Unless buildable 

optset

Named option set file that stores configuration options, separately from projects. See Option Sets Overview.

Yes 

otares

File with unknown resources generated during upgrade of pre XE2 project. (Unknown resources are resources that are not included in the build configuration, like version info, icon, manifest or styles.)

Yes 

pas

Delphi source file.

Yes 

pch

C++ precompiled header file.

Optionally 

pdi

C++ package dependency information file.

No 

plist

Property list file. Property lists are generated for the OS X, iOS Device - 32 bit, iOS Device - 64 bit, and iOS Simulator target platforms. See Compiling and Building Multi-Device Applications.

RAD Studio generates the following property list files:

No 

profile

A connection profile that describes the connection to the Platform Assistant running on a remote system, for multi-device application development that targets either the OS X or the iOS target platform.

No 

res, rc

Compiled and uncompiled resource files.

Unless buildable 

ridl

Restricted Interface Definition Language. Text-based file used by the Type Library Editor.

Yes 

rps

Legacy extension for an ITE/ETM translation repository; supported for read-only access. Translation repositories are now saved as .tmx files.

Optionally 

rsp

Response file used by the C++ linker.

Yes 

rsm

RSM debug file, used for remote debugging in Delphi projects. Enabled by the Include remote debug symbols option on Project > Options > Delphi Compiler > Linking.

Unless buildable 

sdk

An SDK that describes a target platform, and a combination of files needed to build applications for that platform.

No 

so

This is the file extension of shared libraries in Unix-like systems such as OS X and Linux.

When you build a multi-device application for Android, RAD Studio generates a shared library with this file extension that implements the project logic, as Android is based on Linux.

Unless buildable 

stat

RAD Studio saves the Project Statistics when you close the project to the file <ProjectName>.stat. You may keep this file in the version control if you want to.

Optionally 

style

FireMonkey style file. See Customizing FireMonkey Applications with Styles.

Yes 

sym

Symbol file. C++Builder uses tlibimp.sym to map symbol names in type libraries. For more information, see Mapping Symbol Names in a Type Library.

Yes 

targets

Targets file, an MSBuild-compliant XML file you add to your project to allow customizing the build process. It contains MSBuild scripts among other information.

Yes 

tds

TDS debug file.

Unless buildable 

tgproj

Modeling design project.

Yes 

tlb

Type library.

Unless buildable 

tmx

The Translation Repository stores data in a .tmx file in XML format. You can maintain more than one repository by saving multiple .tmx files. See Translation Manager in the IDE.

Optionally 

todo

The project to-do list.

Yes 

tvsconfig

Modeling configuration file.

No 

txvpck, txvcls

Information for model diagram.

Yes 

vsf

VCL style file, enabled in Application Appearance page.

Yes 

vlb

Visual LiveBindings file. See LiveBindings Designer.

No 

xml

XML is a markup language for data files. The following list contains some examples of XML files that RAD Studio generates:

Optionally 

#nn

Here #nn = #00, #01, #02, and so forth. C++ debug type file.

Unless buildable

See Also

Retrieved from "http://docwiki.embarcadero.com/RADStudio/Tokyo/e/index.php?title=File_Extensions_of_Files_Generated_by_RAD_Studio&oldid=266953"