Georg Rudoy posted on Sun, 03 May 2015 17:04:54 +0300 as excerpted: > Speaking of llvm, media-libs/mesa has "llvm" use flag. Why should user > care if it's llvm or whatever?
The local use-description tells the store there: "Enamble LLVM backend for Gallium3D" In this case, LLVM is the feature, and it is billed as such by upstream. Gallium3D can optionally use LLVM to compile shading-language programs to run on the programmable shaders. An alternative USE flag name would be shading-vm, or similar, but because upstream actually "sells" the feature as an LLVM shading language backend, LLVM really is as much the feature as would be shading-vm or shading-compiler or some such, except because it /does/ pull in an LLVM that people might not otherwise need on their machine, the llvm flag is actually more descriptive, since it says what it pulls in as a dep, as well. Of course, if there were multiple choices, then it could either be a generic shading-compiler flag, with flags for each compiler as well, or it could be setup as a USE_EXPAND list, sl_llvm, sl_gcc, sl_amd, sl_intel... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
