|
Notes |
|
|
(0018817)
|
|
François Bertel
|
|
2009-12-11 11:47
|
|
In bug 0008554, there is no use of OSMesa so this is not the reason of bug 0008554.
Nevertheless, the patch addresses a valuable issue. Can you describe your context (in which case you are using OSMesa, hardware (Mac,PC), OS, ... )
Looking at this blog http://www.gnashdev.org/?q=node/46 [^] I wonder if it even makes sense to link both with libOSMesa and libGL. It sounds there are just conflicting. |
|
|
|
(0018818)
|
|
Pietro Cerutti
|
|
2009-12-11 11:58
|
|
Yes you are right, I had misunderstood the problem in 0008554. It just happened to segfault at the same location.
I'm on Ubuntu 9.10 on an iMac and I use OSMesa to render off screen in a console-based program. I will investigate whether removing GL at all when linking against OSMesa works. I'll get back to you monday morning (CET).
Thanks. |
|
|
|
(0018841)
|
|
Pietro Cerutti
|
|
2009-12-14 03:43
|
|
ok, the problem is when you need both an off-screen window and an in-screen window (say, XOpenGL). In that case, you need both OSMesa and GL. For this reason, we cannot mutually exclude the two libraries.
I guess the solution would be indeed to swap the positions (OSMesa first, then GL). This way, the common functions are resolved in OSMesa, and the remaining ones in GL. |
|
|
|
(0037127)
|
|
Kitware Robot
|
|
2016-08-12 09:55
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
|