Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libFTDI major version update 1. This version can coexists beside the 0.x version (libftdi.so, libftdi1.so).
Date: Fri, 3 Oct 2014 15:02:18 +0200	[thread overview]
Message-ID: <20141003150218.2bb79dfd@free-electrons.com> (raw)
In-Reply-To: <2.c5a9d6940ebdbeb712d0@polarstar>

Hello,

On Thu, 02 Oct 2014 09:52:10 +0200, daniel.sangue at sangue.ch wrote:

> Well im new to buildroot and git and also to linux. I am at the
> buttom of the learning curve related to this topics. Thank you for
> your time and feedback.

No problem, you're welcome!

> >According to your libftdi1.mk file comments, it looks like C++
> >support can be autodetected. So maybe it's not really worth the
> >effort having an option for that: we could just enable C++ support
> >when available, and that's it.
> 
> ok, i removed the additional c++ binding option. I admit that i just
> copy pasted it from the existing libftdi(0) package.

Ah, ok.


> >> +LIBFTDI1_VERSION = 1.1
> >> +LIBFTDI1_SOURCE = libftdi1-$(LIBFTDI1_VERSION).tar.bz2
> >> +LIBFTDI1_SITE =
> >> http://www.intra2net.com/en/developer/libftdi/download/
> >
> >Please add LIBFTDI1_LICENSE and LIBFTDI1_LICENSE_FILES.
> 
> ok, i have added:
> IBFTDI1_LICENSE = LGPL2.1 GPL2
> LIBFTDI1_LICENSE_FILES = COPYING

That isn't good, the licensing is a bit more complicated. I think it
should be:

LIBFTDI1_LICENSE = LGPLv2.1 (libfti1), GPLv2 with exceptions (ftdipp1)
LIBFTDI1_LICENSE_FILES = LICENSE COPYING.GPL COPYING.LIB


> >Are you sure --{enable,disable}-libftdipp options are working for
> >CMake? It doesn't look like the usual way of passing CMake
> >configuration options, but maybe I'm missing something here.
> 
> No, i am not sure. I just can refere to the buildroot cmake example
> in the manual where LIBFOO_CONF_OPT is used:
> http://buildroot.uclibc.org/downloads/manual/manual.html#_infrastructure_for_cmake_based_packages

Yes, but it seems like the code you wrote using --enable-libftdipp and
--disable-libftdipp was copied from the other libftdi.mk package. Which
is autotools based, so --enable/--disable options make sense. But for a
CMake package, they clearly do not make sense.

I think, it should instead be:

ifeq ($(BR2_INSTALL_LIBSTDCPP),y)
LIBFTDI1_CONF_OPT = -DFTDIPP=ON
else
LIBFTDI1_CONF_OPT = -DFTDIPP=OFF
endif

You should test this with a non-C++ capable toolchain. For example
http://autobuild.buildroot.org/toolchains/configs/br-arm-basic.config
is a configuration with a minimal toolchain, having just thread support.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-10-03 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  7:52 [Buildroot] [PATCH 1/1] libFTDI major version update 1. This version can coexists beside the 0.x version (libftdi.so, libftdi1.so) daniel.sangue at sangue.ch
2014-10-02 12:45 ` Mike Zick
2014-10-02 12:56   ` Mike Zick
2014-10-03 13:02 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-01 14:18 Daniel Sangue
2014-10-01 14:45 ` 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=20141003150218.2bb79dfd@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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