All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/opencv: fix opencv.pc generation
Date: Sun, 17 May 2015 20:44:40 +0200	[thread overview]
Message-ID: <871tif82nb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1431867794-6291-1-git-send-email-s.martin49@gmail.com> (Samuel Martin's message of "Sun, 17 May 2015 15:03:14 +0200")

>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:

 > This change fixes build of packages depending on opencv and using
 > pkg-config to get the opencv LDFLAGS, which were wrongly ordered for
 > static build and included absolute path pointing to the host system
 > libraries instead of the sysroot ones.

 > This patch fixes build issues with gst1-plugins-bad and vlc.

 > This change introduce and new patch to opencv, which is already merged
 > upstream [1].

 > Fixes:
 >   http://autobuild.buildroot.net/results/c70/c70f793c7c3b380428d6e2e622a90805cffc4dd1/
 >   ... and many others

 > [1] https://github.com/Itseez/opencv/commit/eceada586bbf18fc267e437522ec4f1f23ddc656

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

Committed, thanks.

 > ---
 > Note that this fix is for upcoming 2015.05 release, and I am already
 > preparing a series bumping of the opencv package for the next release. :)

great!

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2015-05-17 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17 13:03 [Buildroot] [PATCH] package/opencv: fix opencv.pc generation Samuel Martin
2015-05-17 15:36 ` Yann E. MORIN
2015-05-17 18:44 ` Peter Korsgaard [this message]

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=871tif82nb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.