About missing executables: basically the only executables that we ship are 
demos. And demos are now copied in the *install *folder only when building 
the *Release *version.
Obviously they would still show up in the *build *folders, for any 
configuration, no matter if Release or Debug or whatsoever.

Dario
Il giorno lunedì 15 settembre 2025 alle 14:35:17 UTC+2 Radu Serban ha 
scritto:

> Hi Alvaro,
>
>  
>
>    1. That is by design.  It is the user’s responsibility to ensure that 
>    dependency DLLs are found (either by adding their location to the path 
>    environment variable or else by manually copying them next to their 
>    executables).  We decided that a Chrono installation should not bundle all 
>    dependency DLLs, first because some dependency libraries (unlike Irrlicht) 
>    come with very many DLLs and second because this can lead to issues with 
>    existing local installations of those libraries.  
>    
>    2. I cannot reproduce this issue. Executables of the demos install 
>    fine in all my tests.  You may want to double check that building demos is 
>    enabled when you configure Chrono or for any other changes you may have 
>    made locally.
>
>  
>
> --Radu
>
>  
>
> *From:* projec...@googlegroups.com <projec...@googlegroups.com> *On 
> Behalf Of *alvaro diaz
> *Sent:* Friday, September 12, 2025 7:27 PM
> *To:* ProjectChrono <projec...@googlegroups.com>
> *Subject:* Re: [chrono] Use YAML_parser on a project calling chrono
>
>  
>
> Hello Radu,
>
>  
>
> Thank you for the updates. I was able to build and install chrono and call 
> the libraries from my own project. A few comments:
>
>    1. I still needed to copy for both the Chrono build and my project 
>    build Irrlicht.dll into the appropriate folders.
>    2. With the push from (9/11/2025) the examples executables are not 
>    copied into the bin folder when installing (the dynamic libraries yes)
>
> Thank you for the help, I can now start working on it.
>
>  
>
> Best,
>
>  
>
> Alvaro
>
>  
>
>  
>
> El jueves, 11 de septiembre de 2025 a las 10:38:05 UTC-6, Radu Serban 
> escribió:
>
> Hi Alvaro,
>
>  
>
> The YAML parser is still under development, and I had no chance to update 
> the Chrono configuration script to make it available in external projects.
>
> I have now pushed a set of necessary fixes to the main branch.
>
> When you get a chance, please pull the latest code, rebuild, and reinstall 
> Chrono and see if that fixes your problem.  Note that I only tested this on 
> Windows so far.
>
>  
>
> --Radu 
>
>  
>
> *From:* projec...@googlegroups.com <projec...@googlegroups.com> *On 
> Behalf Of *alvaro diaz
> *Sent:* Wednesday, September 10, 2025 5:01 PM
> *To:* ProjectChrono <projec...@googlegroups.com>
> *Subject:* [chrono] Use YAML_parser on a project calling chrono
>
>  
>
> In short: after installation, I don't see the folder* 
> chrono_thirdparty/yaml-cpp*.
>
>  
>
> I installed chrono on windows 11 via cloning the main branch on github 
> (version 9.0.1 doesn't have YAML parsers). Within Chrono solution, the file 
> demo_YAML_test, works both on the build and the install and the problem 
> comes when trying to setup a project that uses Chrono. I am following the 
> instruction from the documentation (Link 
> <https://urldefense.com/v3/__https:/api.projectchrono.org/development/tutorial_install_project.html__;!!Mak6IKo!KTq8ASqi48MeZknYIdEhhMwNdaYcxz7dfNoC_1bofonP1UvzXcNMW-tMQOF2qQQ9J-baoUq1RurDLRF6$>
> ). 
>
>  
>
> Apparently, in my install folder the directory '
> *chrono_thirdparty/yaml-cpp/include/yaml-cpp/yaml.h*' does not exist. I 
> do have the folder *chrono_thirdparty*. Can i get some help on this?
>
>  
>
> Thank you in advance for the help.
>
>  
>
> Kind regards,
>
>  
>
> Alvaro
>
>  
>
> -- 
> 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/bec1f18f-a02d-4b5d-8351-8484bf4f20c6n%40googlegroups.com
>  
> <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/bec1f18f-a02d-4b5d-8351-8484bf4f20c6n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!KTq8ASqi48MeZknYIdEhhMwNdaYcxz7dfNoC_1bofonP1UvzXcNMW-tMQOF2qQQ9J-baoUq1Rt5ck0FO$>
> .
>
> -- 
> 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/be8c43a5-ecc7-4d5a-97d0-684fb0a5193en%40googlegroups.com
>  
> <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/be8c43a5-ecc7-4d5a-97d0-684fb0a5193en*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!KXMRz6O77S7KochDj3diK3FrWbcN8B5RZAqDlMenLFywnSiIw2CT4ABde4-Lp8BmBe0hbJ7BDufjambh$>
> .
>

-- 
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/e33c7e35-2eca-4496-ba27-74632d7e1126n%40googlegroups.com.

Reply via email to