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:* projec...@googlegroups.com <projec...@googlegroups.com> *On >> Behalf Of *Susan Alexis Brown >> *Sent:* Wednesday, February 26, 2025 3:45 PM >> *To:* ProjectChrono <projec...@googlegroups.com> >> *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 projectchron...@googlegroups.com. >> 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 projectchrono+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/23876a9e-2c0a-4978-aec1-25d438501df7n%40googlegroups.com.