Eurekalog 6.0.13 does not work with FinalBuilder 5.5

[erik]

We use FinalBuilder 5.5 to build with EurekaLog support. And we use the IsEurekaLogInstalled and StandardEurekaError API's to manually pass errors to EurekaLog.

Up until version 6.0.11, this worked fine, and the exception dialog would pop up on errors. However, this no longer works in 6.0.13 (and 6.0.14 RC3). When I build from within the Delphi 2007 IDE, it still works fine. But when I use FinalBuilder, it doesn't work anymore.

So I think this may be an ecc32.exe command line issue.

[admin]

Hi,

can you create and send to me a little source demo able to reproduce it, please?

[allen]

Same problem here - newer EurekaLog does not work with Finalbuilder.

I remember being asked for a "demo" sample application when the log viewer was corrupting the database. Of course the sample app didn't have any relationship to the issue and that issue was fixed eventually about 6 months later.

[admin]

Hi,

I'm really sorry but I have just try the last EurekaLog 6.0.14 RC 5 with the last FinalBuilder 5.5 version and all seems to works fine.

Can you create and send to me a little source demo able to reproduce this issue, please? :(

[erik]

After some further investigation, I noticed that the problem only occurs when the "Compile" action in the FinalBuilder project outputs the Exe to a different directory than specified in the project file.

For example, the project file has no specific output directory set. But the Compile action in FinalBuilder has the output directory set to a specific directory (since we want to deploy from another directory than the one we use for internal testing).

If you use FinalBuilder to build the project with a specific output directory, then exception logging will not work. If you clear the "Output directory" field in you FinalBuilder Compile action, then everything works fine.

I'll send you a sample project that shows this behavior.

Erik

[admin]

Hi,

perfect I have finally found and fixed this issue in the last EurekaLog 6.0.15 RC 1.

Try it and tell back to me your result, OK? :)

[Unregistered]

Hi,

Thanks for the quick response... and the fix.
It works perfectly again now.

[admin]

Perfect! :)

[mariella]

I experienced the same problem using FB and EurekaLog. Downloading the latest EurekaLog version (6.0.15 RC) did the fix. However, it is now no longer possible to rename executables. For me this is a problem as executables are installed on client computers with a different filename than the filename we use when building.

Previously we did not have any problems. Can someone of EurekaLog please comment on this?

[admin]

Hi,

how I can reproduce the "Rename" problem with the last EurekaLog version?

[mariella]

Hi,

how I can reproduce the "Rename" problem with the last EurekaLog version?

Compile an executable. After compilation, rename the executable (In Windows Explorer or any other app). When running the executable, EurekaLog will not be enabled.

[mariella]

Were you able to reproduce it yet?

[admin]

Hi,

really, really strange.

I have compiled a D2007 project with FinalBuilder 5.5 and EurekaLog 6.0.15 RC 1, after I have changed the .EXE name and executed it.

All works fine.

How is this possible?

[mariella]

Hi,

really, really strange.

I have compiled a D2007 project with FinalBuilder 5.5 and EurekaLog 6.0.15 RC 1, after I have changed the .EXE name and executed it.

All works fine.

How is this possible?

I tested again and was not able to reproduce the behaviour. I might have been wrong, probably it was even originally not working.

It turned out that the .dproj file had EurekaLog not activated. I still do not understand why executables built from the IDE still have EurekaLog enabled and executables built with Finalbuilder not, but it has been resolved.

Thanks for your support.

Kind regards,
Mariëlla

[admin]

Hi,

you're welcome! :)