<div dir="ltr"><div><div>Hi Rick,<br><br></div>This comes up from time to time.  We need the same thing deploying ParaView render servers on CPU-only compute clusters without X, but I've found it difficult to really determine the right set of configuration parameters to use.  With the current Mesa release, 17.x, we've settled on the following ./configure parameters to produce a bare-bones-ish libOSMesa only containing the llvmpipe software driver.  Note that some of these parameters are already set by default but I find it helpful to be explicit since many of them are "auto-detect":<br><span style="font-family:monospace,monospace"><br> /configure                                      \<br>--enable-opengl --disable-gles1 --disable-gles2  \<br>--disable-va --disable-xvmc --disable-vdpau      \<br>--disable-shared-glapi --disable-texture-float   \<br>--enable-llvm --enable-llvm-shared-libs          \<br>--with-gallium-drivers=swrast --with-platforms=  \<br>--disable-dri --disable-dri3 --with-dri-drivers= \<br>--disable-egl --disable-gbm --disable-glx        \<br>--disable-osmesa --enable-gallium-osmesa</span><br><br></div>Some that may be of specific interest to you:<br><ul><li><span style="font-family:monospace,monospace">--disable-texture-float</span></li><ul><li><span style="font-family:arial,helvetica,sans-serif">This is disabled by default but it's an important one to be explicit with if your developing commercial software to ship.  The OpenGL floating point textures implementation in Mesa is currently patent encumbered so enabling it is at your own risk.  FWIW though, the patent should expire sometime next year in the summer I believe when it should no longer be an issue. </span><span style="font-family:monospace,monospace"><br></span></li></ul><li><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace">--enable-llvm-shared-libs</span></span></li><ul><li><span style="font-family:arial,helvetica,sans-serif">If you change this to --disable-llvm-shared-libs then libLLVM will be linked statically into your resulting libOSMesa, which will make it pretty huge but will also drop the need for an extra dependency to be shipped.  So, it's a trade off.</span><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace"><br></span></span></li></ul><li><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace">--disable-osmesa --enable-gallium-osmesa</span></span></span></li><ul><li><span style="font-family:arial,helvetica,sans-serif">No need to change these but it can be confusing.  The first option disables the "legacy" DRI-based OSMesa implementation while the second enables the newer implementation based on the gallium driver architecture and also supports newer OpenGL standards while the legacy one does not.</span><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace"><br></span></span></span></li></ul></ul><div><br></div><div><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">----------<br>Chuck Atkins<br>Staff R&D Engineer, Scientific Computing<br>Kitware, Inc.<br>(518) 881-1183<br></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Dec 5, 2017 at 11:57 AM, Rick Irons <span dir="ltr"><<a href="mailto:Rick.Irons@mathworks.com" target="_blank">Rick.Irons@mathworks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Brian,<br>
<br>
Thanks for the info.<br>
<br>
Regards,<br>
Rick<br>
<span class="im HOEnZb"><br>
-----Original Message-----<br>
From: Brian Paul [mailto:<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>]<br>
Sent: Tuesday, December 5, 2017 11:55 AM<br>
To: Rick Irons <<a href="mailto:Rick.Irons@mathworks.com">Rick.Irons@mathworks.com</a>>; <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.<wbr>org</a><br>
</span><div class="HOEnZb"><div class="h5">Subject: Re: [Mesa-users] Software rendering configuration on LINUX<br>
<br>
Hi Rick,<br>
<br>
 From the sounds of it, OSMesa is indeed what you want.  It works with llvmpipe so it can be reasonably fast.<br>
