I'm trying to run a Vega Prime (Multigen-Paradigm) demo app under Chromium 1.2 (all nodes Linux). Have tried tilesort/render SPU's but encountering same problem with local-only pack/render SPU's.
Problem seems to be with the VP app itself. It dies upon being invoked by crappfaker with an "undefined symbol" complaint about 'glXDestroyWindow' (coming from code in VP's render library -- libsvgr.a or libsvgr.so).
The demo app works fine when executed direct from command line so obviously the problem is tied to the execution environment but I'd like to narrow it down further. Is this a case of A) the app is reliant upon a feature Chromium doesn't yet support or B) the app's renderer library is executing code bypassed under non-Chromium invocation which exposes an internal unanticipated circumstance?
Apologies if this question is overtly naive -- I'm not an OpenGL programmer but desperately need to get either Vega Prime or Performer working under Chromium.
Advice/suggestions much appreciated,
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Problem was missing function in faker GL lib, so I fixed it by adding one. Stubbed out glXDestroyWindow() in cr/opengl_stub/glx.c . No apparent harm done and the app now runs.
Well, sort of. Now I'm encountering what looks like Z-buffer anarchy. Stuff flickers around in Z-space and it looks like everything is being drawn at once. Can anyone tip me in the right direction on resolving this one?
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to run a Vega Prime (Multigen-Paradigm) demo app under Chromium 1.2 (all nodes Linux). Have tried tilesort/render SPU's but encountering same problem with local-only pack/render SPU's.
Problem seems to be with the VP app itself. It dies upon being invoked by crappfaker with an "undefined symbol" complaint about 'glXDestroyWindow' (coming from code in VP's render library -- libsvgr.a or libsvgr.so).
The demo app works fine when executed direct from command line so obviously the problem is tied to the execution environment but I'd like to narrow it down further. Is this a case of A) the app is reliant upon a feature Chromium doesn't yet support or B) the app's renderer library is executing code bypassed under non-Chromium invocation which exposes an internal unanticipated circumstance?
Apologies if this question is overtly naive -- I'm not an OpenGL programmer but desperately need to get either Vega Prime or Performer working under Chromium.
Advice/suggestions much appreciated,
Bill
Problem was missing function in faker GL lib, so I fixed it by adding one. Stubbed out glXDestroyWindow() in cr/opengl_stub/glx.c . No apparent harm done and the app now runs.
Well, sort of. Now I'm encountering what looks like Z-buffer anarchy. Stuff flickers around in Z-space and it looks like everything is being drawn at once. Can anyone tip me in the right direction on resolving this one?
Bill