Root > Advanced topics > Working with configurations > Storing EurekaLog options

Storing EurekaLog options

Previous pageReturn to chapter overviewNext page   

EurekaLog stores configuration in .eof files. .eof file is a UTF-8 encoded text ini-file, which can be edited in any text editor, or in specialized Settings Editor tool, included with EurekaLog.

 

EurekaLog stores base project configuration in file with same name as project file. For example, if you have Project1.dpr - then EurekaLog will save base configuration into Project1.eof file. Such file will be used by default in all cases (compilation from IDE, from command-line, etc.).

 

Additionally, you may manually create individual configurations for each profile (each build configuration). For example: Project1_Debug.eof. See Different EurekaLog settings for Debug and Release profiles for more information.

 

Note: you may create additional (external) configurations.

 

Any .eof-file different from base or profile configuration is considered to be external configuration. Default folder for saving external .eof files (i.e. folder for "Import configuration" and "Export configuration" dialogs) is %AppData%\Neos Eureka S.r.l\EurekaLog\Profiles\ (e.g. like C:\Users\UserName\AppData\Roaming\Neos Eureka S.r.l\EurekaLog\Profiles\). Any .eof file placed in that location will appear as "custom" project type.

 

 

"Project type" option shows two .eof files

 

.eof files outside of the above mentioned folder will not appear in "Project type" option. For example, base configuration of your project will never appear as custom profile.

 

Apart from %AppData%\Neos Eureka S.r.l\EurekaLog\Profiles\ folder, a typical places to store external .eof files are folder or sub-folder of your project.

 


 

Note: older EurekaLog versions stored EurekaLog options directly inside project options file:

 

DOF

Delphi 4-7

BDSPROJ

Delphi 2005-2006

DPROJ

Delphi 2007 and later

BPR

C++Builder 5-6

BDSPROJ

C++Builder 2006

CBPROJ

C++Builder 2007 and later

 

When you open such file in modern EurekaLog version - old options will be imported, saved into usual .eof file, and erased (technically, not erased: EurekaLog will simply not bother to save/write into project options file, and IDE will eventually overwrite non-standard blocks). You still can store settings in such files manually, and you can use Settings Editor tool to force-save settings into these files.

 

 

See also:




Send feedback... Build date: 2018-11-26
Last edited: 2018-06-14
PRIVACY STATEMENT
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.


Permanent link to this article: https://www.eurekalog.com/help/eurekalog/configuration_storage.php