Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Cercueil <paul.cercueil@analog.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] libiio: new package
Date: Wed, 7 Jan 2015 09:55:20 +0100	[thread overview]
Message-ID: <54ACF478.4080509@analog.com> (raw)
In-Reply-To: <20141221223930.6965ea9e@free-electrons.com>

Dear Thomas,

Thanks for merging this patch - and thanks for the extra work.

I see you added a dependency on thread support in the toolchain, is it 
because it breaks some builds if not set?
The library in itself will work just fine on a system without threads, 
only the IIO Daemon requires threads, that's why I'm asking.

Regards,

Paul Cercueil

On 21/12/2014 22:39, Thomas Petazzoni wrote:
> Dear Paul Cercueil,
>
> On Tue, 16 Dec 2014 10:34:06 +0100, Paul Cercueil wrote:
>> Libiio is a library to ease the development of software interfacing
>> Linux Industrial I/O (IIO) devices.
>>
>> http://wiki.analog.com/resources/tools-software/linux-software/libiio
>>
>> v2: Simplify greatly the patch (upstream now uses CMake)
>> v3: Add support for IPv6 and allow installation of systemd service file
>> v4: Added .hash file
>> v5: Rework libiio.mk and init.d scripts after feedback from upstream
>>
>> Signed-off-by: Paul Cercueil <paul.cercueil@analog.com>
>> ---
>>   package/Config.in          |  1 +
>>   package/libiio/Config.in   | 43 +++++++++++++++++++++++++++++++++++++++
>>   package/libiio/S99iiod.sh  | 40 +++++++++++++++++++++++++++++++++++++
>>   package/libiio/libiio.hash |  2 ++
>>   package/libiio/libiio.mk   | 50 ++++++++++++++++++++++++++++++++++++++++++++++
>>   5 files changed, 136 insertions(+)
>>   create mode 100644 package/libiio/Config.in
>>   create mode 100644 package/libiio/S99iiod.sh
>>   create mode 100644 package/libiio/libiio.hash
>>   create mode 100644 package/libiio/libiio.mk
>
> Thanks, applied, after doing a bunch of changes:
>
>      [Thomas:
>       - Remove changelog from the commit log.
>       - Rename init script to S99iiod instead of S99iiod.sh
>       - Remove "status" command from init script, and implement "restart"
>         instead.
>       - Add dependency on thread support in toolchain.
>       - Fixup indentation in the .mk file.
>       - Fixup wrapping in the Config.in help text.]
>
> Also, if you don't have any /sys/bus/iio/devices directory, the iiod
> daemon doesn't start, with a mysterious "Unable to create context"
> message, which only appears if you start iiod manually (not from the
> init script). Maybe it should be improved a bit: make sure to have a
> proper error message, and make sure it gets shown when iiod is started
> from the init script.
>
> Thanks!
>
> Thomas
>

-- 
--
Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, William A. Martin, Margaret Seif

  reply	other threads:[~2015-01-07  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  9:34 [Buildroot] [PATCH v5] libiio: new package Paul Cercueil
2014-12-21 21:39 ` Thomas Petazzoni
2015-01-07  8:55   ` Paul Cercueil [this message]
2015-01-07  9:00     ` Thomas Petazzoni

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=54ACF478.4080509@analog.com \
    --to=paul.cercueil@analog.com \
    --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