On Fri, Oct 21, 2016 at 7:31 AM, Mike Lothian wrote:
> Does this need to be target CPU rather than host?
target and host should always be the same for Mesa, as far as I
understand. See
https://gcc.gnu.org/onlinedocs/gccint/Configure-Terms.html
___
mesa-
On Fri, Oct 21, 2016 at 9:11 AM, Emil Velikov
wrote:
> On 21 October 2016 at 16:58, Jason Ekstrand wrote:
>
> > Will do. Do I need to add intel_icd.@host_cpu@.json to EXTRA_DIST?
> >
> No need, since new file will/should be regenerated as one runs configure.
>
> >>
> >> With those the series is
On 21 October 2016 at 16:58, Jason Ekstrand wrote:
> Will do. Do I need to add intel_icd.@host_cpu@.json to EXTRA_DIST?
>
No need, since new file will/should be regenerated as one runs configure.
>>
>> With those the series is:
>> Reviewed-by: Emil Velikov
>
>
> Thanks! Sorry this has taken s
On Fri, Oct 21, 2016 at 7:31 AM, Mike Lothian wrote:
> Does this need to be target CPU rather than host?
>
No, we want host. See also
https://www.gnu.org/software/autoconf/manual/autoconf-2.65/html_node/Specifying-Target-Triplets.html
> On Fri, 21 Oct 2016 at 14:53 Emil Velikov
> wrote:
>
>
On Fri, Oct 21, 2016 at 6:52 AM, Emil Velikov
wrote:
> Thank you very very very much for this, Jason !
>
If you're happy and I'm happy, I'd say we've got ourselves a solution!
> On 21 October 2016 at 01:07, Jason Ekstrand wrote:
>
> > drivers because they may put it in /usr/local or $HOME
Does this need to be target CPU rather than host?
On Fri, 21 Oct 2016 at 14:53 Emil Velikov wrote:
> Thank you very very very much for this, Jason !
>
> On 21 October 2016 at 01:07, Jason Ekstrand wrote:
>
> > drivers because they may put it in /usr/local or $HOME/.local or some
> > other
>
Thank you very very very much for this, Jason !
On 21 October 2016 at 01:07, Jason Ekstrand wrote:
> drivers because they may put it in /usr/local or $HOME/.local or some
> other
Drop the "/usr/local or " part. The dynamic linker looks in there, by default.
> more exotic location. In t
Dave asked for a different commit message that describes the problem a bit
better:
anv: Suffix the intel_icd file with the host CPU
Vulkan has a multi-arch problem... The idea behind the Vulkan loader is
that you have a little json file on your disk that tells the loader
where
to
Vulkan has a multi-arch problem... The idea behind the Vulkan loader is
that you have a little json file on your disk that tells the loader where
to find drivers. The loader looks for these json files in standard
locations, and then goes and loads the my_driver.so's that they specify.
This allows
