Glut dependency because of TBSystem::RescheduleTimer about turbobadger

[fruxo]

The comment is mentioning glut but the demo actually use glfw now (the implementation is in port_glfw.cpp). You don't need it if you're doing a game (with a game loop), but if you're doing an event driven application (that should be idle unless there are stuff to do) you'll need it.

The method should move out from TBSystem to avoid this confusion, but for now, just defining it somewhere is a quick fix.

[Cleroth]

So I can't use the TB events at all, or just avoid PostMessageOnTime?

[fruxo]

You can still use TB events, including PostMessageOnTime. The messages will be handled when you call ProcessMessages which you'll do often in the game loop. If there's nothing to do, ProcessMessages will not do anything. See integration.txt if you haven't already.

[Cleroth]

Oh, I understand now. Thanks.

[tesch1]

@Cleroth maybe you could close this issue now?

[Cleroth]

@tesch1 The problem isn't solved though. If you're building turbobadger on Windows you'll get the unresolved symbol without knowing how to fix it.