mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Update libusb-1.0
Date: Fri, 28 Mar 2014 10:46:12 +0100	[thread overview]
Message-ID: <20140328094610.GA21559@omega.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <53354118.3090500@mwlaser.de>

On Fri, Mar 28, 2014 at 10:30:00AM +0100, Martin Lammers wrote:
> Am 28.03.2014 09:04, schrieb Alexander Aring:
> >On Fri, Mar 28, 2014 at 08:59:49AM +0100, Martin Lammers wrote:
> >>Hi Alex,
> >>
> >>thanks for the fast response. We want to use libusbx version 1.0.18.
> >>
> >Then you need to write a new port of it. Look for the documentation at
> >[0], "4.2.1 Rule File Creation". Send the new rules added to ptxdist
> >with git send-email as patches, then we can talk about the new port and
> >hopefully get the libusbx mainline to ptxdist so other can use it also.
> >
> >I don't have time right now to do the port myself, sorry.
> >
> >- Alex
> >
> >[0] http://www.ptxdist.org/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
> >
> Hi Alex,
> thanks for the information.  On the ptxdist the version of libusb.org have
> the name libusb-1.x. When it build the name of the library file like
> libusb-1.0.a .la.

name the library LIBUSBX_...

> Now i want to create a new rule file for the libusbx versions witch had the
> same library name like libusb-1.0.a .la.
> It is necessary to block the two versions each other ?
>
Yes. LIBUSB should have depends on !LIBUSBX and LIBUSBX should have
depends on !LIBUSB. Maybe there exists a better solution, I don't look
much more into that.

> Now we had to check, if we get any problems with the update, because the
> libusb is used by some phytec tools.

This would end in problems yea, but then you need to change the
dependency of these tools to "select LIBUSBX". You don't should do that,
because these tools was developed for LIBUSB and not LIBUSBX.

You can't have LIBUSB and LIBUSBX installed, but maybe it's easy to port
it look at [0] in About.

"As far as the library binary and header are concerned, since libusb and
libusbx use the same names and have the same API, you just need to
replace your deployed libusbx files with the libusb ones. That's all!"

This makes all things much difficult... maybe we make a config option to
LIBUSB to decide if you want to have libusb or libusbx and change the
actually libusb rules. But this sounds like an hack, which remember me
about the gnu- and bsd-netcat rules. Another option would be to drop
libusb support and add libusbx support. But this is a question which
should answer by the ptxdist maintainer Michael Olbrich.

My opinion is that when all others distribution uses libusbx and not
libusb then we should also drop the libusb support and add libusbx for
that instead.

But remember what I already said, the "phytec tools" was developed for your
libusb and to the libusb version which is shipped out with your BSP, you
can maybe run into trouble with that and I don't want to make the phytec
people angry.

- Alex

[0] http://libusbx.org/

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-03-28  9:46 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
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 [this message]
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=20140328094610.GA21559@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