From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] pulseview: new package
Date: Wed, 8 Apr 2015 22:38:51 +0200 [thread overview]
Message-ID: <20150408223851.3abe5405@free-electrons.com> (raw)
In-Reply-To: <CAMpxmJVGxtExSQmdjqYvbXuw2hDvObnyfaN27RG+dn88ipu=jw@mail.gmail.com>
Hello,
On Wed, 8 Apr 2015 22:29:06 +0200, Bartosz Golaszewski wrote:
> 2015-04-08 21:12 GMT+02:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
> > I've reproduced the problem in the autobuilder directly, and the
> > problem is fairly clear:
>
> Thanks for the investigation!
No problem, you're welcome. Without having access to the autobuilders,
it might be hard to reproduce some of the issues, so I'm definitely
happy to reproduce them and provide more details as needed.
> > So, generating the C++ bindings requires Doxygen. And Doxygen is not
> > part of the mandatory Buildroot dependencies, and not packaged in
> > Buildroot as a host package.
>
> Can we add an error message similar to those emitted when e.g. git or
> svn is missing. but for doxygen (only when libsigrokcxx is selected)?
Yes, we can, but it's a bit annoying. It means that building
libsigrokcxx + pulseview will most likely not be tested much by the
autobuilders.
> > So, in the mean time, I've marked libsigrokcxx as broken, as well as
> > pulseview. I believe the best solution is probably to create a
> > host-doxygen package (or convince the libsigrok developers to not use
> > something such as doxygen to generate C++ bindings). Can you look into
> > this?
>
> C++ bindings are generated using xml files created by doxygen. I will
> take a look tomorrow, but it may be impossible to drop using doxygen
> without having to do a major overhaul of libsigrokcxx. I think that
> host-doxygen is a more feasible solution unless we can demand user to
> install doxygeb on the host machine.
Can you have a quick look at how annoying (or not) it would be to create
a host-doxygen package? This would be the nicest solution, of course
assuming it doesn't require millions of dependencies that would also
have to be packaged in Buildroot.
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-08 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 10:08 [Buildroot] [PATCH v2] pulseview: new package Bartosz Golaszewski
2015-03-20 22:07 ` Thomas Petazzoni
2015-03-23 22:09 ` Bartosz Golaszewski
2015-04-06 21:43 ` Thomas Petazzoni
2015-04-08 10:45 ` Bartosz Golaszewski
2015-04-08 14:07 ` Bartosz Golaszewski
2015-04-08 14:29 ` Thomas Petazzoni
2015-04-08 14:38 ` Bartosz Golaszewski
2015-04-08 16:05 ` Bartosz Golaszewski
2015-04-08 19:12 ` Thomas Petazzoni
2015-04-08 20:29 ` Bartosz Golaszewski
2015-04-08 20:38 ` Thomas Petazzoni [this message]
2015-04-09 10:19 ` Bartosz Golaszewski
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=20150408223851.3abe5405@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