On 11/17/20 1:36 PM, Marek Vasut wrote:
On 11/13/20 8:05 PM, Mark Hatle wrote:
On 11/12/20 4:30 PM, Marek Vasut wrote:
On 11/12/20 8:09 PM, Mark Hatle wrote:
On 11/12/20 12:07 PM, Marek Vasut wrote:
On 11/12/20 5:27 PM, Mark Hatle wrote:
On 11/12/20 10:20 AM, Marek Vasut wrote:
On 11/5/20 5:52 PM, Marek Vasut wrote:
On 11/5/20 5:06 PM, Mark Hatle wrote:
Ok, got an answer for you. What you are running is for embeddedsw
code that has not been released. (This is different from the
https://github.com/Xilinx/embeddedsw repository.)
What are you trying to do build? I suspect it's available through
a differently named recipe.
Either the hello-world example or the freertos10-xilinx , but they
_all_ depend on xilstandalone and so neither can be built anyway.
So, how can I obtain this patched embeddedsw code ?
Are there any news on this ? It seems v2020.2 also has the same
problem.
The issue is that the libxil component (replacement for libgloss) is
defined based on device tree and other components. This code doesn't
exist in the public repositories yet. (I'm working on trying to get
it released, but it's taking time.)
The existing embeddedsw can be used, but it's not integrated into the
Yocto Project build.
(This all is an area that I'm not terribly familiar with the existing
mechanisms, but I understand the new unreleased work.)
My expectation is that we will be pushing this as part of the master
work in the next 6 months. (I really don't want this to take all of
6 months before we have something that is usable!)
I'm not entirely sure waiting for another 6 months is going to work in
this case. Is there some workaround to build any of the
meta-xilinx-standalone recipes for v2019.1/v2019.2/v2020.1/v2020.2
releases or any other way to obtain those missing scripts ?
I would prefer to avoid implementing the entire set of build scripts
from scratch, since they are apparently already implemented somewhere
for at least four releases of meta-xilinx.
I will look, I'm not sure there is any existing way to get them from
within the Yocto Project build system.
If all that is missing is a couple of scripts from embeddedsw git, why
not push those scripts and be done with it ?
It's not a couple of scripts, it's the entire build environment (and related
components) within embeddedsw has/will be changing in a new version in the
future in order to facilitate how the Yocto Project builds will work, how the
usage of device trees will be in the future and for other reasons.
But all that should already be implemented somewhere for
v2019.1/v2019.2/v2020.1/v2020.2 versions of meta-xilinx and
meta-xilinx-standalone, so it shouldn't be that much work, right ?
I don't know of any work before 2020.1 when I became involved. If it's there
in older versions, it would be in the github in the rel-v2019.1 or rel-v2019.2
branches. 2020.1 and beyond I only know of the components for the embeddedsw
that has not yet been released.
--Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4783):
https://lists.yoctoproject.org/g/meta-xilinx/message/4783
Mute This Topic: https://lists.yoctoproject.org/mt/78053120/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
