Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rotaerk

Pages: [1]
1
Window / SFML clashing with GLee
« on: November 22, 2007, 03:32:13 am »
Sounds good to me :)

2
Window / SFML clashing with GLee
« on: November 21, 2007, 07:39:15 pm »
Okay, I could do that.  However, if it is safe to simply remove that include from the header, then it is an unnecessary dependency.  Furthermore it causes issues with other libraries.  So should it really be there in the released version?  I would like to not have to make modifications to a third-party library every time I set it up.

3
Feature requests / Visual Studio 2008
« on: November 21, 2007, 05:13:29 am »
Because VS 2008 has now been officially released, it would be nice if there were a corresponding solution and build in the SDK, either in addition to or as a replacement to those for 2005.  Of course, this isn't critical since one can convert the solution and project, which is what I'll be doing for now.

4
Window / SFML clashing with GLee
« on: November 21, 2007, 04:48:43 am »
The GLee library's main header, <gl/glee.h>, may not be included after <gl/gl.h>.  Also, the former includes the latter.

Now in version 1.1 of SFML, the <sfml/window.hpp> header includes <sfml/window/openglcaps.hpp>, which in turn includes <sfml/window/glew/glew.h>.  This header also cannot be included after <gl/gl.h>, and includes <gl/gl.h> internally.

This is an issue because no matter the order in which you include <gl/glee.h> and <sfml/window.hpp>, a compiler error occurs.

Considering GLee is a library meant to serve as a sort of wrapper for GL, it makes sense that it would have such a requirement.  However, SFML windows shouldn't.  I hope this issue is resolved.  For now I will continue to use SFML 1.0 until it is.  If it does not get fixed I will have to find another library.

Pages: [1]
anything