These are not part of the Chrono distribution. Rather, they are files generated during the build process with Visual Studio.
Whatever Dropbox thinks about these files may have to do with some setting on your local machine.
Having said that, there is no reason to try to backup such files. If you want to save an install of Chrono, set a proper install directory during CMake configuration, then build the INSTALL target (project) after a successful build of the Chrono solution, and backup the install directory. That directory will contain all headers, libraries, and DLLs you’d need to link Chrono to some external project.
--Radu
Thanks,
Qihan
--
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 on the web visit
https://groups.google.com/d/msgid/projectchrono/6dc185ad-803d-4fdb-8f19-ea5782cdae99n%40googlegroups.com.