From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] libsigrok: add host-doxygen dependency for C++ bindings
Date: Sun, 12 Apr 2015 18:58:40 +0200 [thread overview]
Message-ID: <20150412185840.2f07e37e@free-electrons.com> (raw)
In-Reply-To: <1428659399-28620-3-git-send-email-bgolaszewski@baylibre.com>
Dear Bartosz Golaszewski,
On Fri, 10 Apr 2015 11:49:58 +0200, Bartosz Golaszewski wrote:
> Doxygen is required to generate xml files required by libsigrokcxx
> build system.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> package/libsigrok/libsigrok.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've applied, after adding host-python (or host-python3) in the
dependencies when building the C++ bindings. Otherwise, the creation of
the C++ bindings fail, due to Python being too old: some autobuilders
only have Python 2.6, while libsigrok requires at least Python 2.7.
Committed with this fixed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-12 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 9:49 [Buildroot] [PATCH v3 0/3] fix pulseview build failures Bartosz Golaszewski
2015-04-10 9:49 ` [Buildroot] [PATCH v3 1/3] doxygen: new package Bartosz Golaszewski
2015-04-12 16:55 ` Thomas Petazzoni
2015-04-13 10:31 ` Bartosz Golaszewski
2015-04-13 11:27 ` Thomas Petazzoni
2015-04-10 9:49 ` [Buildroot] [PATCH v3 2/3] libsigrok: add host-doxygen dependency for C++ bindings Bartosz Golaszewski
2015-04-12 16:58 ` Thomas Petazzoni [this message]
2015-04-10 9:49 ` [Buildroot] [PATCH v3 3/3] Revert "libsigrok: mark libsigrokcxx as broken" Bartosz Golaszewski
2015-04-12 16:59 ` 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=20150412185840.2f07e37e@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