@ -242,18 +242,22 @@ user visible API changes, thus should be not considered part of the API version.
All new symbols should be guarded by the macro like the example given below:
All new symbols should be guarded by the macro like the example given below:
~~~~
#if REQUIRE_LIBWESTON_API_VERSION >= 0x0101
#if REQUIRE_LIBWESTON_API_VERSION >= 0x0101
bool
bool
weston_ham_sandwich(void);
weston_ham_sandwich(void);
#endif
#endif
~~~~
In order to use the said symbol, the one will have a similar code in their
In order to use the said symbol, the one will have a similar code in their
configure.ac:
configure.ac:
~~~~
PKG_CHECK_MODULES(LIBWESTON, [libweston-1 >= 1.1])
PKG_CHECK_MODULES(LIBWESTON, [libweston-1 >= 1.1])
AC_DEFINE(REQUIRE_LIBWESTON_API_VERSION, [0x0101])
AC_DEFINE(REQUIRE_LIBWESTON_API_VERSION, [0x0101])
~~~~
If the user is _not_ interested in forward compatibility, they can use 0xffff
If the user is _not_ interested in forward compatibility, they can use 0xffff
or similar high value. Yet doing so is not recommended.
or similar high value. Yet doing so is not recommended.