[Mesa-dev] Copying common u_format from gallium/auxiliary to broadcom/util

Andreas Bergmeier abergmeier at gmx.net
Sun Oct 6 19:31:03 UTC 2019


What I am fuzzy about is why in `src`, there is actually an include for
`gallium/include` and `gallium/auxiliary` (in `inc_common`). AFAIU this
forces most of mesa to sooner or later use Gallium code. It seems to stem
from the introduction of Intels Vulkan drivers.

On Sun, 6 Oct 2019 at 03:54, Rob Clark <robdclark at gmail.com> wrote:

> The plan is to extract some of this from gallium to share formats and
> related utils.. I need this too in order to share layout helper
> between gallium (freedreno) and vulkan (turnip) drivers
>
> BR,
> -R
>
> On Thu, Oct 3, 2019 at 11:30 PM <abergmeier at gmx.net> wrote:
> >
> >
> > Currently broadcom/compiler does not link on its own. It references
> undefined symbols to:
> > - `util_format_description`
> > - `util_format_is_unorm`
> > - `util_format_is_float`
> >
> > For gallium/v3d, these get provided by gallium/auxiliary. Seems to be an
> odd dependency to me.
> > I would now like to copy at least these 3 symbols to broadcom/util with
> a `v3d_` prefix. This way broadcom/compiler has no implicit dependency on
> gallium anymore.
> > Any opinions or better ideas?
> >
> > _______________________________________________
> > mesa-dev mailing list
> > mesa-dev at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20191006/13dc23ce/attachment.html>


More information about the mesa-dev mailing list