isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-10-06 14:18:15 -04:00
Code Issues Packages Projects Releases Wiki Activity
f820bb3506
mutter/clutter/clutter/mutter-clutter.pc.in

25 lines
685 B
PkgConfig
Raw Normal View History

Merge gobject-branch into trunk
2006-05-29 04:59:36 -04:00
prefix=@prefix@
Bug 1491 - Fix hardcoded lib path in .pc files We should instead use @libdir@ from configure to be correct on multilib systems.
2009-03-06 00:19:12 -05:00
exec_prefix=@exec_prefix@
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
apiversion=@LIBMUTTER_API_VERSION@
autotools: Make install directories paths more consistent Install include files in $prefix/include/mutter-$apiversion/[clutter,cogl,...,meta]/, and datafiles in /usr/share/mutter-$apiversion/.... We still would conflict e.g. given that our gettext name is "mutter", and how keybindings are installed, but it's a step in the right direction.
2018-07-17 06:39:57 -04:00
libdir=@libdir@/mutter-${apiversion}
includedir=@includedir@/mutter-${apiversion}
build: Fix include and lib paths in autotools .pc files Some hadn't been updated after lib/mutter/ changed to lib/mutter-N/. Fixes: https://gitlab.gnome.org/GNOME/mutter/issues/382
2018-11-07 08:29:30 -05:00
requires=@CLUTTER_REQUIRES@ mutter-cogl-${apiversion}
build: Add infrastructure for inserting Requires.private into pkg-config files
2012-01-11 07:23:46 -05:00
requires_private=@CLUTTER_REQUIRES_PRIVATE@
Implement multi-backend support The Clutter backend split is opaque enough that should allow us to just build all possible backends inside the same shared object, and select the wanted backend at initialization time. This requires some work in the build system, as well as the initialization code, to remove duplicate functions that might cause conflicts at build and link time. We also need to defer all the checks of the internal state of the platform-specific API to run-time type checks.
2011-09-21 13:05:03 -04:00
backends=@CLUTTER_BACKENDS@
Do not hardcode paths in pkgconfig file The pkgconfig file correctly sets $prefix to @prefix@, but the other paths should be relative to $prefix.
2010-06-22 03:29:02 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
# only kept for backward compatibility
soname_infix=@CLUTTER_SONAME_INFIX@
winsys=@CLUTTER_WINSYS@
backend=@CLUTTER_WINSYS@
cogl=deprecated
cogl_driver=deprecated
clutter: make library private to mutter
2016-04-08 14:53:58 -04:00
Name: Mutter Clutter
Description: Mutter's Clutter Private Library
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
Version: @MUTTER_VERSION@
clutter: make library private to mutter
2016-04-08 14:53:58 -04:00
Libs: -L${libdir} -lmutter-clutter-${apiversion}
autotools: Make install directories paths more consistent Install include files in $prefix/include/mutter-$apiversion/[clutter,cogl,...,meta]/, and datafiles in /usr/share/mutter-$apiversion/.... We still would conflict e.g. given that our gettext name is "mutter", and how keybindings are installed, but it's a step in the right direction.
2018-07-17 06:39:57 -04:00
Cflags: -I${includedir}/clutter
2008-07-16 Emmanuele Bassi <ebassi@openedhand.com> * clutter.pc.in: Add a variable containing the COGL backend inside the pkg-config file, for configure-time checks.
2008-07-16 12:53:41 -04:00
Requires: ${requires}
build: Add infrastructure for inserting Requires.private into pkg-config files
2012-01-11 07:23:46 -05:00
Requires.private: ${requires_private}
Reference in New Issue Copy Permalink