Separate DLLs

This program should basically be a open-source library for identifying MtG-cards. For it to be that, the borders between the application and the library needs to be clearer, perhaps by using separate DLL-files.

It fells like OpenCV has a good structure. How are they doing it?

Suggestion for splitting up the code:
* rmc_core.dll - A file containing the classes, containers enums and other parts used by pretty much everything and everyone.
* rmc_library.dll - All "useful" methods of a abstract/general nature.
* rmc_engine.dll - The applied engine that does the job of identifying the cards.

Start by mapping the existing classes, containers, enums, general-purpose methods, and card-identification engine into the proposed rmc_core.dll, rmc_library.dll, and rmc_engine.dll boundaries. Compare OpenCV's library structure as suggested, then define and document the dependencies and build outputs; done means the application and reusable library have clear, separate DLL interfaces.

Written by the indexing model from the issue text.