summaryrefslogtreecommitdiff
path: root/src/version.h.in
Commit message (Collapse)AuthorAgeFilesLines
* src: Update boilerplate from MIT X11 license to MIT Expat licenseBryce Harrington2015-06-151-16/+19
|
* Spellcheck fixesBryce Harrington2015-03-191-3/+3
| | | | | | | | | | | | | ./ivi-shell/README:19: protocal ==> protocol ./src/compositor.h:596: seperate ==> separate ./src/version.h.in:33: actualy ==> actually ./src/cms-helper.h:44: embeded ==> embedded ./protocol/fullscreen-shell.xml:65: seperate ==> separate ./protocol/xdg-shell.xml:150: auxilliary ==> auxiliary ./clients/window.c:1035: preferrably ==> preferably Signed-off-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
* Document WESTON_VERSION_AT_LEAST() macro behaviorKristian Høgsberg2014-01-271-1/+11
| | | | | | | | | | | | | | | | | | | | Adding this comment to explain the behavior: This macro may not do what you expect. Weston doesn't guarantee any stable API between 1.X and 1.Y, and thus this macro will return FALSE on any WESTON_VERSION_AT_LEAST(1,X,0) if the actualy version is 1.Y.0 and X !=Y). In particular, it fail if X < Y, that is, 1.3.0 is considered to not be "at least" 1.4.0. If you want to test for the version number being 1.3.0 or above or maybe in a range (eg 1.2.0 to 1.4.0), just use the WESTON_VERSION_* defines above directly. Version number testing is the one thing we can't break in the weston API, so we'll have to settle for documenting the behavior and recommending using the version number macros directly. https://bugs.freedesktop.org/show_bug.cgi?id=74023
* version.h: Add version check macroPier Luigi Fiorini2013-09-231-0/+6
| | | | Make it easier to check for a Weston version.
* Install header files and pkg-config file for external modulesKristian Høgsberg2013-02-181-0/+31
This patch installs the three header files that define the compositor plugin interface as well as a pkg-config file. This allows building weston plugins outside the weston tree. We currently don't make any guarantees about the plugin API/ABI except that within a stable branch we won't break it.