libpyne

This PR makes our C/C++ library a first class citizen following [these suggestions](http://lucumr.pocoo.org/2013/8/18/beautiful-native-libraries/).

This basically entails a complete refactor of the C++ side of the build system.  This has the following features:

* a single `libpyne` that you can link against
* a single `pyne.h` that can be included via `#include "pyne/pyne.h"`

Other features such as those implemented by FindPyne.cmake have all been maintained.  

Testing this feature likely involves blowing away the existing install dir as it is incompatible with the develop install.  I anticipate that this feature will be useful to folks like @makeclean.

For background, I need to do something similar for bright and figured that I'd practice on pyne :)
I know it isn't how cyclus works.  I wish it was and brought this up
before, but I was overruled.  And what if I, or somebody else doesn't want
to use cmake?  With this small change, compiling against pyne will become
trivial without any help from any build system.  I think that is a
fantastic feature to have and love using c/c++ libs that don't require
special compiler/linker flags.


On Sat, Jun 14, 2014 at 11:49 AM, Anthony Scopatz <notifications@github.com>
wrote:

> In cpp/pyne.h:
>
> > -  #define isnan(x) __isnand((double)x)
> > +#ifndef PYNE_IS_AMALGAMATED
> > +#include <json/json-forwards.h>
> > +#include <json/json.h>
> > +//#include "dagmc_bridge.h"  // figure this out later...
> > +#include "data.h"
> > +#include "enrichment_cascade.h"
> > +#include "enrichment.h"
> > +#include "enrichment_symbolic.h"
> > +#include "extra_types.h"
> > +#include "h5wrap.h"
> > +#include "material.h"
> > +#include "nucname.h"
> > +#include "rxname.h"
> > +#include "tally.h"
> > +#include "utils.h"
>
> This isn't how cyclus works, there is a UsePyne.cmake file for ease of
> use, and you can always use -I$(python -c 'import pyne;
> print(pyne.includes)'). I don't really want to refactor all of the
> includes to make this work :)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/pyne/pyne/pull/472/files#r13781844>.
>