setup.py: ship the clang plugin

[mook]

Without this, installed packages don't work very well for indexing.

Note that I don't know my way around setuptools/distribute/whatever so don't trust me on this - it's more of a bug report that not doing this doesn't work, I guess? Anyway, with setup.py install, it didn't include the .so so actually using clang wasn't very productive. If we're going to ship the rest of the clang plugin anyway...

[erikrose]

The idea is sane, though we should probably use MANIFEST.in instead. I vaguely recall package_data being a distutils thing, obsolete, and unreliable in some way.

I can see us leaving trilite out of this mix for now, since we have not-quite-horrible instructions in deployment.mkd about installing it. However, perhaps it would be friendlier to install it, too.

[erikrose]

We could probably make a custom distutils Command (and build_ext) subclass and trigger it from setup(ext_modules=[that class]). We can probably do whatever we want from a command, including building the shared libs. Ideally, setup() won't be too disappointed that an extension module isn't actually built. See M2Crypto's setup.py for an example of a custom build_ext subclass.

Then doing setup.py install will run make, and we'll be able to build arch-specific eggs with all the shared libs (maybe even trilite!) included.

[erikrose]

Moved the automatically-run-make thread to a dedicated bug: https://bugzilla.mozilla.org/show_bug.cgi?id=881490.