Hello,
we have got the problem that w/ the Yocto recipe and CMake install
targets as below always everything (headers and library or binary
respectively) is installed in the SDK.
The binary also goes into the SDK even though we just add it to
IMAGE_INSTALL based on a XILINX yocto build (rel-v2
Hi Pascal
I don't think your issue has something do to with CMake.
You are right IMHO. We checked again the pugixml installation behaviour
and it turned out we are experiencing the same issue.
we have got the problem that w/ the Yocto recipe and CMake install
targets
as below always every
Hi Ross,
DEPENDS += "bc-native dtc-native"
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"
Don't _append when you can just extend the assignment above.
I just did it that way for the moment since I wanted to circumvent merge
conflicts when I upgrade the
Hello,
it seems that even in the most current yocto u-boot recipes from
openembedded some general and also x86 specific dependencies are
missing.
The patch below adds them.
From 0502033c5e555abaadcb5e01faae041293e9 Mon Sep 17 00:00:00 2001
From: Eric Schwarz
Date: Tue, 3 Oct 2017 18:24
Am 09.10.2017 12:30, schrieb Burton, Ross:
On 8 October 2017 at 18:04, Eric Schwarz
wrote:
Don't _append when you can just extend the assignment above. I just
did it that way for the moment since I wanted to circumvent merge
conflicts when I upgrade the underlying recipes
Most likely a dependency problem of the package which fails w/ exit code
1.
Check the dependencies in the recipe and w/ Yocto's bitbake it self.
Cheers
Eric
Am 08.11.2017 16:49, schrieb Jerry Lian:
I am not sure whether it is a bug or an error: * Quite often, bitbake
will fail before finishin
Hi Jerry,
Am 01.12.2017 15:07, schrieb Jerry Lian:
I am new to embedded linux, and some concepts confuse me:
* I have downloaded an Autotools-based application to run on my board.
* If I boot the board with original image/original SDK, I normally
build/install it with steps:
- ./bootstrap
Am 01.12.2017 15:16, schrieb Eric Schwarz:
Hi Jerry,
Am 01.12.2017 15:07, schrieb Jerry Lian:
I am new to embedded linux, and some concepts confuse me:
* I have downloaded an Autotools-based application to run on my board.
* If I boot the board with original image/original SDK, I normally
in:
"... you may supply a custom install prefix directory to configure."
--- how?
There is IMHO no standardized variable available. Just look into the
configure script how the variable is named and if it is actually
available at all.
Thanks!
On Fri, Dec 1, 2017 at 9:34 AM, Eric S
arget.
On the target 'cp -Rfa /* /' should do it if the basic
directory structure fits to your rootFS.
--- copy (via scp) -then how do I know: what files to go which
folder?
--- can you explain:
"... you may supply a custom install prefix directory to configure."
---
Hello Jerry,
U-Boot depends on Python but the dependency is not included in the
U-Boot recipe AFAIK.
I have already sent a patchset which was not complete at that time to
the yocto mailinglist. Ross meant one needs to inherit from Python
U-Boot class in the recipe not just include a dependency
Hello,
is this the right mailing list to post new recipes for libraries to be
included in the openembedded layer and/or recipes patches, respectively?
Many thanks
Eric
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/list
12 matches
Mail list logo
