No, this won't be added to meta-qt5 layer, because it's not the right fix.
If you're happy with empty packages, then you don't need meta-qt5 at all.
Empty packages are useless and bitbake is right not to create them.
My guess is that you don't have all necessary PACKAGECONFIGs enabled for
qtbase
Hey,
thanks, that solved my problem! Should probably added to the qt5 layer?
Best
On Tue, Apr 25, 2017 at 9:51 PM, Martin Kelly wrote:
> On 04/25/2017 07:41 AM, Malte Thiel wrote:
>
>> Hello,
>>
>> I am trying to compile a Qt 5.8 application using the master branch
>> of meta-qt5/recipes-qt/q
On 04/25/2017 02:14 AM, Patrick Ohly wrote:
Native recipes must be called -native. This is more than just a
recommendation, there's actual code which checks for the suffix.
Not following that rule broke swtpm-wrappers when using the "usrmerge"
DISTRO_FEATURE, because the code in native.bbclass
Signed-off-by: Armin Kuster
---
.../freediameter/files/freeDiameter.conf | 250 +
recipes-security/freediameter/files/init | 160 +
.../freediameter/files/no_test_run.patch | 12 +
.../freediameter/freediameter_1.2.1.bb |
On 4/20/17 5:04 PM, Martin Kelly wrote:
> Hi,
>
> After compiling a package with GCC 6, I noticed the following error,
> which is a known issue:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
>
> The problem is caused by adding -isystem /usr/include, which breaks the
> GCC 6's #include
I am using
- meta-xilinx and meta-xilinx-tools @ branch 2017.1
- meta-openembedded, poky @ branch morty
When I bitbake core-image-minimal I get the following error. Can you
suggest me a solution?
ERROR: Nothing PROVIDES 'python3-pyyaml-native'. Close matches:
python-pyyaml-native
python3
Signed-off-by: Khem Raj
---
.../0001-Fix-fallthrough-warnings.patch| 237 +
.../0002-Fix-printf-overflow-warnings.patch| 57 +
recipes-devtools/elfutils/elfutils_0.148.bb| 2 +
3 files changed, 296 insertions(+)
create mode 100644
recipes-d
"Burton, Ross" writes:
> On 24 April 2017 at 23:00, Nathan Lynch wrote:
>
>> Does adding this patch to lttng-modules work around it?
>>
>
> Yes, it fixes the build here. I'll throw it at the autobuilder now, can
> you send a patch with a commit message that isn't "someone told me to try
> this"
On 04/25/2017 07:41 AM, Malte Thiel wrote:
Hello,
I am trying to compile a Qt 5.8 application using the master branch
of meta-qt5/recipes-qt/qt5/ (For 5.8 support).
Within my recipe I have:
RDEPENDS_${PN} = "libgcc glibc qtbase [...] qtdeclarative"
My recipe (and therefore the application) co
Hello Paul,
thanks for the try. It should means that there is a detail on my setup
which prevents the build from being done. I encounter the error on the
commits id your provided too. I also tried being on last tag on poky
project for morty branch, without success. I also suspected my python
co
On Tue, Apr 25, 2017 at 11:15 AM, Alvaro Garcia wrote:
> Hi! This worked perfectly!
>
> But now I have the following problem:
> If I set prefered virtual/libgl as my nvidia recipe, then mesa is not
> installed and when xorg-xserver is compiling the library libepoxy cannot
> compile because of: No
Hi! This worked perfectly!
But now I have the following problem:
If I set prefered virtual/libgl as my nvidia recipe, then mesa is not
installed and when xorg-xserver is compiling the library libepoxy cannot
compile because of: No package 'egl' found (because this is provided by
mesa I guess)
If I
Hello,
I am trying to compile a Qt 5.8 application using the master branch
of meta-qt5/recipes-qt/qt5/ (For 5.8 support).
Within my recipe I have:
RDEPENDS_${PN} = "libgcc glibc qtbase [...] qtdeclarative"
My recipe (and therefore the application) compiles fine. However, in
do_rootfs I get the
On Tue, Apr 25, 2017 at 01:58:25PM +0300, Alexander Kanavin wrote:
> On 04/25/2017 12:09 PM, Olivier Sobrie wrote:
>
> > This patch ensures that libQtXml is build before libQtDBus and that
> > both libQtGui and libQtNetwork are built before libQt3Support.
>
> Applied, thanks. Please add a [meta-q
On 04/25/2017 12:09 PM, Olivier Sobrie wrote:
This patch ensures that libQtXml is build before libQtDBus and that
both libQtGui and libQtNetwork are built before libQt3Support.
Applied, thanks. Please add a [meta-qt4] to the subject, so that it's
easier to see which layer the patch is intende
On 24 April 2017 at 23:00, Nathan Lynch wrote:
> Does adding this patch to lttng-modules work around it?
>
Yes, it fixes the build here. I'll throw it at the autobuilder now, can
you send a patch with a commit message that isn't "someone told me to try
this"? :)
Ross
--
__
Native recipes must be called -native. This is more than just a
recommendation, there's actual code which checks for the suffix.
Not following that rule broke swtpm-wrappers when using the "usrmerge"
DISTRO_FEATURE, because the code in native.bbclass which cleans up
DISTRO_FEATURES for native reci
The libQtDBus requires libQtXml at link time otherwise it fails with
the following error:
x86_64-pokysdk-linux-g++
--sysroot=/home/build/dev/yocto/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux
-Wl,-O1 -fno-exceptions -Wl,--no-undefined -Wl,-O1
-Wl,-rpath,/opt/poky-oso/2.2/sysroots/x86_64
On Mon, Apr 24, 2017 at 7:25 PM, wrote:
> Hello,
> I am currently encountering an issue with meta-raspberry and more
> specifically Raspberry Pi 3 build. Since I was not sure the problem was
> not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both
> checked out on morty, and meta
Hi
I am trying to include CPPCheck into Yocto to be used by CMake as a Cmake
Module.
Hence when building my application recipes that are based on using CMake
build as build system, CPPCheck is performed.
What I currently did, was:
Making a recipe for CPPCheck to be used in the toolchain by:
BBCLAS
On Mon, Apr 24, 2017 at 10:20 PM, Mike Looijmans
wrote:
> On 24-04-17 16:29, Martin Jansa wrote:
>>
>> * gnutls depends on nettle-3.1* since 3.4.0:
>> The requirement for nettle was bumped from 3.0 to 3.1 in gnutls_3_4_0
>>
>> https://gitlab.com/gnutls/gnutls/commit/c84129af91b21d33ffe086e507632
21 matches
Mail list logo
