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: f50aa21456 "(swr: build driver proper separate from rasterizer")
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
Tested-by: Chuck 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>>
(cherry picked from commit 54d844897f)
This commit is contained in:
Emil Velikov 2018-01-22 17:52:49 +00:00 committed by Andres Gomez
parent 7af6be8864
commit 9dacf10ca8
2 changed files with 1 additions and 2 deletions

View file

@ -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);

View file

@ -1143,7 +1143,6 @@ swr_validate_env_options(struct swr_screen *screen)
}
PUBLIC
struct pipe_screen *
swr_create_screen_internal(struct sw_winsys *winsys)
{