Decouple pipeline and CUDA abstraction/helper layer

[j-stephan]

GLADOS currently serves two independent purposes:

1. Providing the pipeline pattern
2. Providing a CUDA abstraction layer / C++11 style memory handling / pool allocators

There are no dependencies or interlinks between both components, it is entirely by accident that they are both part of GLADOS. From a software development point of view this bundling doesn't make a lot of sense, especially when considering the different development speeds. The pipeline pattern is (more or less) feature complete and its interface should be -- for the foreseeable future -- considered stable. The CUDA component on the other hand will likely see a lot of changes in the future as it includes only a subset of all current CUDA features and CUDA itself is evolving as well.

I'm currently considering the removal of the CUDA parts from GLADOS and putting them into a separate project. Thoughts?

[tobiashuste]

Will the decoupled part be able to be used elsewhere as a stand-alone library?

[j-stephan]

Yes, of course! I would create a new repository for that.