ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that depends on the compiler itself, usually in /usr/include, but it is only the header
the source code of those objects are already compiled and will be linked together with your code.
OK. Let's subtitute usb.h for stdio.h in a sentence like
Code:
#include <usb.h>
In a certain library the functions declared by usb.h are already compiled. Specifically, there is the function usb_control_msg in usb.h. So the sources may come from many places?! As I have in vain looked for complete specifications for the use of that function, I wanted to go to the source. Now I see I was being naive.
Yes, the http://libusb.sourceforge.net/doc/fu...ontrolmsg.html is insufficient. And the second link, well I have /usb/core/message.c in my disk already, and the order and quantity of the arguments are different to those declared in /usr/include/usb.h. Doesn't matter, for it would be hard for me to draw safe conclusions form the sources, now I see.
What I need, is something like The GNU C Library.htm, which explains everything in such detail and so much intelligibility. Look at the sourceforge.net link and tell me if you can understand what it is about! And all the pages from Google refer to this kind of documentation.
usb.h comes from libusb package, if you look at the package sources, there is libusb-compat-x.y.z.tar.xz containing usb.h and core.c which contains the implementations from usb.h
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.