Run the C++ generated component through the GL backend

... which in turn forward to the corelib, but with the GL renderer attached.
This commit is contained in:
Simon Hausmann 2020-05-11 15:05:33 +02:00
parent 5b4966f652
commit 83eb00b080
6 changed files with 87 additions and 2 deletions

View file

@ -4,6 +4,7 @@ using str = char; // FIXME: this is just required because of something wrong
namespace sixtyfps::internal {
struct ComponentType;
} // namespace sixtyfps::internal
#include "sixtyfps_gl_internal.h"
#include "sixtyfps_internal.h"
namespace sixtyfps {
@ -16,7 +17,7 @@ template <typename Component> void run(Component *c) {
// FIXME! some static assert that the component is indeed a generated
// component matching the vtable. In fact, i think the VTable should be a
// static member of the Component
internal::sixtyfps_runtime_run_component(
internal::sixtyfps_runtime_run_component_with_gl_renderer(
&Component::component_type,
reinterpret_cast<internal::ComponentImpl *>(c));
}