DLL 'ChronoEngine.dll' in package Chrono is not installed properly

[Halvor Aslaksen]

Hi!

I am new to Project Chrono, and was wondering about an error I get when trying to build a project. Just as a test case, I am running the template_project with the pendulum in the chrono directory.

The first time I built this project, everything went fine (irrlicht-1.8.5). Though after experimenting with installing some modules and then reinstalling the base version of chrono::engine with irrlicht and postprocess, I got these errors in CMake when trying to configure the same project again:

DLL 'ChronoEngine.dll' in package Chrono is not installed properly

DLL 'ChronoModels_robot.dll' in package Chrono is not installed properly

DLL 'ChronoEngine_irrlicht.dll' in package Chrono is not installed properly

DLL 'ChronoEngine_postprocess.dll' in package Chrono is not installed properly

I have tried to uninstall everything and reinstalling many times, trying different versions of irrlicht (1.8.5 and 1.8.4) and different changes.

Would anyone know what might cause this problem?

Any answers would be appreciated.

[Dario Mangoni]

Hi,
did you make sure that both your project and Chrono were built with same configuration type?
We are currently rewriting the files that are used for linking from external projects so this info might change in the very next future, but as for now I would recommend you to compile both Chrono and your project in Release.

Let us know,
Dario M.

[Halvor Aslaksen]

Hi Dario!

Thanks for the quick reply.
I built the chrono build directory with only Release. Though when I try to build the project from the generated project (with the error messages listed) with Release, I can't open the exe-file. It says that the ChronoEngine_irrlicht.dll and ChronoEngine.dll files were not found. 

I had no problem with generating and building projects before, and can't figure ou what has changes since the last time it worked. I've noticed that there are more options in the CMake configuration of the Chrono::Engine now, for example the USE_EIGEN_OPENMP, which is checked automatically. I don't know if this is relevant.

Halvor

[Radu Serban]

Hi Halvor,

 

Following up on Dario’s comments and if you are using the latest code in the Chrono ‘main’ branch, to make sure you deal properly with the changes to the build system we made recently, I suggest trying reconfiguring and rebuilding both Chrono and then the template project starting from scratch, in new build directories.  Or at least delete the CMake cache first.

 

You should have no issues building everything like before, provided you do not change some of the new CMake variables from their default values (which reproduce the previous setup, namely building Chrono shared libraries and using the dynamically-linked runtime library (on Windows)).  The USE_EIGEN_OPENMP option has been in there for a while and is likely not related to your issue.

 

--Radu

--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/9dd74fe6-a602-4f60-b708-fdde629ca821n%40googlegroups.com.

[Halvor Aslaksen]

Hi Radu!

I've tried rebuilding both Chrono and the template project with only release, and I still get the same error as before. The error says it calling back to the chrono-config.cmake, on line 561. I've now tried editing the file itself, changing the path from "E:/Build/chrono/bin" to "c:/workspace/chrono_build/bin", with Prefix: Release. This actually made me able to build the project, and I could now view the exe. Though I suspect this isn't a very effective fix, and that I might have problem with this down the line.

Do you know anything about why  "E:/Build/chrono/bin" was written in the chrono-config.cmake made from the chrono build?

Halvor 

[Dario Mangoni]

Oh yes, I found this error also in my code! I fixed it in my local copy and it will be pushed soon. I forgot about it.
@Radu, it's actually quite strange: if I look at the log for the cmake/chrono-config.cmake.in it does not seem that the line was changed but I found that also on my pc there was this hardcoded "E:/Build/chrono/bin" (I think it's your path!)

Anyway, it will be changed soon.
Thanks Halvor for the feedback.

Dario

[Radu Serban]

Yes, I introduced this bug.  Copying stuff from the generated configuration script into the template while I was making those changes…

Of course, I didn’t find any problems when I was testing this on my machine (that path works fine for me!) and this is not something that is tested during CI (we should think about adding a test for this).

Dario, please push the fix as soon as you get a chance.

 

Thanks,
Radu

To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/3d0c0af4-1171-4dc1-9c4e-48b83b36c4a8n%40googlegroups.com.

[Halvor Aslaksen]

Thanks for the help and quick feedback Radu and Dario!

[Radu Serban]

Hi Halvor,

I just pushed the fix to chrono-config.cmake.in.  Please let us know if reconfiguring Chrono resolves the issue you reported.

Thanks for pointing this out.

To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/c9486ea6-c7c9-4acb-9eb0-cd3ec369fda9n%40googlegroups.com.

[Halvor Aslaksen]

It seems that everything is working now! Thank you!