mirror of
https://github.com/brl/mutter.git
synced 2024-11-10 07:56:14 -05:00
77ec8774a0
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
89a2862b05 commit. The history is too long
to be reverted commit by commit without being extremely messy.
25 lines
596 B
PkgConfig
25 lines
596 B
PkgConfig
prefix=@prefix@
|
|
exec_prefix=@exec_prefix@
|
|
libdir=@libdir@
|
|
includedir=@includedir@
|
|
|
|
apiversion=@CLUTTER_API_VERSION@
|
|
requires=@CLUTTER_REQUIRES@
|
|
requires_private=@CLUTTER_REQUIRES_PRIVATE@
|
|
backends=@CLUTTER_BACKENDS@
|
|
|
|
# only kept for backward compatibility
|
|
soname_infix=@CLUTTER_SONAME_INFIX@
|
|
winsys=@CLUTTER_WINSYS@
|
|
backend=@CLUTTER_WINSYS@
|
|
cogl=deprecated
|
|
cogl_driver=deprecated
|
|
|
|
Name: Clutter
|
|
Description: Clutter Core Library
|
|
Version: @VERSION@
|
|
Libs: -L${libdir} -lclutter-${apiversion}
|
|
Cflags: -I${includedir}/clutter-${apiversion}
|
|
Requires: ${requires}
|
|
Requires.private: ${requires_private}
|