-
Notifications
You must be signed in to change notification settings - Fork 52
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
Couldn't find "libh264decoder.so" and "libavcodec-ffmpeg.so.56" #9
Comments
Hi, did you follow the exact instructions? please follow the exact installation instructions and try again |
@mandelyoni Thanks for your reply, I followed the exact installation instructions on the README. To break down the problem, I would like to check if "libh264decoder.so" indeed exists under the path "~/ROS/h264decoder/libh264decoder.so". Since in my case, I couldn't find that file, and that might be the trigger of other errors. Best regards, |
Yes |
├── h264decoder |
h264decoder 需要的是老版本,老版本会生成libh264decoder.so,新版本会生成h264decoder.so。在https://github.com/DaWelter/h264decoder 中下载老版本(现在也只有两个版本)后,将src文件夹中的h264decoder.hpp中所有的PIX_FMT_RGB24改为 AV_PIX_FMT_RGB24。其余编译过程不变。 |
Hi @mandelyoni |
I followed the guide on installing h264decoder. After completing the below commands:
.
.
.
.
I couldn't find libh264decoder.so in the below command
.
Instead, I found libh264decoder.so at ~/ROS/Tello_ROS_ORBSLAM/TelloPy/tellopy/_internal/libh264decoder, and I copyed that file to /usr/local/lib/python2.8/dist-packages/
.
.
.
.
Everything seems fine until I executed "roslaunch flock_driver orbslam2_with_cloud_map.launch"
I faced an error below:
It seems that my computer couldn't find the file libavcodec-ffmpeg.so.56
After checking the path /usr/lib/x86_64-linux-gnu/, I could only find the below file rather than "libavcodec-ffmpeg.so.56"
I also ran "sudo apt install ffmpeg" to make sure I install the ffmpeg file, not sure why I don't have the required "libavcodec-ffmpeg.so.56" here.
Hope someone here can help me out, I will be really appreciate it!
Best regards,
The text was updated successfully, but these errors were encountered: