Eurekalog and Packages

[Marius]

I'm rebuilding a couple of projectgroups with ~100 packages
(recompiling a part of my package collection).

But because Eurekalog is by default enabled it tries todo something
with the bpl after the compilation and that seems to be conflicting
with the ide. Is there any chance i can quickly deactivate eurekalog
for all packages (which you normally do with project -> eurekalog
options -> uncheck activate Eurekalog)?

Basicly i only want Eurekalog activated for my executables and dll's
but not for dpk's, is there an option i can use to do this (could not
find it)? If not, could this behaviour be implemented as a feature in a future version?

Thanks,
Marius

[Alex]

Hi,

Which version of Delphi do you use?

I think that you can delete project configuration files and replace them with default ones (with EurekaLog enabled). Alternatively, you can just delete them and disable EurekaLog by default. After configuration files will be recreated, you can turn EurekaLog back on.

There is no option for selectable activation on project and it is not in our suggestion list yet. Do you really think that it'll worth it? From my POV, it is much simplier to manually turn EurekaLog on/off for every new project. How are you going to configure it? Should console, service or VCL application have the same settings? How about stand-alone DLL or package, which are going to be used in your EurekaLog-enabled application, and ISAPI DLL or some other kind of plugin-DLL, which will be used in non-Delphi application?

There are all different requirements.

P.S. Don't forget about import/export buttons too ;)

[Marius]

Which version of Delphi do you use?

Delphi 7 (but slowly upgrading to 2010)

I think that you can delete project configuration files and replace them with default ones (with EurekaLog enabled). Alternatively, you can just delete them and disable EurekaLog by default. After configuration files will be recreated, you can turn EurekaLog back on.

I'm afraid i cannot delete them as they all contain additional output
paths for the bpl's and dcu's (different then the standard compiler
configuration).


From my POV, it is much simplier to manually turn EurekaLog on/off for every new project.

Eureka is now default on, i could reverse it though, never thought
about that ;)
Think i'll go this way as its much easier then configuring all those
dpk's <g>

How are you going to configure it? Should
console, service or VCL application have the same settings? How about stand-alone DLL or package, which are going to be used in your EurekaLog-enabled application, and ISAPI DLL or some other kind of plugin-DLL, which will be used in non-Delphi application?

You got a point there, on the other hand mayby your thinking to
difficult, i had just in mind to enable eurekalog if the project
extension is .dpr and disable it when its .dpk.

There are all different requirements.

P.S. Don't forget about import/export buttons too ;)

I never used those buttons or any of the dialog options (other then
activate <g>), i configure all the options via code instead of the
dialog (so i can just use a shared unit and have the same set of
options in all my projects, this is just easer then having (problably different) setups in all our programs and tools).

Greetings,
Marius

[Alex]

You got a point there, on the other hand mayby your thinking to
difficult, i had just in mind to enable eurekalog if the project
extension is .dpr and disable it when its .dpk.
May be you are right. Packages are somehow special from other types of project. We need to think about it.
I've added this to our suggestions list.