Hello forum : )
I was wondering if it is common practice to wrap around classes from external libraries in order to interchange such library by another.
And how modern C++ tackle to provide multiple builds for multiple OS.
What I do:
I have the same files used by multiple projects, one project per OS.
All I do is linking different OS versions of my one Graphics library. Is this advised? Or are macros more common?
Let us take a Graphics library as an example, containing a windows-class and a sprite-class.
Now, our code owns a Graphics component having the sprite-class as a member.
I can simply change the library binaries
Would it be better to create a Sprite-wrapper instead? So, my Graphics component can call methods to obtain coordinates without really knowing what kind of object it is working with.
As far as I know, decoupling is generally advised, just curious to know when it is too much.
Thanks for reading : )!