From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/cutelyst: Fix build dependencies
Date: Wed, 1 Aug 2018 15:06:37 +0200 [thread overview]
Message-ID: <20180801150637.3e3403b1@windsurf> (raw)
In-Reply-To: <CACo8zOf7ukrnVpS0QUCA_YpmX7ApxApqGdadyTJn4yocF+juTg@mail.gmail.com>
Hello,
On Wed, 1 Aug 2018 09:55:43 -0300, Daniel Nicoletti wrote:
> > However, there are other build issues of the cutelyst package which
> > don't seem to be related:
> >
> > - http://autobuild.buildroot.net/results/b4b/b4bd0807fed721d8f553f1392e7d1fa51545d046/build-end.log
> >
> > Lots of Qt/C++ errors.
> Yeah, I have fixed a few right after the release, as they usually build fine
> when warnings are not enabled...
I'm not sure what you mean here. These errors still occur in the
autobuilders. Do we need to bump the cutelyst version ?
> > - http://autobuild.buildroot.net/results/555/555cf0cd59c9c832b15c604dae5bad3640f8b450/build-end.log
> >
> > Doxygen missing. We have a host-doxygen package in Buildroot, but it
> > would be a lot nicer of Cutelyst would not require Doxygen. Any
> > chance to make this optional ? We don't really care about building
> > documentation in the context of Buildroot.
> It does not require, it only uses if found and if make docs, I could
> add a BUILD_DOCS option but it's not very important IMO.
So according to your next e-mail, this failure is not due to
lrelease/doxygen missing, but only because libpwquality could not be
found ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-01 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 11:47 [Buildroot] [PATCH] package/cutelyst: Fix build dependencies Daniel Nicoletti
2018-08-01 12:27 ` Thomas Petazzoni
2018-08-01 12:55 ` Daniel Nicoletti
2018-08-01 13:00 ` Daniel Nicoletti
2018-08-01 13:06 ` Thomas Petazzoni [this message]
2018-08-01 13:11 ` Daniel Nicoletti
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=20180801150637.3e3403b1@windsurf \
--to=thomas.petazzoni@bootlin.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.