-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
have problems add open3d into C++ project #2894
Comments
Looks like a YAML linking issue. Does this work? #include <iostream>
#include <yaml-cpp/yaml.h>
int main(int, char**) {
YAML::LoadFile("./config.yaml");
const std::vector<std::string> files = {
"../data/models/ROBOX_0.pcd",
"../data/models/ROBOX_1.pcd",
"../data/models/ROBOX_2.pcd",
"../data/models/ROBOX_3.pcd"
};
} |
Thank you for your advice. I have tried it and get same messages:
I also found that if I change
I also tried other library like fcl, It seems the compilation will get wrong after linking the open3d libraries. Just for my opinion, I guess there is something wrong with CMakeLists.txt or Open3D . |
instead of "link_libraries(Open3D)" try "link_libraries(Open3D::Open3D)" |
the sentence |
Seems that this #2286 (comment) solves the problem |
I can verify that @cbenitez81 's suggestion resolves this. Also, with PR #4387 this is no longer needed. Note that if you need PyTorch Ops or TensorFlow Ops, you will need to build PyTorch / TensorFlow from source with the new CXX11_ABI. This only affects GCC. |
Describe the bug
Hello, I created a simple C++ project with yaml-cpp. This project can be compiled until I add open3d into my CMakeLists.txt.
the output error messages are:
Is there something missing or wrong with my CMakeLists.txt ? thanks in advance.
To Reproduce
here is my main.cpp:
and CMakeLists.txt:
Environment (please complete the following information):
Operating system: Ubuntu 18.04
Open3D version: 0.12.0
Is this remote workstation?: no
How did you install Open3D?: build from source
Compiler version (if built from source): gcc 9.3.0
The text was updated successfully, but these errors were encountered: