On 18 January 2017 at 18:12, Jose Fonseca <jfons...@vmware.com> wrote:
>>> In order to untangle things we want to have a distinction between the >>> gallium (gallivm afaict) and other users - RADV presently. >>> So how about we update the RADV instances and ensure that the we set >>> the HAVE_{RADV,}_LLVM lot appropriately. Latter will be picky but >>> overall things should work w/o annoyances that HAVE_GALLIUM_LLVM >>> brings ? > I honestly don't even understand why we'd want to build parts of the tree > with LLVM while hiding LLVM from other components. We can't we just build > everything with LLVM and avoid this combinatorial explosion of wierd options > that are nothing more than yet another way the build can break!!? > Sadly the combinatoric explosion has been there for a while. Based on how well my previous attempts to resolve similar issues (see the "platforms" topic) I doubt we'll even get to fix that. > But if a separate option is truly necessary, have the newcomer pick a > different name, or something. > That's pretty much what I suggested above. Tobias can you please give it a try ? Thanks Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev