Compiling libusb c++ program to run without it's dependencies

linuxmandrake · 08-06-2010, 04:38 AM

Hi
I've built a piece of hardware that communicates using usb. I was wondering could I make a libusb based program run on it's own without gcc/ libusb

Sergei Steshenko · 08-06-2010, 04:46 AM

Quote:

Originally Posted by linuxmandrake

Hi
I've built a piece of hardware that communicates using usb. I was wondering could I make a libusb based program run on it's own without gcc/ libusb

Suppose I run, say, 'cp src_file dst_file' - does the 'cp' program need 'gcc' to run ?

If yes - how ? If no, how is your program different ?

linuxmandrake · 08-06-2010, 06:04 AM

but I don't need to cp files. I'm simply using libusb

wje_lq · 08-06-2010, 06:34 AM

Quote:

Originally Posted by linuxmandrake

I've built a piece of hardware that communicates using usb. I was wondering could I make a libusb based program run on it's own without gcc/ libusb

Using libusb means you don't have to worry about low-level usb programming details yourself. The most straightforward way to avoid using libusb itself is to look at the source code for libusb and steal whatever you need from it and put it into your own source code.

Of course, if you decide to do that and you distribute your compiled program to others in any way, you'll have to license it under the GPL (with all that this implies), or we'll come after you.

Sergei Steshenko · 08-06-2010, 06:34 AM

Quote:

Originally Posted by linuxmandrake

but I don't need to cp files. I'm simply using libusb

No software library works by itself, it works being linked to a program.

But when a library is linked to a program, why/what for do you need a compiler ('gcc' in this case) ?

linuxmandrake · 08-06-2010, 07:46 AM

that's fair enough I'll research into the GPL since I've never had to work with it.

Sergei Steshenko · 08-06-2010, 08:03 AM

Quote:

Originally Posted by linuxmandrake

that's fair enough I'll research into the GPL since I've never had to work with it.

And what does the license (GPL) have to do with the issue ?

linuxmandrake · 08-06-2010, 08:39 AM

read wje_lq post.

dugan · 08-06-2010, 08:41 AM

Just distribute your program as statically linked binary. Google for "gcc" and "static linking."

Sergei Steshenko · 08-06-2010, 09:56 AM

Quote:

Originally Posted by linuxmandrake

read wje_lq post.

You asked a question about library and compiler usage, and not distribution.

GPL mandates the way code is distributed - if you do not distribute the code containing GPL'ed components, e.g. use at home or at work (but not ship to customers/other companies) you can do with GPL'ed whatever you like:

http://www.gnu.org/licenses/gpl-faq.html ->
http://www.gnu.org/licenses/gpl-faq....alDistribution
.

wje_lq · 08-06-2010, 08:09 PM

Quote:

Originally Posted by Sergei Steshenko

GPL mandates the way code is distributed - if you do not distribute the code containing GPL'ed components, e.g. use at home or at work (but not ship to customers/other companies) you can do with GPL'ed whatever you like

Exactly. But this thread has already visited that point, when I talked about swiping code from libusb:

Quote:

Originally Posted by wje_lq

Of course, if you decide to do that and you distribute your compiled program to others in any way, you'll have to license it under the GPL (with all that this implies), or we'll come after you.