libdir option applies to everything except backends
Bug #959282 reported by
micove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Compiz |
Fix Released
|
High
|
Stephen M. Webb | ||
| Compiz Configuration Library |
Won't Fix
|
Undecided
|
Unassigned | ||
| compiz (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Is there a reason for using the -Dlibdir option for everything except the backends?
It seems that if I want to install everything into a -Dlibdir that is a multiarch path the backends will be hardcoded to /usr/lib/.
It will also make rpm distros happy as mentioned here:
http://
Something like:
- INSTALL_RPATH "${CMAKE_
+ INSTALL_RPATH "${libdir}"
- DESTINATION ${COMPIZ_
+ DESTINATION ${COMPIZ_
Works fine too.
Related branches
lp://staging/~bregma/compiz/lp-1395105
- Christopher Townsend (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 1086 lines (+488/-277)20 files modifiedCMakeLists.txt (+7/-6)
compizconfig/CMakeLists.txt (+6/-6)
compizconfig/compizconfig-python/CMakeLists.txt (+1/-1)
compizconfig/gsettings/gsettings_backend_shared/CMakeLists.txt (+1/-1)
debian/compiz-core.install (+6/-6)
debian/compiz-dev.install (+10/-10)
debian/compiz-gnome.install (+8/-8)
debian/compiz-plugins-default.install (+49/-25)
debian/compiz-plugins.install (+106/-57)
debian/compiz-plugins.install.armel (+92/-52)
debian/compiz-plugins.install.armhf (+92/-52)
debian/control (+24/-1)
debian/libcompizconfig0-dev.install (+5/-5)
debian/libcompizconfig0.install (+5/-5)
debian/libdecoration0-dev.install (+3/-3)
debian/libdecoration0.install (+1/-1)
debian/python-compizconfig.install (+3/-3)
debian/rules (+7/-0)
src/plugin.cpp (+42/-35)
src/plugin/tests/test-plugin.cpp (+20/-0)
| Changed in compiz: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in compiz: | |
| milestone: | none → 0.9.12.1 |
| assignee: | nobody → Stephen M. Webb (bregma) |
| Changed in compiz: | |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in compiz (Ubuntu): | |
| status: | New → Fix Released |
| Changed in compiz: | |
| status: | In Progress → Fix Committed |
| Changed in compiz-libcompizconfig: | |
| status: | New → Won't Fix |
| Changed in compiz: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package compiz - 1:0.9.12.
---------------
compiz (1:0.9.
[ James Jones ]
* Added support for GL_EXT_
based GPUs to avoid screen refresh issues. (LP: #269904)
[ Kyle Brenneman ]
* Added support for GL_EXT_
based GPUs to avoid screen refresh issues. (LP: #269904)
[ Viktor A. Danilov ]
* Added support for GL_EXT_
based GPUs to avoid screen refresh issues. (LP: #269904)
[ Chris Townsend ]
* Added support for GL_EXT_
based GPUs to avoid screen refresh issues. (LP: #269904)
[ Stephen M. Webb ]
* Added support for GL_EXT_
based GPUs to avoid screen refresh issues. (LP: #269904)
* libdecoration/
directories (LP: #1392715)
* Switcher Plugin: renamed a local variable so it does not hide a
function parameter. (LP: #1101585)
* added support for multi-arch installations (LP: #1395105, #959282)
* libcompizconfig: reorder stat() and open() calls to eliminate a race
condition (LP: #1101608)
* dodge plugin: avoid potential null pointer dereferences (LP:
#1101554)
* PrivateScreen unit tests: added additional assertions to verify the
tests are run in an expected state (LP: #1101413)
[ Ubuntu daily release ]
* New rebuild forced
[ Brandon Schaefer ]
* Rev 3891 change caused 2 known regressions. (Could be more).
Reverting. (LP: #1398512, #1393020)
-- Ubuntu daily release <email address hidden> Wed, 10 Dec 2014 19:52:06 +0000