Just a preliminar question: you said you enabled "all" the modules. Given the amount of errors looks like you really enable many... but* do you really need them*? You need URDF, VSG, MUMPS, MULTICORE, all enabled?
In general I would recommend to *enable ONLY those modules that you really need*. As Huzaifa pointed out, (almost) every module comes with one or more dependencies that you have to satisfy. The buildScripts surely help in configurin the project but even with the build scripts some additional effort is required. Il giorno lunedì 6 novembre 2023 alle 16:23:45 UTC+1 [email protected] ha scritto: > Hello, > > Have you added the path to external libraries in your cmake GUI? > > For example, for vsg, see point 3 under "Building Instructions". > https://api.chrono.projectchrono.org/module_vsg_installation.html > This is also the same for the parsers module > https://api.projectchrono.org/module_parsers_installation.html > > > On Monday, November 6, 2023 at 5:19:02 AM UTC-6 [email protected] wrote: > >> hello， >> I had some problems building chrono again, >> First, my environment is configured under windows11 and CMake3.27.4 >> versions >> I expect all modules plus build to be successful, but now I have >> encountered the following problems >> >> 1. Parsers module: Package urdfdom NOT found. The Chrono URDF parser will >> NOT be built. (Here I have built with contrib\build-scripts, but this error >> is reported.) >> >> 2, Chrono VSG module: CMake Error at src/chrono_vsg/CMakeLists.txt:28 >> (find_package): >> By not providing "Findvsg.cmake" in CMAKE_MODULE_PATH this project has >> asked CMake to find a package configuration file provided by "vsg", but >> CMake did not find one. >> Could not find a package configuration file provided by "vsg" with any of >> the following names: >> vsgConfig.cmake >> vsg-config.cmake >> Add the installation prefix of "vsg" to CMAKE_PREFIX_PATH or set "vsg_DIR" >> to a directory containing one of the above files. If "vsg" provides a >> separate development package or SDK, be sure it has been installed. >> (Here, too, I built the library using the scripts in >> contrib\build-scripts.) >> >> 3, Chrono Distributed module: >> CMake Warning at src/chrono_distributed/CMakeLists.txt:18 (message): >> Chrono::Distributed requires MPI, but MPI not found; disabling >> Chrono::Distributed >> (I've enabled the MULTICORE module here, and I've done this with the >> Multicore Module.) >> >> 4, Chrono Engine Mumps module >> Searching for MUMPS... >> CMake Warning (dev) at src/chrono_mumps/CMakeLists.txt:41 (find_package): >> Policy CMP0144 is not set: find_package uses upper-case < >> PACKAGENAME> _ROOT >> variables. Run "cmake --help-policy CMP0144" for policy details. Use the >> cmake_policy command to set the policy and suppress this warning. >> CMake variable MUMPS_ROOT is set to: >> D: / Program Files/Chrono/library/MUMPS_5. 1.2 >> For compatibility, find_package is ignoring the variable, but code in a >> .cmake module might still use it. >> This warning is for project developers. Use -Wno-dev to suppress it. >> Mumps not found. >> MUMPS_INCLUDE_DIRS: >> MUMPS_LIBRARIES: >> MUMPS_CXX_COMPILE_FLAGS: >> MUMPS_CXX_LINK_FLAGS: >> Searching for BLAS... >> A library with BLAS API not found. Please specify library location. >> BLAS not found. Disabling the Chrono::Mumps module. >> (Here I have downloaded mumps5.1.2 and set the path in cmake Gui) >> >> Regards >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/0fdbe6ca-3bee-414c-a367-81d96be43e86n%40googlegroups.com.
