# Not yet. # --enable-nine \
 

Any particular reason why? I have to rebuild mesa just to enable nine, it's just a bit of a hassle.

I have it enabled in my custom build, but unless you're running Wine, it's not too useful. Plus, it hasn't been tested enough to prove stable. You can enable it and rebuild Mesa to have it, but as stated, unless you're running Wine for Windows applications, it won't be much good.

Yeah I use wine with d3dadapter, already rebuilt mesa with nine enabled was just wondering why slackware doesn't enable it when it's automatically enable in all other distros now through the binary.

Slackware also doesn't include a few optional support vectors as well such as libomxil-bellagio and libclc.

The reason I asked is because in the mesa slackbuild itself he commented

# Not yet.
# --enable-nine \

indicating that will be enabled, I just wanted to know the reason it's not. Maybe he figures it's interfering with the other code, I don't know, don't see how but again, I'm not a coder/programmer, in any case I'll stop asking a simple question.

It is probably due to ReaperX7's second sentence in his first post.

Slackware is not one to just jump on the bandwagon, even if other distros have. Software needs to be proven reliable before it is incorporated into Slackware. Since it is labeled as "Not yet", it was probably tested at one point, but may have introduced instability wtih something. Or maybe one of the core developers had it enabled on their builds, but Pat felt it wasn't ready yet so he decided to not include it (but probably commented it out instead of removing it as a reminder to revisit it later).

But, there is no way of knowing the reason for sure unless Pat (or one of the core devs who is familiar with it) steps in to provide that information. Anything else is just speculation.

I asked the same thing here http://www.linuxquestions.org/questi...ml#post5409568
As far as i understand it shouldn't effect the rest of mesa at all and needs the application to call for that function.
It needs an patched wine and then you need to enable it in wine config.
I can understand that it's not tested very much yet but unless anything tries to use the d3dadapter then it shouldn't matter.
But i might be wrong since my knowledge isn't big in this area.

Thanks for the news, it's so new it doesn't show on the site yet.

It's also going to be less useful on x86_64 unless you're building Wine64 only. It may be enabled on 32-bit systems, but on x86_64 it's entirely optional.

Yeah I already noticed that, but it doesn't bother me, I've been using 32bit on my 64 bit all along since there's no big difference.

The additional support vectors libomxil-bellagio (OpenMAX for multimedia) and libclc (OpenCL via LLVM/Clang) actually are more useful, but as far as I know only AMD Radeons support OpenMAX and OpenCL fully. Mesa's Nouveau currently is still working on OpenCL, but I'm not sure if they're adding OpenMAX support ever, as far as Intel is concerned, neither is known fully if they support these features though they do have a project called beignet, but regardless those are far more useful than DirectX9 support at the moment.

Don't get me wrong, you can, and might benefit from rebuilding and enabling these features, provided you add the correct packages to support them, and a combination of nine, libomxil-bellagio, and libclc would give you a rounded out Mesa support system.

If you want to play around with these libraries I have them in my git repo. Just clone it and build the packages after grabbing copies of sources. Libclc' source is git clone only, and libomxil-bellagio requires a patch to build which I included, but nine should build without any extras.