public inbox for cygwin-xfree-announce@sourceware.org help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com> To: cygwin-xfree-announce@cygwin.com Subject: Updated: mesa-10.2.4-1, mesa-demos-8.2.0-1 Date: Wed, 23 Jul 2014 16:09:00 -0000 [thread overview] Message-ID: <1406131700.1920.77.camel@YAAKOV04> (raw) The following packages have been updated in the Cygwin distribution: * dri-drivers-10.2.4-1 * libEGL1-10.2.4-1 * libEGL-devel-10.2.4-1 * libGL1-10.2.4-1 * libGL-devel-10.2.4-1 * libGLESv1_CM1-10.2.4-1 * libGLESv1_CM-devel-10.2.4-1 * libGLESv2_2-10.2.4-1 * libGLESv2-devel-10.2.4-1 * libglapi0-10.2.4-1 * libOpenVG1-10.2.4-1 * libOpenVG-devel-10.2.4-1 * libOSMesa8-10.2.4-1 * libOSMesa-devel-10.2.4-1 * mesa-demos-8.2.0-1 Mesa is an open-source implementation of the OpenGL specification, a system for rendering interactive 3D graphics. This is an update to the latest upstream release, with a number of new features. Until now, OpenGL has been handled solely with indirect rendering, meaning that libGL passes calls over the GLX protocol to the server, which then handles the rendering with hardware acceleration in multiwindow/-wgl mode, or software rendering (swrast) in desktop/-nowgl mode. The major drawback of this method is that the GLX protocol only supports OpenGL 1.4, anything which requires 2.0 or newer (such as GLSL) cannot work. This release adds *direct* rendering support, where libGL handles the rendering itself via DRI drivers. This provides complete OpenGL 3.0 and GLSL 1.30 support (along with numerous newer extensions), allowing much more OpenGL software to render correctly. The only drawback at the moment is that only the llvmpipe DRI driver is current available, meaning that rendering is done in software and passed to the server over the X11 protocol, and therefore more CPU intensive. As this is a new feature, the previous behaviour of indirect rendering is still the default. In order to enable direct rendering (and hence OpenGL 3.0), the following steps are required: 1) If using -multiwindow, the -nowgl flag must be added. 2) Add the following to your ~/.startxwinrc, ~/.xinitrc, or ~/.bashrc, or run this manually in the shell from which you will launch OpenGL applications: unset LIBGL_ALWAYS_INDIRECT (tcsh users need to use unsetenv instead of unset, of course.) Other feature changes: * llvmpipe uses LLVM 3.4 and is now available on x86_64. * GLES support has been added. * mesa-demos includes EGL/GLES utilities. Many thanks to Jon TURNEY for his continued work on OpenGL support which led to these new features. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
reply other threads:[~2014-07-23 16:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1406131700.1920.77.camel@YAAKOV04 \ --to=yselkowitz@cygwin.com \ --cc=cygwin-xfree-announce@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).