Bug 29613 - OSMesa and GL cannot be linked together
Summary: OSMesa and GL cannot be linked together
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/OSMesa (show other bugs)
Version: git
Hardware: All All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-17 07:51 UTC by Kevin Hobbs
Modified: 2019-09-18 20:12 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Kevin Hobbs 2010-08-17 07:51:29 UTC 
Before commit cbf30fce322506bd43692617de9d201533f41532 an application was required to link GL (xlib driver) in order to link OSMesa. The application could then do on-screen or off-screen software rendering.

After cbf30fce322506bd43692617de9d201533f41532 an application can only link GL or OSMesa but not both. Applications that assume the old behaviour can not be built.

The change was made because -fvisibility=hidden hid the internal mesa functions in GL from OSMesa.
Comment 1 Matt Turner 2012-08-22 17:59:16 UTC 
If you merge this branch into master, does it fix the problem?

http://cgit.freedesktop.org/~mattst88/mesa/log/?h=configure-cleanups
Comment 2 Matt Turner 2012-08-22 18:08:36 UTC 
Actually, I've just pushed it to master, so try that.
Comment 3 Kevin Hobbs 2012-08-22 19:43:59 UTC 
(In reply to comment #2)
> Actually, I've just pushed it to master, so try that.

I'm experimenting under the assumption that your patch will allow me to build libGL (dri) and libOSMesa that can be linked from the same app. 

I see that I cannot link the same app to libGL (xlib) and libOSMesa.
Comment 4 GitLab Migration User 2019-09-18 20:12:26 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/875.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.