deleting autobatch
Files moved for new package structure.
All modules now in ./charm/ and c source in ./native_extension/.
Directory structure is now
projectrooot/
    README
    setup.py
    configure.sh
    ....
    tests/              -- not moved for now to allow Christina to
                        -- finish changing the tests
    charm/              -- now the python package root
        __init__.py
        scheme/
        toolbox/
        core/           -- the spiritual sucessor to charm-src
            engine/
                __init__.py
                        -- other extension modules put here at compile
                        -- compile time such as math.pairing, utils etc

        zkp_compiler/   -- new name for compiler to avoid confusion with
                        -- real compiles like gcc or clang/llvm

    native_extensions/  -- new home for c or c++ source
        core/           --
            math/       -- holds all the math extensions
            crypto      -- was cryptobase
C extensions compile under new structure
Compiles and creates correct layout but c extensions not recognized
benchmark works but must be in top level
Manfiest no longer imports python files
Because of the changes to setup, we no longer need to manually pull python packages
Added package for charm.core.crypto.

This is neeeded to put an __int__.py in the folder that setup.py
puts the AES/DES/etc shared objects in. Otherwise they don't import
charm.crypto.base now charm.crypto.cryptobase

For some unkown reason the c extension module did not
react well to being renamed

Also added comments explaining the apparently empty packages
that get filled with the c extension modules
removed relative imports
Changed PyInit_ecc to PyInit_ellitpic_curve to complete name change

Python appear to require the init fuction to be named the same as the
module name. So both that and all strings containing the module name
were replaced.

As to why we changed the name at all, ecc is ellitpic curve cryptography
and this is trictly such elliptic curves
fixed pathing in symcrypto tests
Merge branch 'dev' into change_package_structure

Conflicts:
	charm/schemes/pkenc/pkenc_adapt_chk04.py
	charm/schemes/pksig/pksig_adapt_naor01.py
	charm/schemes/pksig/pksig_rsa_hw09.py
	charm/toolbox/__init__.py
	charm/zkp_compiler/__init__.py
fixed imports for tests.
adde charm prefix to imports for  schemes and toolbox. Corrected import for interfac_ABEnc_test
instead of trying to get IBE_BB04 from schemes.ibenc_bb03
fixed imports for hash_module
fixing test errors
Moving toolbox tests into charm/test

Because we are have decided not to package the schemes with the
installed code, we cannot have the schemes and core tests
intermingled. However, we still want to ship the core tests with
the installed becauase we want to enable self test and such.
Schemes no longer part of the installed package

We opt to only package and install the framework portions of charm
instead of the schemes. Installings the schemes makes it  needlessly
difficutl to work withthem, test them, etc. If we did install them a
long with everything else, there would be an odd distinction between
the schemes that were last installed and anything a cryptographer has
written recently or worse modified.
Scheme tests moved to schemes/test/ and rm'd tests/

Schemes should be with their own tests. This follows form the fact
that we want to ship the core tests with the charm framework.
As such, we to have them in the charm package. This leaves
tests for schemes orphined. Moreover, we should ship the scheme tests
when we ship schemes (whether it is as part of a package or as a
downloadable package of examples). Thus they are now in schemes/test
Fixed imports for scheme tests

Because we are not installing the schemes, the scheme tests
can't import form charm.scheme. Rather they will pull from
schemes directory itself
Renaming charm to charm-pkg and fixing setup.py

Because we split schemes of, we epect people to run the python
intepreter from the project directory. As, because of python search
order for imports, the intepreter would actually try to import
project/charm instead of installed version. This would break because
the project version does not have the binaries built for it.