-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Include file directory prefix 'lib' confusing #38
Comments
Yep, this is true, but realsense alone as an include path is also confusing. The additional lib- disambiguates and helps discoverability, for instance on Github code search. It's unlikely that we will change the convention at this point. Thanks for your note! |
furushchev
pushed a commit
to furushchev/librealsense
that referenced
this issue
Jul 17, 2016
Add Project Contribution Conditions
matkatz
pushed a commit
to matkatz/librealsense
that referenced
this issue
Nov 22, 2018
Merge from Librealsense/Development
nhershko
pushed a commit
to nhershko/librealsense
that referenced
this issue
Feb 23, 2020
…branch Make stream_counter as a static member
ev-mp
pushed a commit
to ev-mp/librealsense
that referenced
this issue
Jul 23, 2020
…ttons on Viewer app menu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Normally libraries, e.g. libcurl have their library file called e.g. libcurl.so, but keeps the include without the lib prefix, e.g.
include/curl
.It would be great if also librealsense followed this convention.
The text was updated successfully, but these errors were encountered: