DLL profile includes the following options:
(bold lines are mandatory for profile; normal lines are optional - they are set by default, but can be altered later)
This profile is for DLL which is supposed to be used in any EurekaLog-enabled application. No EurekaLog code will be injected in this project. Only EurekaLog's data will be injected into target DLL file.
You should install host callbacks into DLL, if you want to handle exceptions in DLLs with creating EurekaLog bug reports - so DLL can call into host and ask it to create bug report. EurekaLog offers EAppDLL unit for this task (see Delphi example in this article). Non-Embarcadero DLLs should implement a similar service OR handle exceptions by themselves (without EurekaLog's assist).
Note: your project must be DLL, not exe.
1. DLL profile is designed to exclude EurekaLog code from executable. This means that most EurekaLog options will have no effect for a project with DLL profile. For example, dialog settings will be ignored, since there is no dialog code in DLL compiled with this profile. Dialog code will be in EurekaLog-enabled host. Thus, you should adjust options of the host. However, some options will still affect DLL. For example, application type hooks (such as VCL forms, etc.), memory manager, compilation options, and debug information options.
2. Do not include EurekaLog units into project compiled with DLL profile. This is not supported and may have unexpected results. In particular, do not link DLL project with EurekaLogCore run-time package.