Hi Chris,
This is a bug that was introduced recently in an attempt to formalize the installation directories to use standard targets on a *nix system. Unfortunately, that broke the installed demos which cannot find the installed Chrono data files.
We will work on a proper fix for this.
Thanks,
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 post to this group, send email to projec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Chris,
I just pushed a fix to this issue. With this, the various
install directories should be as follows:
--
When you run from within Visual Studio, you must properly set the "Working Directory" which is by default $(ProjectDir):
Unfortunately, this property is not stored in the Visual Studio
project files, so there is no way to set it through CMake.
--Radu
Shubhankar,
The mention of CHRONO_DATA_DIR indicates that your situation is not the same as the one I discussed in that reply back in 2017.
You are building a separate project and link to the Chrono libraries. Based on what you get for CHRONO_DATA_DIR, I take it you are linking against the Chrono build directory, as opposed to an install directory. In this case, it is indeed intended to point to the data/ directory in the Chrono source tree.
You must make an explicit call to the function chrono::SetChronoDataPath() and pass it the path contained in that CMake variable. See my_example.cpp in the Chrono distribution (under “template_project”).
If you already do this, there must be some other problem. You mention “some parsing issues while building”. Could you provide more details? Maybe it has to do with the space in this path, within “Chrono Workspace”.
--Radu
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/b53fac39-0dcf-4e48-8106-0cbee5730f2cn%40googlegroups.com.