Skip to content
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

Building QtLeapMotionLibrary #1

Open
messi1 opened this issue Oct 17, 2013 · 1 comment
Open

Building QtLeapMotionLibrary #1

messi1 opened this issue Oct 17, 2013 · 1 comment

Comments

@messi1
Copy link

messi1 commented Oct 17, 2013

Hi
I'm testing your QtLeapMotionLibrary at the moment.
I was faced with the following issues.
LeapSDK include path:
I suggest that you should add some kind of global LeapSDK path variable to your main project file. From there it would be much easyer to find the include path and the library path.

Adding librarys to your projectfile should be done this way:
LIBS += -L -l
e.g.
LIBS += -L/usr/local/LeapSDK/lib/x86 -lLeap

This line is not working:
linux-g++-32 {
LIBS += -L/usr/local/LeapSDK/lib/x86 -lLeap
LIBS += $$PWD/Leap/x86/libLeap.so
install_folder.files += $$LIBS
}

It never reaches the LIBS settings. My machine is a 32bit x86
It would be better if you would use "unix {" instead.

Cheers
Juergen

@lemirep
Copy link
Owner

lemirep commented Oct 17, 2013

You're right, I didn't use the proper syntax to link the libraries. I just committed a correction. I'd like to keep the lib includes in the .pri in order to keep each entity cleanly separated. I have no issue at all on my x86_64. For the unix {} part, I'm not against it but as I need to know the architecture (64 or 32) to link the proper Leap library, I don't know if I'd be able to still do it.
Please let me know if it works for you now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants