Hey Anthony, I personally never saw this issue before, but few things in my mind: 1. TensorRT is not required for Chrono::Sensor module, so can you try to build without selecting "USE_TENSOR_RT" choice? 2. I found this link <https://forums.developer.nvidia.com/t/file-not-found-why/248471> online, "nvinder.dll" not found issue might have something to do with installation process. Hopefully these will be helpful :-)
Best, Harry On Friday, June 16, 2023 at 10:48:42 AM UTC-5 [email protected] wrote: > Hello Harry, > > I think I am almost there. I disabled "USE_CUDA_NVRTC" and it was able > to create the demos application in my build folder. However, whenever I > open the demo, I get an error that the nvinfer.dll was not found (picture > attached) and the demo does not open. I redownloaded TensorRT as that is > the folder that have nvinfer.dll, but the same error came up. Would you > know how to go about this? > > As always, your help is greatly appreciated > > Thank you, > Anthony > > On Wednesday, June 14, 2023 at 2:46:51 PM UTC-4 [email protected] wrote: > >> Hello Anthony, >> >> Few our colleagues also experienced the sensor issue before, and they >> fixed it by disable "USE_CUDA_NVRTC" choice, so you can try to do this >> first. >> >> Best, >> Harry >> On Wednesday, June 14, 2023 at 12:32:38 PM UTC-5 [email protected] >> wrote: >> >>> Hello Harry, >>> >>> Thank you for helping out because I think I resolved that issue using >>> your step (2) but I have a new one that may or may not be connected to my >>> first issue. My new issue is that I am getting a "cannot open input file >>> (lib\Release\ChronoEninge_sensor.lib) when I try to build. And when I look >>> into the Chrono_build folder, I do not see the object library file. Is that >>> something that I should be automatically put in when I generate my >>> solution? I have attached screenshots of my Cmake configuration, error, and >>> folder where I believe I am missing the object library. >>> >>> As always your help is very much appreciated. >>> >>> Thank you, >>> Anthony >>> >>> >>> On Monday, June 12, 2023 at 6:34:55 PM UTC-4 [email protected] wrote: >>> >>>> Hello Anthony, >>>> >>>> I have few questions: >>>> 1) Are you trying to build Chrono main branch? >>>> 2) If you are on the main branch, or Chrono-8, make sure you run the >>>> openGL building script in the 'build-script/' folder ( >>>> https://github.com/projectchrono/chrono/blob/main/contrib/build-scripts/opengl/buildGL.sh). >>>> >>>> After you run the script, there should be a folder full of latest openGL >>>> packages (like ../Packages), make sure you configure openGL related stuffs >>>> using this package folder (like GLEW, GLFW, and GLM). >>>> 3) Double check if you include the correct directories for the CMake >>>> configuration. >>>> 3) If you try above steps and still can't work, can you please share >>>> with your CMake configuration with us? >>>> >>>> Best, >>>> Harry >>>> >>>> On Monday, June 12, 2023 at 2:00:35 PM UTC-5 [email protected] wrote: >>>> >>>>> Hello, >>>>> >>>>> My name is Anthony. I am trying to run Chrono::Sensors demoes. I >>>>> successfully run the Chrono::Vehicle demos recently. All demos of the >>>>> Chrono::Vehicle module works fine. However, when I tried to configure the >>>>> build of the Chrono::Sensor through CMAKE, I had the error* >>>>> "src/chrono_sensor/CMakeLists.txt:527: Target "ChronoEngine_sensor" >>>>> links >>>>> to:GLEW::glew, but target was not found"*. I followed every mentioned >>>>> steps ( >>>>> https://api.projectchrono.org/development/module_sensor_installation.html) >>>>> >>>>> to configure the build. >>>>> >>>>> Can you please help me finding some solutions? >>>>> >>>>> Thank you. >>>>> >>>>> Regards, >>>>> Anthony Abrahamian >>>>> >>>>> >>>>> -- 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/d182a4c1-6c2f-4824-b032-9ae9161e6722n%40googlegroups.com.
