We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Pinocchio pkg-config file have a lot of drawback:
I plan to simplify it by only allowing to link against pinocchio_default.
I don't know what pkg-config use case is. So if you use it, please, comment on this issue to expose your use case.
The text was updated successfully, but these errors were encountered:
Also, boost does not provide a .pc, so our .pc are doomed to be incomplete, unless we generate the required boost.pc ourself.
I would advocate for a simple removal of pkg-config support from all our codebases, if nobody provide a convincing use case 👼🏼
Sorry, something went wrong.
I know there's been discussions about getting rid of pkg-config support - I also support it (to keep things simple and maintainable)
On my side, I've just use pkg-config for quick compilation via g++:
g++ -O3 -std=c++14 -g overview-urdf.cpp -o overview-urdf $(pkg-config --cflags pinocchio) $(pkg-config --libs pinocchio) && ./overview-urdf
No branches or pull requests
Pinocchio pkg-config file have a lot of drawback:
I plan to simplify it by only allowing to link against pinocchio_default.
I don't know what pkg-config use case is. So if you use it, please, comment on this issue to expose your use case.
The text was updated successfully, but these errors were encountered: