Dear Radu, Dario, Thanks for your help. Best, Utk
On Wednesday, March 26, 2025 at 8:36:49 PM UTC+1 Radu Serban wrote: > Hi Utk, > > > > The installation documentation for the PardisoMKL module needs a face > lift. > > > > For now, as Dario mentioned, the easiest is to use the Intel command > prompt, at least when you first configure Chrono with CMake (in other > words, start cmake-gui from the Intel command prompt). That will allow > CMake to find all necessary dependencies if/when you enable the > Chrono::PardisoMKL module. > > > > After that, you can proceed as Dario suggested and start Visual Studio > from within the same Intel environment (as well as run Chrono programs for > there). But if you have added the correct MKL directory to the PATH > environment variable, you don’t actually need to do that after the first > CMake configuration of Chrono. Once that first configuration was done, you > can skip the Intel command prompt (when running cmake-gui, or starting > Visual Studio, or running Chrono demos). This is how I personally deal with > the MKL stuff. > > > > Having said that, the directory you mention (C:\Program Files > (x86)\Intel\oneAPI\mkl\2023.0.0\lib\cmake\mkl) is **not** the correct > path to the DLLs that you need at run-time. That should be something like: > C:\Program Files (x86)\Intel\oneAPI\mkl\latest\redist\intel64 (just like > the Chrono documentation says). If you do not find that on your machine, > you may have an incomplete Intel OneAPI installation. > > > > Best, > Radu > > > > *From:* projec...@googlegroups.com <projec...@googlegroups.com> *On > Behalf Of *Dario Mangoni > *Sent:* Wednesday, March 26, 2025 5:37 PM > *To:* ProjectChrono <projec...@googlegroups.com> > *Subject:* [chrono] Re: Irrlicht.dll was not found. > > > > Location of MKL DLLs may vary depending on your MKL version. > > I highly recommend, as also suggested in the PardisoMKL installation > guide, to make the first tests by running the demos using MKL through a > "Intel oneAPI command prompt for Intel 64 for Visual Studio 2022". > You should find it among the installed software, > > This command prompt already sets all the variables for you. > > If this works I would still recommend to always start both your Visual > Studio, your CMake etc, from such command prompt to avoid having to pollute > your PATH envvar with hardcoded MKL paths. > > Dario > > Il giorno mercoledì 26 marzo 2025 alle 17:05:03 UTC+1 utk...@gmail.com ha > scritto: > > Dear Dario, > > Thanks for your prompt reply. I am facing a new issue now. It cannot find > the mkl dlls even after adding > > C:\Program Files (x86)\Intel\oneAPI\mkl\2023.0.0\lib\cmake\mkl; to the > PATH. > > I however think the issue is because I have not added the variables given > in the Pardiso MKL module . > > *For Windows:* > <install_folder>/Intel/oneAPI/mkl/latest/redist/intel64 > <install_folder>/Intel/oneAPI/compiler/latest/windows/redist/intel64_win/compiler > > > > the reason being I cannot find those folders especially the redist. Thanks > for the help. > > > > Best, > > Utk > > On Wednesday, March 26, 2025 at 4:12:27 PM UTC+1 dariom...@gmail.com > wrote: > > Hi Utk, > we recently changed how DLLs are handled in Chrono. We copy the DLLs only > for the INSTALL tree not for the BUILD anymore. > > In the page you referred there is a small section telling that: > > - Since many of the 3rd-party dependency packages create and install > shared libraries, the following steps may be required: > > > - on Linux, run ldconfig (you will likely need root permissions) to > cache the necessary link to the newly created shared libraries or set > the > LD_LIBRARY_PATH environment variable > - on Windows, add to the PATH environment variable the directories > containing the package DLLs (otherwise, these DLLs have to be manually > copied next to the binaries so that they can be found at run-time) > > This means that you need to add the Irrlicht DLL folder to PATH if you are > on Windows. > > However, since you refer to Irrlicht you should have checked the dedicated > Chrono::Irrlicht install guide... but you wouldn't have find anything about > this. We should definitely remind the user about it > > Dario > > > > Il giorno mercoledì 26 marzo 2025 alle 16:04:28 UTC+1 utk...@gmail.com ha > scritto: > > Hello, > > Trying to build chrono using the instructions on this page. > <https://urldefense.com/v3/__https:/api.projectchrono.org/tutorial_install_chrono.html__;!!Mak6IKo!LI7E0dX2Qr2rNnFmxdS-x07O3-9sEGK2qq3xElkGuU8wk9xHMIOM7rnzRIph1VBGdOebP3ewD93rh_XUPpql$> > > for a windows 11 machine. But after the build is complete the demos won't > work with a error message irrlicht.dll was not found, even though the demos > folder has the chrono.irrlicht.dll file in it. Please help. Thank you. > > > > Best, > > Utk > > -- > 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/7c1e2a6c-26df-4528-b095-f2e7d2bfba17n%40googlegroups.com > > <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/7c1e2a6c-26df-4528-b095-f2e7d2bfba17n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!LI7E0dX2Qr2rNnFmxdS-x07O3-9sEGK2qq3xElkGuU8wk9xHMIOM7rnzRIph1VBGdOebP3ewD93rh_cP2Q4l$> > . > -- 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/bbb2be85-5576-4492-af06-b360e192f0ebn%40googlegroups.com.
