error: Do not define _cairo_error twice

cairo-perf-trace uses cairo-hash.c, which calls _cairo_error.

Instead of redefining it in cairo-perf-trace.c it can be abstracted in
a separate source which is directly included in the build of
cairo-perf-trace.

This avoids visibility issues when compiling cairo-perf-trace with a
statically linked cairo library on architectures which do not support
hidden visibility (example: win32).

1 files changed, 0 insertions, 26 deletions

diff --git a/src/cairo.c b/src/cairo.c
index c19a1e9ff..dde9dacda 100644
--- a/src/cairo.c
+++ b/src/cairo.c
@@ -154,32 +154,6 @@ static const cairo_t _cairo_nil__null_pointer = {
 #include <assert.h>
 
 /**
- * _cairo_error:
- * @status: a status value indicating an error, (eg. not
- * %CAIRO_STATUS_SUCCESS)
- *
- * Checks that status is an error status, but does nothing else.
- *
- * All assignments of an error status to any user-visible object
- * within the cairo application should result in a call to
- * _cairo_error().
- *
- * The purpose of this function is to allow the user to set a
- * breakpoint in _cairo_error() to generate a stack trace for when the
- * user causes cairo to detect an error.
- *
- * Return value: the error status.
- **/
-cairo_status_t
-_cairo_error (cairo_status_t status)
-{
-    CAIRO_ENSURE_UNIQUE;
-    assert (_cairo_status_is_error (status));
-
-    return status;
-}
-
-/**
  * _cairo_set_error:
  * @cr: a cairo context
  * @status: a status value indicating an error