<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jan 16, 2018, at 1:40 PM, Chuck Atkins <<a href="mailto:chuck.atkins@kitware.com" class="">chuck.atkins@kitware.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Perhaps one can split out the .cpp and build changes somehow.<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">Good idea. It's easy enough to split and without the autoconf changes the existing behavior will still be preserved so the other two builds can still work as they normally do, they just won't have the builtin-swr feature.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Given that the builtin-swr feature is intended for a specific customer, it is not a problem that it is only enabled for the autoconf build at this time. SCons and Meson can be enabled at a later time, if necessary.</div>
<div><br class="">
</div>
<div>Bruce<br class="">
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">- Chuck<br class="">
</div>
</div>
_______________________________________________<br class="">
mesa-dev mailing list<br class="">
<a href="mailto:mesa-dev@lists.freedesktop.org" class="">mesa-dev@lists.freedesktop.org</a><br class="">
https://lists.freedesktop.org/mailman/listinfo/mesa-dev<br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>