the libOSMesa isn't installed. It looks as it was removed around 6.3.1.1-r3. from the ChangeLog: 16 Aug 2005; Donnie Berkholz <spyderous@gentoo.org>; mesa-6.3.1.1-r3.ebuild: libOSMesa isn't building anymore, so stop symlinking and installing libtool archives. A native mesa-6.5.1 still (or again?) builds the osmesa library. Is there a reason for not including it in the ebuilds-install? Otherwise it would be nice to have it back, because its the only option to render openGL without graphics hardware.
It was removed because in the current build system, it's a complete hack to build and almost nobody actually uses it anymore. Do you?
Yes, I do.Its very useful for rendering openGL images on servers, where X11 isn't available. I compiled the latest native mesa (6.5.1), and libOSMesa was build by default. Maybe its not that complicated to add it again probably something has changed again and it is not much effort to add it. After all, the native mesa installs it by default.
No, nothing's changed. It's still a huge PITA. You've having an easy time because you're only building it once (not OSMesa, OSMesa16, OSMesa32) and you're not simultaneously building the DRI drivers.
maybe you could also nuke the osmesa.h header or I'm missing something?
Still missing in 7.0.2. I don't understand why osmesa.h is installed while the library is not even built. I just need it. I agree it's a hack to build it, but it is quite useful for off-screen rendering.
Created attachment 146083 [details] ebuild for media-libs/osmesa "It was removed because in the current build system, it's a complete hack to build and almost nobody actually uses it anymore. Do you?" hehe, calling the stuff the mesa guys use to .. well, "build" things a "build system" is kind of nice. the way to produce proper win32 based libs is hackerish at its best, why not use cmake or scons to provide platform neutral stuff, but anyway. yes, i use osmesa. and some others might as well. but since you are right in the fact that it should be only installed when really explicitly wanted: i attached the proposal for an osmesa-ebuild. i stripped down the mesa ebuild, i am not very much in the deeps of getting a perfect ebuild but it creates the osmesa just fine on my system. next step would be to a) make a new ticket for osmesa.ebuild and b) let people test it, especially the requestors. what do you think?
Upstream git now has an autoconf build, and I think that getting a simultaneous osmesa may have gotten a lot easier there. I faintly recall mailing-list posts to that effect. I'll look into getting osmesa into it, and then we can have a mesa-9999.ebuild in the x11 overlay that can do osmesa. How's that sound?
Huh... Shouldn't this bug be renamed to something else? mesa-6.5.1-r1 is somewhat old, and is not even in portage anymore.
Created attachment 189051 [details] uses the autotools configuration this is an adjustment of the media-libs/mesa ebuild to generate the osmesa result. I put the patches in ${FILESDIR} since I don't have access to the mirrors.
Created attachment 189077 [details] add libGLU.so* to the dynamic_libgl list otherwise conflicts with the libGLU.so* installed with media-libs/mesa
Any progress? desmume (svn version) need OSMesa for 3d engine
I think OSmesa should now be handled using the media-libs/mesa ebuild instead. Or maybe at the very least, the 2 ebuilds should be identical.
(In reply to comment #12) > I think OSmesa should now be handled using the media-libs/mesa ebuild instead. Yep. I think build-system changes might actually allow for the osmesa to be built at the same time without restarting from a clean build now.
Okey if anyone interested here in writting nice patch then do it this way: add osmesa useflag to the mesa-7.5 ebuild and make it work with it. I will then review the patch and apply it to main tree/overlay :] Cheers.
Actually, I would suggest a "minimal" USE flag instead. USE=minimal would only build one or more variants of osmesa USE=-minimal would build everything like today + osmesa It would probably require quite a few DEPEND changes... Like Tomáš said, patches welcome :)
Just so you know: Firefox 4, having WebGL included, uses and requires osmesa. It won’t even compile without it. At least the ebuild that’s in the mozilla overlay right now. So you better get osmesa back, or you’ll be in real trouble when Firefox 4 gets into main Portage. But of course, 1. If it’s such a mess, then how come nobody cleans it up? I can’t stand messes in my own code. It makes me feel sick. So I’m unable to relate. Although maybe just because nobody needed it. But then why did the mesa team not officially deprecate it? 2. Why does Firefox need osmesa in the first place? Is it for those cases where there is no GPU acceleration / OpenGL library available? I’m not sure there are any systems where Firefox would run on, that don’t at least have a mainboard chipset (e.g. a Intel one) supporting OpenGL.
(In reply to comment #16) > Just so you know: Firefox 4, having WebGL included, uses and requires osmesa. > It won’t even compile without it. At least the ebuild that’s in the mozilla > overlay right now. So you better get osmesa back, or you’ll be in real > trouble when Firefox 4 gets into main Portage. I hope you're not threatening us... And [1] disagrees with you, Firefox doesn't _need_ osmesa although it can _use_ it if asked to do so. [1] http://www.khronos.org/webgl/wiki/Implementations/Firefox
(In reply to comment #17) > I hope you're not threatening us... LOL. What? Why would I…? How…? …wait, what? I guess I was just watching too much of that one show. :) Replace the “you’ll” with a “we’ll” :) > And [1] disagrees with you, Firefox doesn't _need_ osmesa although it can _use_ it if asked to do so. Well, a crashing Firefox 4 ebuild would like to disagree with /that/. I can’t tell him he’s lying. He’s such a nice ebuild. :P
I added an osmesa USE flag to mesa-9999 in the X11 overlay. I don't have any use for osmesa, but I can confirm that it builds a working osmesa .so. This will get to the tree for Mesa 7.12/8.0.
Hey, nice work! Thank you man! You’d be surprised how much this helps! :) Sorry, I’m just so excited!
Very glad to hear it! :) Please let me know how it works and if there's something I can do to make it better.
Even sci-visualization/gfsview wants libOSMesa for being able to batch process data. So thanks for re-integrating - please keep it included.
I need it for gchemutils.
Fixed in 7.11.1, thanks for holding out with us.