-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
glewCreateContext fails on MacOSX on Travis #34
Comments
|
This is also misleading:
Should be separate lines. Also i'm curious to see if glewInit gives useful feedback if it's called before glewCreateContext. Maybe try this in a separate branch. |
Where did the idea to use glewCreateContext come from anyhow? As far as i can see it is only declared for glewinfo, which is a specific commandline tool. |
The line-by-line check for the glewCreateContext and glewInit are in test 01_context.t |
Alright, so neither of us knows why it's there. Checking to see if it's actually necessary. As for 02, the line is misleading as it only says glewInit in the skip message, it should at least mention both, i think? |
Err, results on this: If i don't run glewCreateContext (using master) it crashes as soon as it tries to use a GL function:
If i don't run glewInit, Microidium works, but runs at 3.6 fps? |
Ok, on further inspection, without create context glewinit errors out with "Missing GL version" if glCreateContext wasn't called. Do you think you can get some more details out of glCreateContext if it fails? Maybe by making some of the internally called functions available in Perl? ( https://github.com/nigels-com/glew/blob/master/auto/src/glewinfo_tail.c#L176-L598 ) |
I thought you were asking about why glewCreateContext specifically. In order for GLEW to load the needed extensions, there has to be an OpenGL context. glewCreateContext is good because it comes with the GLEW distribution. |
Alright, so if that's not strictly necessary, can you throw together a different context creation process we can bash against mac? |
You can use GLUT from OpenGL. Once the window+context is created, you can call glewInit. If you use the just fixed for the transparent glewInit calls, it should just work. (Famous last words...) |
Right, so you probably want to add -framework GLUT to MFpl so it can link and then special-case macosx in the test. Also, i'm asking you to write the test code because you know better what you're doing there. :x |
That is the problem. If the MacOSX code built and linked
correctly, then glewCreateContext should work as well. I
put out a call for someone with MacOSX to help debug. Here's
hoping....
…--Chris
|
Oh, I didn't realize this was in the Travis-CI thread. There is definitely something needed to allow glutCreateContext to work. I vaguely recall something about Xvfb or some such from a search... HTH. |
If i understand this correctly, xvfb won't run on osx anymore without considerable effort to get quartz installed and set up: http://stackoverflow.com/questions/25451133/xvfb-run-on-os-x/32786365#32786365 Please read and tell me what you get from it. |
Ok, turns out there is xvfb on those machines: travis-ci/travis-ci#2351 (comment) And i actually got somewhat close to making things happen, but now i'm quite stuck:
|
Asked in the Travis issues: travis-ci/travis-ci#7313 |
@zmughal made |
Right now the tests only skip and mention they failed. They don't try to inspect the return values to see why they failed. Tests should try and give more feedback about that.
The text was updated successfully, but these errors were encountered: