Sounds likely to be this issue:
https://github.com/nigels-com/glew/issues/103
I can go ahead and release a GLEW 2.0.1 (bugfix release) if it's likely
to be promptly downstreamed.
** Bug watch added: github.com/nigels-com/glew/issues #103
https://github.com/nigels-com/glew/issues/103
--
You r
As the GLEW maintainer my suggestion would be to only continue with MX
packages for GLEW 1.13. There is no good reason to continue using GLEW
1.x aside from the MX multi-thread, multi-context support.
--
You received this bug notification because you are a member of DX
Packages, which is subscri
To clarify the intended behavior.
$ pkg-config --cflags glew
-I/usr/include/GL -I/usr/include/libdrm
ought to be:
$ pkg-config --cflags glew
-I/usr/include -I/usr/include/libdrm
In other words, headers are supposed to include GLEW via
As a workaround perhaps:
$ pkg-config --cflags glew
-I/us
Awesome. You rock!
- Nigel
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to glew in Ubuntu.
https://bugs.launchpad.net/bugs/1408347
Title:
bump version to 1.11 in ubuntu 15.04?
Status in glew package in Ubuntu:
Triaged
Bug description:
GLEW does not support OpenGLES. Therefore it seems doubtful that
openimageio-1.3.12 supports OpenGLES unless there is some kind of build
option for that.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to glew in Ubuntu.
https://bugs.launchpad.n
I'm the upstream maintainer of GLEW, my comment is that although a lot
of packages depend on GLEW, the vast majority of changes are fully
backwards compatible. 1.11.0 is itself nearly one year old and is two
versions behind. Fortunately for me I'm not having too much traffic
about obsolete bugs,
6 matches
Mail list logo