Hi hj,
If you are familiar with Docker, to save you trouble, try to pull the image from the registry and deploy a Docker container that has Chrono ready to go.
See here: https://hub.docker.com/r/uwsbel/projectchrono .
Dan
-------------------------------------------------
Bernard A. and Frances M. Weideman Professor
NVIDIA CUDA Fellow
Director, Wisconsin Applied Computing Center
Department of Mechanical Engineering
Department of Computer Science
University of Wisconsin - Madison
4150ME, 1513 University Avenue
Madison, WI 53706-1572
-------------------------------------------------
--
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/52aa5580-988f-4a61-adbe-20a36275daa0n%40googlegroups.com.
HJ,
What compiler (I assume VS) and version do you use?
What version of Blaze do you use? Most of the internal testing is done with Blaze 3.8.
As Luning indicated, Blaze is used only in the Chrono::Multicore module and you should only enable that module until you resolve this compilation problem. If you are still getting the error messages, please also post here the output from your CMake configuration.
--Radu
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/3ff8257d-a81e-4a0d-8e6d-92b5a730a507n%40googlegroups.com.