20 minutes ago, a light breeze said:

[...]/Horde3D-1.0.0/Horde3D/Source/Horde3DEngine/egRenderer.cpp:2301:78: error: cannot take the address of an rvalue of type 'float'
        _renderDevice->setShaderConst( _defColorShader.uni_worldMat, CONST_FLOAT44, &Matrix4f().x[0] );
                                                                                    ^~~~~~~~~~~~~~~~

The error itself doesn't look hard to fix, but it also looks like Horde3D is no longer being actively maintained - the last update on GitHub was "a year ago".

99% that this issue was fixed in 2017. And it may not be updated, but there isn't a reason to as it works fine, and it is still maintained, support still exists.

1 hour ago, midn said:

99% that this issue was fixed in 2017. And it may not be updated, but there isn't a reason to as it works fine, and it is still maintained, support still exists.

Yes, It looks like the problem has been fixed on Github.  I had been using the 1.0.0 stable release, which predates the fix.  So Horde3D is back in the running again.

Check out bs::framework and Diligent Engine https://github.com/DiligentGraphics/DiligentEngine