Clean up the x-mas tree

unroll AES round by hand to help the compiler to optimize the command queue

Allow to change the indexing used to address the hash scratchpad memory.

- add option `strided_index` for each gpu

Fix for AMD GPU detection on MacOS X
On MacOS X the platform is reported as Apple, and the vendor is reported as AMD.

Fixing the compile error on MacOS X

The max work size shown to the user was the hardware maximum but not take in account thet some kernel spwning 8 times more threads per work group than configured by the user.

- handle opencl errors to avoid unexpected behaviors
- remove code duplicatio nwithin the some method

- enforce that only host side OpenCl 1.2 functions are used if the miner is compiled with `XMR-STAK_COMPILE=generic`
- update documentation
- add CMake option `XMR-STAK_COMPILE` to windows

Remove whitespace lines

- removed all space indention in `*.hpp` and `*.cpp` files

- rename all `xmr` to `monero`
- be insensitive while check for set currency
- add function to compate two strings insensitive

- add compile parameter to support aeon and xmr
- update auto suggestion to handle aeon

- remove 32bit target value
- use always 64bit target for amd backend

fix bug announced in #52

If the miner is compiled in debug mode the assert condition results in a compile time error.

Early returns within a kernel can have unexpected behavior, this strongly depends on the opencl
runtime compiler. To avoid errors all early returns are removed.
There is no negative effect(e.g.performance) if the threads stay alive up to the end of the kernel.

One source for the early return is: http://al-key-opencl.blogspot.de/2014/09/be-careful-not-to-mix-early-return-and.html

This pull request also fix a race condition where all fill the shared memory.
Also a bug introduced with #16 is fixed, because of the early return not was possible that
the last block works with an wrong initilized shared memory (result should be a wrong hash if the result target size is valid).

Is is possible that the number of results are greater than the result output array,
in this case invalid memory can be access within the device and on the host side.

check that the number of global threads is a multiple of the workgroup size

The number of threads within a kernel must be a multiple of the worksize.
If not it can crash on some systems.

- string literal can only be 16kbyte

- move source code to `src`
- categorize files and move to group folder
- change upper case class files to lower case
- change C++ header to `*.hpp`