-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OgreVis.hpp: No such file or directory #15
Comments
You have to know where you installed raisimOgre when you call python setup. Please do not use sudo when calling python. You will get stuck at some point. You can use |
Thanks for the fast reply. Ok, I am calling setup.py:
And I get the answer:
Although in .bashrc I have a line written:
|
You have installed the package using I am closing this issue because it's related to neither raisimOgre nor raisim. |
Ok, I created a docker container and deployed the installation there. I have resolved the python issue, but the original issue has not been resolved. When I call:
I get:
The tree result of the build folder:
|
|
Oh, that's a typo. I solved the problem by adding lines to СMakeLists.txt:
Yes, it's barbaric, but it works. |
Did you add target link library? This example will help |
Hi I'm trying to render on raisimOgre, for RaiSim 1.0.0 version.
I was sequentially compiling raisimLib -> ogre -> raisimogre -> pybind11 into my $ LOCAL_BUILD.
I go to the raisimGymTorch folder and add a line to setup.py:
__CMAKE_PREFIX_PATH__ = '/home/roman/unia1/raisim_build'
I go along the path raisimLib/raisimGymTorch/raisimGymTorch/env/envs/rsg_a1
...
├── cfg.yaml
├── Environment.hpp
├── runner.py
├── tester.py
└── visSetupCallback.hpp
In Environment.hpp, I add the line:
#include "visSetupCallback.hpp"
or#include "OgreVis.hpp"
or#include "raisim/OgreVis.hpp"
I run setup.py:
sudo python3 setup.py develop
And the error appears:
With all this, in the /home/roman/unia1/raisim_build/include/raisim folder, I see the OgreVis.hpp file.
What could be the problem and how to solve it?
The text was updated successfully, but these errors were encountered: