Add some minimal documentation about static linking
authorPeter Hutterer <peter.hutterer@who-t.net>
Tue, 19 Aug 2014 00:31:12 +0000 (10:31 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Mon, 25 Aug 2014 00:12:37 +0000 (10:12 +1000)
I can't recommend it, but I can't stop people from doing it, so at least
document the ground rules.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
libevdev/libevdev.h

index 321f9803e1e202dcfea75df89d98e59ee557a8cf..afc1d13624df75f1c1f2a235ee9c3e6c23152efc 100644 (file)
@@ -540,6 +540,20 @@ extern "C" {
  * @include linux/input.h
  */
 
+/**
+ * @page static_linking Statically linking libevdev
+ *
+ * Statically linking libevdev.a is not recommended. Symbol visibility is
+ * difficult to control in a static library, so extra care must be taken to
+ * only use symbols that are explicitly exported. libevdev's API stability
+ * guarantee only applies to those symbols.
+ *
+ * If you do link libevdev statically, note that in addition to the exported
+ * symbols, libevdev reserves the <b>_libevdev_*</b> namespace. Do not use
+ * or create symbols with that prefix, they are subject to change at any
+ * time.
+ */
+
 /**
  * @page testing libevdev-internal test suite
  *