Commit 54d84489 authored by Emil Velikov's avatar Emil Velikov Committed by Emil Velikov

swr: don't export swr_create_screen_internal

With earlier rework the user and provider of the symbol are within the
same binary. Thus there's no point in exporting the function.

Spotted while reviewing patch from Chuck, that nearly added another
unneeded PUBLIC function.

Cc: Chuck Atkins <chuck.atkins@kitware.com>
Cc: Tim Rowley <timothy.o.rowley@intel.com>
Fixes: f50aa214 "(swr: build driver proper separate from rasterizer")
Signed-off-by: default avatarEmil Velikov <emil.velikov@collabora.com>
Tested-by: Chuck Atkins's avatarChuck Atkins <chuck.atkins@kitware.com>
Reviewed-By: George Kyriazis <george.kyriazis@intel.com<mailto:george.kyriazis@intel.com>>
Tested-by: Chuck Atkins <chuck.atkins@kitware.com<mailto:chuck.atkins@kitware.com>>
parent e02f061b
......@@ -37,7 +37,7 @@ extern "C" {
struct pipe_screen *swr_create_screen(struct sw_winsys *winsys);
// arch-specific dll entry point
PUBLIC struct pipe_screen *swr_create_screen_internal(struct sw_winsys *winsys);
struct pipe_screen *swr_create_screen_internal(struct sw_winsys *winsys);
// cleanup for failed screen creation
void swr_destroy_screen_internal(struct swr_screen **screen);
......
......@@ -1143,7 +1143,6 @@ swr_validate_env_options(struct swr_screen *screen)
}
PUBLIC
struct pipe_screen *
swr_create_screen_internal(struct sw_winsys *winsys)
{
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment