-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
libfreenect_sync.h has broken includes #210
Comments
Github's Markdown processor appears to have eaten important relevant details from your bug report, but I'm guessing that you wanted the include to read: #include <libfreenect/libfreenect.h> or #include "libfreenect.h" One alternative solution would be to add -I/usr/local/include/libfreenectto your compiler include path, but I'm not sure which approach is considered best practice. I think we'd have to restructure our git tree to accomplish the first suggestion, the second one seems less correct, and I'm somewhat used to doing the third, but it could be considered incorrect form for a library...not sure what the right thing to do here is. :/ Also, sorry for the ridiculously latent reply. |
Hello , freenect_context *f_ctx; int main(int argc, char *_argv) |
Hey, yes, I think something is wrong here. libfreenect installs its files into It would be nice if libfreenect could pick one of the two ways and consistently follow it (personally I believe that the current structure looks good and that What do you think? |
7b9a5de introduces the following changes:
THIS IS A BREAKING CHANGE; UPDATE YOUR INCLUDES |
On my Ubuntu system, the c headers are installed here:
/usr/local/include/libfreenect/libfreenect.h
/usr/local/include/libfreenect/libfreenect_sync.h
Including libfreenect_sync.h gives the following error:
/usr/local/include/libfreenect/libfreenect_sync.h:29:25: fatal error: libfreenect.h: No such file or directory
This is because libfreenect_sync.h has:
#include <libfreenect.h>
this should be:
#include <libfreenect/libfreenect.h>
or:
#include "libfreenect.h"
(I'm not sure which of the 2 would be best c practice)
The text was updated successfully, but these errors were encountered: