From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Update libusb-1.0
Date: Fri, 28 Mar 2014 08:41:42 +0100 [thread overview]
Message-ID: <20140328074139.GA11168@omega.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <533520E5.7040700@mwlaser.de>
Hi Martin
On Fri, Mar 28, 2014 at 08:12:37AM +0100, Martin Lammers wrote:
> Hi there,
>
> we are using ptxdist 2012.03.0 with the Phytec iMX board. I develop some USB
> applications with my Ubuntu machine using libusb-1.0.16.
> In the ptxdist menuconfig i can select the libusb-1.0 to install it on my
> target system. When i look at the rules files i see this is version 1.0.8.
> Also in the newest version of ptxdist is the same version.
> Now my question, what is the right way to update the libusb to version
> 1.0.18 and it is possible to do that without changing the ptxdist version?
>
There exists two libusb variants, the original one "libusb" [0] and
"libusb-x" [1] a fork of libusb.
The current version of libusb is 1.0.9 and we have indeed 1.0.8. I can
write a patch to bump this version but we have also a crazy patch for
libusb 1.0.8:
`cat patches/libusb-1.0.8/libusb-1.0.1-pkg-config.diff`
Subject: libusb needs librt and libpthread
Add missing dependencies.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
# 20100603 rsc: The patch was closed upstream, and I don't
# remember a use case any more :-( Let's keep it
# here for the moment, until we have a user.
# 20100101 rsc: added as http://libusb.org/ticket/24
libusb-1.0.pc.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: libusb-1.0.1/libusb-1.0.pc.in
===================================================================
--- libusb-1.0.1.orig/libusb-1.0.pc.in
+++ libusb-1.0.1/libusb-1.0.pc.in
@@ -6,6 +6,6 @@ includedir=@includedir@
Name: libusb-1.0
Description: C API for USB device access from Linux userspace
Version: @VERSION@
-Libs: -L${libdir} -lusb-1.0
+Libs: -L${libdir} -lusb-1.0 -lrt -lpthread
Cflags: -I${includedir}/libusb-1.0
Maybe this already fixed in mainline... I will check this.
If you want to use libusb-x you need to generate a new port of this. I
checked it and they using autotools as buildsystem so a new port would
be (hopefully) easy.
But it depends which library you want... libusb or libusbx.
- Alex
[0] http://www.libusb.org/
[1] http://libusbx.sourceforge.net/
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-28 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 7:12 Martin Lammers
2014-03-28 7:41 ` Alexander Aring [this message]
2014-03-28 7:59 ` Martin Lammers
2014-03-28 8:04 ` Alexander Aring
2014-03-28 9:30 ` Martin Lammers
2014-03-28 9:46 ` Alexander Aring
2014-03-28 11:33 ` Alexander Aring
2014-03-31 5:33 ` Martin Lammers
2014-03-31 5:57 ` Alexander Aring
2014-03-31 9:09 ` Martin Lammers
2014-03-31 9:26 ` [ptxdist] mutt config for applying patches [Was: Re: Update libusb-1.0] Uwe Kleine-König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140328074139.GA11168@omega.Speedport_W_921V_1_24_000 \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox