Hello DM,
I managed to compile and work with Chrono. I did not try PyChrono yet, but from the instructions page there are two options for installing it (using precompiled modules or building it from source). The former should be fairly easy, even for "non-CS" people. Is that what you tried to do? If so, at what step of the instructions on https://api.projectchrono.org/pychrono_installation.html did something fail? If you describe what you were doing and where you think it went wrong, I'm sure someone here can help.
Greetings, Marcel
--
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/38095356-655b-4fa4-94c7-ead986c3743bn%40googlegroups.com.
Hi DM
First of all, for the functionality that you listed, the two optional modules you enabled should suffice.
It’s still not clear to me what issues you are having with building PyChrono from sources?
Now, if you successfully built the C++ libraries and demos, you are almost there. What you will need in addition is just the SWIG package (you will be asked for the path to the SWIG executable unless you install it in a system path).
Once you have that, rerun CMake (reopening the configuration you already have is just fine) and enable the Python module (set ENABLE_MODULE_PYTHON to “on”). After you hit Configure, if the SWIG executable was not found automatically, set the CMake variable SWIG_EXECUTABLE and Configure again. Then generate your build files.
After that it’s just a matter of ‘make’ (and optionally ‘make install’), just like before.
As a side note, related to a comment you made to Marcel, you *do not* have to go through the process of building all of Chrono without the Python module enabled and then again after enabling that module. You can enable all desired modules (Python included) the very first time. Just make sure to go through the usual cycle of CMake configurations and resolve all necessary dependencies. By the way, if the documentation is unclear or confusing in this or other parts, this would be a great contribution you could help with!
Note also that PyChrono is simply a set of wrappers around the Chrono C++ libraries. These are still needed in order to use PyChrono! That is the case with any other piece of software that uses SWIG (or similar technologies) to provide Python wrappers to libraries developed in other languages.
Once you build Chrono (now with the Python module enabled), besides the Chrono shared libraries, you will also get the Python hooks. These will be located in your build tree (under bin/). In order to use Pychrono you *must* properly set your PYTHONPATH environment variable to include the path to the PyChrono modules (something like /path-to-your-chrono-build-tree/bin/). Of course, if you choose to install the Chrono libraries and Python hooks elsewhere (through make install), you will need to set PYTHONPATH accordingly.
Please let me know where in the above process you encounter problems.
--Radu
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/8002ff1a-9fff-4e1a-9e12-0009a87d7c99n%40googlegroups.com.