No worries, Alexis. We always encourage users to start with one of the “template” projects we distribute with Chrono and only once they get that to build fine, move to configuring and building their own project.
--Radu From: [email protected] <[email protected]> On Behalf Of Susan Alexis Brown Sent: Wednesday, February 26, 2025 7:11 PM To: ProjectChrono <[email protected]> Subject: Re: [chrono] Compiling Pardiso_MKL module with new cmake Follow up follow up it works fine, it was just an error in my cmake file. Sorry for the spam! On Wednesday, February 26, 2025 at 12:00:13 PM UTC-6 Susan Alexis Brown wrote: Follow up, it does compile with MKL after I re-define the path in the configuration (which it seems I should not have to do?), but does not compile due not finding the chrono files. This seems unrelated, but I am doing this with a basic demo file, so it should run. [ 50%] Building CXX object CMakeFiles/demo_fea.dir/demo_FEA_basic.cpp.o /home/sab/workspace/demos/demo_fea/demo_FEA_basic.cpp:19:10: fatal error: chrono/physics/ChSystemSMC.h: No such file or directory 19 | #include "chrono/physics/ChSystemSMC.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. gmake[2]: *** [CMakeFiles/demo_fea.dir/build.make:76: CMakeFiles/demo_fea.dir/demo_FEA_basic.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/demo_fea.dir/all] Error 2 gmake: *** [Makefile:91: all] Error 2 On Wednesday, February 26, 2025 at 10:27:08 AM UTC-6 Susan Alexis Brown wrote: Apologies, a follow up issue. Although the chrono build compiled without issue, configuring a project which uses Pardiso_MKL gives the following error: Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables. Run "cmake --help-policy CMP0074" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable MKL_ROOT is set to: /opt/intel/oneapi/mkl/2024.0/lib/cmake/mkl/../../../ For compatibility, CMake is ignoring the variable. and does not configure with Pardiso. Furthermore, the MKL_DIR variable is once thrown as not found. What am I missing here? On Wednesday, February 26, 2025 at 9:18:35 AM UTC-6 Susan Alexis Brown wrote: I understand, this solved my issue, thank you! On Wednesday, February 26, 2025 at 9:04:34 AM UTC-6 Radu Serban wrote: Hi Alexis, If you use cmake-gui and hover over MKL_DIR you will see the description of this variable: “The directory containing a CMake configuration file for MKL”. So, you should set this to something like: * (Windows) C:/Program Files (x86)/Intel/oneAPI/mkl/2023.0.0/lib/cmake/mkl * (Linux) /opt/intel/oneapi/mkl/latest/lib/cmake/mkl We resolved the problem (mentioned in my Feb 16 post) with having both MUMPS and MKL enabled at the same time. We will update the installation page when we get a chance. --Radu From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Susan Alexis Brown Sent: Wednesday, February 26, 2025 3:45 PM To: ProjectChrono <[email protected]<mailto:[email protected]>> Subject: [chrono] Compiling Pardiso_MKL module with new cmake Hello, Following the update to modern cmake I am having an issue configuring with the Pardiso module. The previous update posted Feb 16 noted configuration issues using both Chrono::PardisoMKL and Chrono::Mumps however even without the Mumps module enabled the configuration does not correctly identify the MKL directory. Indeed, rather than two directories (MKL_INCLUDE_DIR, and MKL_RT_LIBRARY) only one is given (MKL_DIR) which is not reflected in the current installation guide. Attempts to direct this variable to any of the MKL subdirectories (within \opt\intel\oneapi\mkl) fail. Please advise. Thanks! Alexis -- 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]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/2e0e6e6f-bcd6-4f2f-aa81-1fff835efd40n%40googlegroups.com<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/2e0e6e6f-bcd6-4f2f-aa81-1fff835efd40n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!K8dnWk2oJrufR3Tx94-TpMjih28vToq-jSQMaV_PD3M0LI2i6RSQ0qStmgmQZxxk3OgtYMapf3q9wBcAM060H4U$>. -- 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]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/4b76e585-927f-4424-b6af-f4ed57070b2dn%40googlegroups.com<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/4b76e585-927f-4424-b6af-f4ed57070b2dn*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!JN4F2kzNpkPuIrM0DRdztxgbZHto9ZzvRaOvBfzvsz3JGceJLfcY9VYJgPqyLYdZG0VjZLjVGPs57ctkvDLkQzI$>. -- 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 visit https://groups.google.com/d/msgid/projectchrono/CH3PPF46CDC2185986428707FF52DFE3FF5A7CD2%40CH3PPF46CDC2185.namprd06.prod.outlook.com.
