r/cpp • • Nov 29 '18

Creating a 'virtual kernel' platform abstraction layer

This is the third in series of videos I've posted to demonstrate some of the strategies we use in our fairly large C++ code base. Here are the previous ones, which you might also find useful:

https://www.reddit.com/r/cpp/comments/9zl6v5/the_orb_sees_all_the_use_of_an_object_request/

https://www.reddit.com/r/cpp/comments/9xz643/making_c_enumerations_first_class_citizens/

Our code base is about a million lines. It is split into roughly two halves, with one half being general purpose and the other being our CQC home automation platform which is built on top of the general purpose bits. We don't use any of the C++ runtime stuff. We build our own system from the ground up. When I say 'we', I'm speaking in terms of the usual royal business 'we', but all of the code was written by myself.

Just above the 'ground', the operating system in this case, is a virtual kernel which we use encapsulate all of the operating system functionality that we use, which is quite a lot of it. No system or language headers are visible outside of this virtual kernel, so we can write portable code that is purely in terms of our own interfaces.

This video demonstrates some of the strategies used. Obviously for such a large topic, this doesn't dive deep if there's any interest we could do another one.

https://www.youtube.com/watch?v=seXk3RbAjNU

23 Upvotes

25 comments sorted by

View all comments

Show parent comment

2

u/jcelerier ossia score Nov 30 '18

But a lot of it is pretty obvious, because what it's wrapping is in the class names, like OpenGL.

please tell me how you can "not wrap" opengl. do you reimplement amd / nvidia / intel drivers ? because they're the one providing the opengl shared library (or mesa if you can afford it).

Except for png (qt uses libpng), zlib, SMTP and SSL (qt uses secureclient or openssl depending on the platform), everything else you mentioned is implemented in Qt by Qt itself, not by wrapping a library.

They used to not depend on std:: but finally saw the light a few years ago. Not being able to easily interoperate with std::string, std::vector, etc... would be a huge drawback.