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