Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Phidgets library and web server?
Date: Mon, 25 Aug 2014 20:26:43 +0300	[thread overview]
Message-ID: <20140825172643.GA29733@tarshish> (raw)
In-Reply-To: <alpine.DEB.2.02.1408241012500.2336@tavas.tkos.co.il>

Hi Yonatan,

On Sun, Aug 24, 2014 at 10:40:39AM +0300, Jonathan Ben Avraham wrote:
> I have integrated the Phidgets (http://www.phidgets.com/)
> libphidget-2.1.8.20140319 and phidgetwebservice into my Buildroot tracking
> branch.
> 
> I have tested on x86 and i.MX287.
> 
> The Phidgets software license is LGLP Version 3. No publicly accessible
> repo, just tarball downloads.
> 
> Uses autoconf build system.
> 
> Requires glibc and libusb.
> 
> From the Phidgets site:
> 
> "Phidgets are a set of user friendly building blocks for low cost USB
> sensing and control from your PC."
> 
> My client is using Phidgets products on a custom i.MX287 board rather than a
> PC, for control of a home kitchen and restaurant appliance using GPIO's and
> ADC's. I personally have no commercial interest in Phidgets.
> 
> I can commit to maintaining for six months on arm, x86 and ppc.
> 
> My question to you is, is this the type of package that we want to add to
> Buildroot? Should I submit patches? Or is there a "contrib" dir where I
> could put the patches?

Just submit a patch.

One problem I see with libphidget is that there seems to be no way to download 
older versions. The only downloadable tarball is at 
http://www.phidgets.com/downloads/libraries/libphidget.tar.gz, which 
apparently points to the latest version. Having an automatically upgraded 
download source is strongly discouraged, as it makes the build produce 
different results at different times.

The preferred solution would be to have upstream provide access to immutable 
per-version tarballs.

An alternative solution might be to store the libphidget tarballs on the 
Buildroot backup download server (http://sources.buildroot.net).

Any other suggestions?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  parent reply	other threads:[~2014-08-25 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24  7:40 [Buildroot] Phidgets library and web server? Jonathan Ben Avraham
2014-08-24  7:56 ` Oli Vogt
2014-08-25 17:26 ` Baruch Siach [this message]
2014-08-26 11:59   ` Jonathan Ben Avraham

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=20140825172643.GA29733@tarshish \
    --to=baruch@tkos.co.il \
    --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