After buinding and installing the SDK using agl-image-graphical-qt5-crosssdk I am able to see and use wayland-scanner on my host.
Regards,
Bogdan Ilies
On Sat, 27 Jun 2020 at 19:41, ilies bogdan via lists.automotivelinux.org<ilies_06=yahoo.com@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:Hi Marius,I see.. I will let you know once done.Thank you,Bogdan Ilies
On Sat, 27 Jun 2020 at 19:25, Marius Vlad<marius.vlad@xxxxxxxxxxxxx> wrote:Hi Bogdan,
On 6/27/20 8:03 PM, ilies bogdan via lists.automotivelinux.org wrote:
> Hi Marius,
>
> Thank you for the explanation.
> I saw that patch but I did not know how to use it.
> I think that I was not able to find it in sdk as I used an image
> different from agl-image-graphical-qt5-crosssdk.
> Today I noticed that this image includes wayland-scanner as part of
> meta-agl-profile-graphical-qt5/recipes-platform/images/agl-image-graphical-qt-crosssdk.inc
> I am building that image and check to see if available then.
> Isn't agl-compositor generating the headers for agl-shell and
> agl-desktop-shell so that they can be used from there?
It does, but only the server ones, which won't be really useful for
clients, even if we were to install them, which we do not. We should
always use the XMLs instead of the generated headers as to be sure that
both the client/server use the same thing. The compositor has a
agl-compositor pc file for you to use in order to retrieve the correct
path of the protocols. Would suggest to use that instead of copy-pasta
them in your client.
Unfortunately applications in AGL don't really do that (I have Jira
ticket for this) but you're not planning on using that anyway, so using
the SDK you should have the PKG_CONFIG_* paths exported correctly.
Would be nice if you could get back either way to see if building that
image does the trick.
I do remember in the past that I've used the host's wayland-scanner to
generate the client headers. It is less than ideal, but it works, as the
tool is pretty stable at this point. Use this as your last approach.
Mixing SDK with host tools might be a bit finicky.
>
> Regards,
> Bogdan Ilies
>
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature>
>
> On Sat, 27 Jun 2020 at 16:36, Marius Vlad
> <marius.vlad@xxxxxxxxxxxxx> wrote:
> Hi,
>
> wayland-scanner is part of wayland which will need to be built twice in
> order to use it from the SDK. The scanner is present in the SDK just
> that it will (only) include the target one.
>
> There's a wayland-native package which I guess OE/poky/yocto uses it to
> first bootstrap wayland, using the native one to build/generate the
> headers need build those headers.
>
> Might want to try out https://patchwork.openembedded.org/patch/154282/
> and see if that works?
>
> IDK, maybe we can have a bbappend recipe for wayland and include that if
> the above seem to work?
>
>
> On 6/26/20 12:24 AM, ilies bogdan via lists.automotivelinux.org wrote:
> > Hi,
> >
> > I have successfully build an image containing agl-compositor and in
> > order to experiment with this I would need wayland-scanner as part of
> > SDK so that I can generate agl-shell and agl-shell-desktop-client
> > headers from agl-shell.xml and agl-shell-desktop.xml respectively.
> > Does anybody know how can I include it in SDK?
> >
> > Or can I include the headers somehow into SDK?
> >
> > Thank you,
> > Bogdan Ilies
>
> >
> >
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature>>
> >
>
> --
> Marius Vlad
>
>
>
>
--
Marius Vlad