<br>
-Brian<br>
<br>
<br>
On 12/05/2017 07:32 AM, Rick Irons wrote:<br>
> Thanks Jeffrey for the info.<br>
><br>
> We are looking to render without a windowing system.  It seems that<br>
> using OSMesa is the only Mesa based option for such off screen<br>
> rendering.  Is this correct?<br>
><br>
> Thanks,<br>
><br>
> Rick<br>
><br>
> *From:* Jeffrey Collins [mailto:<a href="mailto:tildejac@outlook.com">tildejac@outlook.com</a>]<br>
> *Sent:* Monday, December 4, 2017 7:51 PM<br>
> *To:* Rick Irons <<a href="mailto:Rick.Irons@mathworks.com">Rick.Irons@mathworks.com</a>>;<br>
> <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.<wbr>org</a><br>
> *Subject:* Re: Software rendering configuration on LINUX<br>
><br>
> Isn't this what the Wayland interface is meant for?<br>
> <a href="https://en.wikipedia.org/wiki/Wayland_(display_server_protocol" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/<wbr>Wayland_(display_server_<wbr>protocol</a><br>
> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org" rel="noreferrer" target="_blank">https://urldefense.<wbr>proofpoint.com/v2/url?u=https-<wbr>3A__en.wikipedia.org</a><br>
> _wiki_Wayland-5F-28display-<wbr>5Fserver-5Fprotocol&d=DwMFAg&<wbr>c=uilaK90D4TOV<br>
> oH58JNXRgQ&r=Ie7_<wbr>encNUsqxbSRbqbNgofw0ITcfE8JKfa<wbr>UjIQhncGA&m=CST2HkydTH1<br>
> XFl9qklsxi2sqHB7GggKHET8Fpl5vV<wbr>U4&s=1pj_<wbr>k6n3PJx12IhM9jQcKcZas3MScgGS8S<wbr>s<br>
> 6ojmUH80&e=>)<br>
><br>
> ------------------------------<wbr>------------------------------<wbr>----------<br>
> --<br>
><br>
> *From:*mesa-users <<a href="mailto:mesa-users-bounces@lists.freedesktop.org">mesa-users-bounces@lists.<wbr>freedesktop.org</a><br>
> <mailto:<a href="mailto:mesa-users-bounces@lists.freedesktop.org">mesa-users-bounces@<wbr>lists.freedesktop.org</a>>> on behalf of Rick<br>
> Irons <<a href="mailto:Rick.Irons@mathworks.com">Rick.Irons@mathworks.com</a> <mailto:<a href="mailto:Rick.Irons@mathworks.com">Rick.Irons@mathworks.<wbr>com</a>>><br>
> *Sent:* Monday, December 4, 2017 2:23 PM<br>
> *To:* <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.<wbr>org</a><br>
> <mailto:<a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.<wbr>freedesktop.org</a>><br>
> *Subject:* [Mesa-users] Software rendering configuration on LINUX<br>
><br>
> Hi,<br>
><br>
> Is a Mesa software rendering configuration that does not rely on X11<br>
> possible for LINUX?  I would like to use a version of Mesa for OpenGL<br>
> rendering on LINUX that does not rely on either graphics hardware and<br>
> or X11.  Is using OSMesa my only option?<br>
><br>
> Thanks,<br>
><br>
> Rick<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> mesa-users mailing list<br>
> <a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.<wbr>org</a><br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__lists.<wbr>freedesktop</a><br>
> .org_mailman_listinfo_mesa-<wbr>2Dusers&d=DwIGaQ&c=<wbr>uilaK90D4TOVoH58JNXRgQ&r<br>
> =Ie7_<wbr>encNUsqxbSRbqbNgofw0ITcfE8JKfa<wbr>UjIQhncGA&m=<wbr>CST2HkydTH1XFl9qklsxi2s<br>
> qHB7GggKHET8Fpl5vVU4&s=<wbr>FP73VXIZ4X0mqLPR7dcV3niNT9m7Tr<wbr>qFRRYckPyxQDg&e=<br>
><br>
<br>
______________________________<wbr>_________________<br>
mesa-users mailing list<br>
<a href="mailto:mesa-users@lists.freedesktop.org">mesa-users@lists.freedesktop.<wbr>org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-users" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/mesa-users</a><br>
</div></div></blockquote></div><br></div></div>