Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] usbip: add a new package
Date: Sun, 11 Dec 2016 11:06:34 +0100	[thread overview]
Message-ID: <20161211100634.GA3599@free.fr> (raw)
In-Reply-To: <CAFDyS3Mp5SkXG9hJwCxDnoPEK_h6Xd1B_Jp6bE6GDu0CRSnMyw@mail.gmail.com>

Tal, All,

On 2016-12-10 20:39 +0200, Tal Shorer spake thusly:
> On Sat, Dec 10, 2016 at 3:31 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > On Fri,  9 Dec 2016 10:37:51 +0200, Tal Shorer wrote:
> >> Add usbip tools (usbip, usbipd) from the running linux source
> >>
> >> Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
> >
> > Thanks for your contribution. However, since usbip tools is provided as
> > part of the Linux kernel source code, it should be supported by the
> > package/linux-tools/ package, which already handles similar tools (perf
> > and others).
> >
> > However, it is true that the linux-tools infrastructure currently only
> > handles tools that just need to be built/installed, and not tools that
> > use autoconf/automake. So most likely, we want to extend
> > package/linux-tools/linux-tools.mk? Or should we, because usbip is
> > different, have a separate package?
> Thanks for your reply.
> 
> I managed to compile usbip as part of linux-tools, but it's quite a
> hack, doing configuration stuff in USBIP_BUILD_CMDS before actually
> calling make. The other option I see is defining
> LINUX_TOOLS_POST_CONFIGURE_HOOKS and doing that there, but it's still
> duplicating what's already being done in pkg-autotools.

Yes, that's not clean...

However, I think it is netter to introduce this configure step in the
linux-tools infra. Then you can hand-write a configure rule for usbip.

Then, we can see whether we make this infra more like any other package
infra. But I'm warry to add even more complexity just for a single
package...

So, could you please send a patch series that;

 1- introduces LINUX_TOOLS_POST_CONFIGURE_HOOKS,
 2- adds usbip with hand-written commands, duplicated from
    pkg-autotools.

On my side, I'll see what we can do about the infra itself and see if we
can re-use the existing infra...

Regards,
Yann E. MORIN.

> Either way, I noticed I sent a silly placeholder for the help string
> in Config.in in my patch, so even if you decide to have usbip external
> to linux-tools, don't apply just yet . I'll conjure a real help string
> and send a v2 soon :)
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-12-11 10:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  8:37 [Buildroot] [PATCH] usbip: add a new package Tal Shorer
2016-12-10 13:31 ` Thomas Petazzoni
2016-12-10 18:39   ` Tal Shorer
2016-12-11 10:06     ` Yann E. MORIN [this message]
2016-12-11 13:56 ` Yann E. MORIN
2016-12-11 17:39   ` Tal Shorer
2016-12-11 17:45     ` Yann E. MORIN
2016-12-11 18:12       ` [Buildroot] [PATCH] pkg-generic: run $(PKG)_PRE_RSYNC_HOOKS before checking for the existence of $(SRCDIR) Tal Shorer
2016-12-11 19:19         ` Yann E. MORIN
2016-12-11 19:44         ` [Buildroot] [PATCH] package/usbip: new package Tal Shorer
2016-12-17 15:00         ` [Buildroot] [PATCH] pkg-generic: run $(PKG)_PRE_RSYNC_HOOKS before checking for the existence of $(SRCDIR) Thomas Petazzoni
2016-12-11 18:31       ` [Buildroot] [PATCH] usbip: add a new package Tal Shorer
2016-12-11 19:24         ` Yann E. MORIN
2016-12-11 19:59     ` Arnout Vandecappelle
2016-12-11 21:40       ` Yann E. MORIN
2016-12-11 21:46       ` Tal Shorer
2016-12-11 22:05         ` Yann E. MORIN
2016-12-11 22:11           ` Tal Shorer
2016-12-11 22:20             ` Yann E. MORIN
2016-12-11 22:30               ` Tal Shorer
2016-12-12  9:40                 ` Arnout Vandecappelle
2016-12-12 17:25                   ` Yann E. MORIN
2016-12-12 22:17                     ` Tal Shorer
2016-12-12 22:21                       ` [Buildroot] [PATCH v3] usbip: " Tal Shorer
2016-12-13 17:53                         ` Yann E. MORIN
2016-12-14 17:28                           ` [Buildroot] [PATCH v4] " Tal Shorer
2016-12-21 22:17                             ` Tal Shorer
2016-12-22 20:45                             ` Yann E. MORIN
2016-12-23 18:24                             ` Yann E. MORIN
2016-12-23 19:10                               ` Yann E. MORIN
2016-12-13 17:35                       ` [Buildroot] [PATCH] usbip: add a " Yann E. MORIN
2016-12-12 17:09                 ` [Buildroot] [PATCH v2 1/2] package: linux-tools: allow tools to define configure hooks Tal Shorer
2016-12-12 17:09                   ` [Buildroot] [PATCH v2 2/2] package: linux-tools: add usbip Tal Shorer
2016-12-12 17:26                     ` Yann E. MORIN

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=20161211100634.GA3599@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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