[meta-xilinx] [PATCH 3/7] xsct-tc: append the local system's /usr/bin dir as Xvfb fallback

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: Jean-Francois Dagenais [mailto:jeff.dagenais at gmail.com]
> Sent: Friday, July 07, 2017 2:51 PM
> To: Manjukumar Harthikote Matha <MANJUKUM at xilinx.com>
> Cc: Sai Pavan Boddu <saipava at xilinx.com>; Cyril Chemparathy <cyrilc at xilinx.com>;
> git <git at xilinx.com>; michal.simek at xilinx.com; meta-xilinx at yoctoproject.org
> Subject: Re: [PATCH 3/7] xsct-tc: append the local system's /usr/bin dir as Xvfb
> fallback
>
>
> > On Jul 7, 2017, at 17:14, Manjukumar Harthikote Matha <manjukumar.harthikote-
> matha at xilinx.com> wrote:
> >
> > I will check with team here on this requirement. I am not sure if it is a right idea to
> include /usr/bin in the PATH variable as of now. Maybe there is a way to append this
> in local.conf or set it in your local PATH
>
> I understand your concern. This was by far a comfortable change to make...
>
> I have to say though, it is also a bad idea to invoke an x11 server to run a command-
> line compiler!! :-P
>
> There are probably other pretty yocto-style ways to do this, I just couldn't find them.
> The major point of my submission was to reveal the fact that when a build doesn't
> have "x11" in the DISTRO_FEATURES, the xsct tools fail to launch!
>

xsct in general requires xvfb to be installed on your host, I don't think it works without it.
I am assuming you encountered the issue where it complained about xvfb not available.
We tested our distro removing X11 as well (in case of microblaze) and we did not encounter this issue but that might be due to the fact that xvfb was installed on our host machine.

Thanks,
Manju

> This is not a local build (local.conf) related quirk, but a distro related choice. That is
> why in my opinion, local.conf is not suited for this solution. Of course, anything that
> can be put in a local.conf will also work in the distro conf file.
>
> Cheers.


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.