[Mesa-dev] [PATCH 2/2] radv: Add new flag for LLVM dependecies with vulkan
emil.l.velikov at gmail.com
Wed Oct 5 12:16:45 UTC 2016
On 2 October 2016 at 20:45, Tobias Droste <tdroste at gmx.de> wrote:
> This reuse the same logic gallium uses to determine if LLVM is needed or
> --enable-vulkan-llvm is set to yes if at least one vulkan driver is
> active and the host is i3*6 or x86_64.
> To build vulkan drivers without LLVM (e.g. intel) one has to add
> In order to make this all work the vulkan driver check has to move
> either diretcly below or directly above the gallium driver checks.
> Move them below the gallium driver stuff.
Having a blond moment here - is there an actual issue with the way
(Dave/Bas) did the Vulkan/LLVM detection ?
If the goal is to have a more gallium-like approach that isn't
applicable since the gallium aux modules (using LLVM) are linked in
every driver - regardless if it uses them or not. Admittedly one could
untangle this and make the LLVM requirement implicit as requesting a
driver which uses LLVM.
Even then, some modules can optionally make use of it (LLVM) for which
we'll still need the toggle :-\
Afaict RADV does not use the gallium aux module so the above should
not be needed, no ?
More information about the mesa-dev