Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/8 v2] package/libftdi: fix libftdi.pc
Date: Sun, 25 Jan 2015 22:13:48 +0100	[thread overview]
Message-ID: <1422220435-18689-2-git-send-email-s.martin49@gmail.com> (raw)
In-Reply-To: <1422220435-18689-1-git-send-email-s.martin49@gmail.com>

This patch fixes libftdi pkg-config module, so that packages linking
against libftdi correctly have all needed CFLAGS and LIBS defined,
especially when running a static build.

Fixes:
  http://autobuild.buildroot.org/results/e90/e90b4d5ad79d99487f21c9d18581e8eba7034501/

Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>

---
change v1->v2:
- libusb as "Require" (ThomasP)
---
 ...bftdi.pc-requires-libusb-fix-static-build.patch | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 package/libftdi/0002-libftdi.pc-requires-libusb-fix-static-build.patch

diff --git a/package/libftdi/0002-libftdi.pc-requires-libusb-fix-static-build.patch b/package/libftdi/0002-libftdi.pc-requires-libusb-fix-static-build.patch
new file mode 100644
index 0000000..ee47af6
--- /dev/null
+++ b/package/libftdi/0002-libftdi.pc-requires-libusb-fix-static-build.patch
@@ -0,0 +1,27 @@
+From d3d6ca63cb86727533d7d83c98e70002bb04f343 Mon Sep 17 00:00:00 2001
+From: Samuel Martin <s.martin49@gmail.com>
+Date: Wed, 21 Jan 2015 11:18:59 +0100
+Subject: [PATCH] libftdi.pc: requires libusb (fix static build)
+
+---
+ libftdi.pc.in | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/libftdi.pc.in b/libftdi.pc.in
+index 2061b91..57f0a09 100644
+--- a/libftdi.pc.in
++++ b/libftdi.pc.in
+@@ -5,8 +5,8 @@ includedir=@includedir@
+ 
+ Name: libftdi
+ Description: Library to program and control the FTDI USB controller
+-Requires:
++Requires: libusb
+ Version: @VERSION@
+-Libs: -L${libdir} -lftdi -lusb
++Libs: -L${libdir} -lftdi
+ Cflags: -I${includedir}
+ 
+-- 
+2.1.0
+
-- 
2.2.2

  reply	other threads:[~2015-01-25 21:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 21:13 [Buildroot] [PATCH 0/8] Misc. fixes around libftdi Samuel Martin
2015-01-25 21:13 ` Samuel Martin [this message]
2015-02-01 22:31   ` [Buildroot] [PATCH 1/8 v2] package/libftdi: fix libftdi.pc Thomas Petazzoni
2015-01-25 21:13 ` [Buildroot] [PATCH 2/8] package/libiio: update cmake code for libxml2 detection Samuel Martin
2015-01-27 21:16   ` Arnout Vandecappelle
2015-03-02 20:35     ` Samuel Martin
2015-02-14 21:15   ` Thomas Petazzoni
2015-02-14 23:33     ` Samuel Martin
2015-01-25 21:13 ` [Buildroot] [PATCH 3/8] package/libftdi: bump to version 0.20 Samuel Martin
2015-01-25 21:13 ` [Buildroot] [PATCH 4/8] package/libftdi1: new package Samuel Martin
2015-01-27 22:10   ` Arnout Vandecappelle
2015-01-25 21:13 ` [Buildroot] [PATCH 5/8] package/avrdude: depends on libftdi1 instead of libftdi Samuel Martin
2015-01-25 21:13 ` [Buildroot] [PATCH 6/8] package/openocd: " Samuel Martin
2015-01-25 21:13 ` [Buildroot] [PATCH 7/8] package/cmake: bump to version 3.1.1 Samuel Martin
2015-01-25 21:13 ` [Buildroot] [PATCH 8/8] package/cmake: only build what is necessary Samuel Martin
2015-03-04 23:30   ` Romain Naour

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=1422220435-18689-2-git-send-email-s.martin49@gmail.com \
    --to=s.martin49@gmail.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