Python extension module should be installed into arch-dependent directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently Python extension module installs in '/usr/lib/
Why this was made in early days documented in Compiz:
# We must build the python module using CMake instead of distutils.
#
# The only way in which the python module can be built using distutils
# is by using add_custom_command to "generate" it into existence.
# Unfortunately this has drawbacks. Namely, it is not possible for
# add_custom_command to depend on library targets. Because of that, there's
# no way that we can guarantee that libcompizconfig.so will be linked
# before compizconfig.so (which is required). The best that we can do
# there is to use add_custom_target, and make that target depend on the
# file,
but seems like this is not an issue anymore in new Cmake versions:
> Changed in version 3.16: A target-level dependency is added if any dependency is a byproduct of a target or any of its build events in the same directory to ensure the byproducts will be available before this target is built.
https:/
Related branches
- Alberts Muktupāvels: Approve
- Artem (community): Approve
- Compiz Maintainers: Pending requested
-
Diff: 254 lines (+35/-78)8 files modifiedCMakeLists.txt (+1/-1)
cmake/CompizCommon.cmake (+1/-1)
compizconfig/ccsm/CMakeLists.txt (+5/-5)
compizconfig/compizconfig-python/CMakeLists.txt (+15/-65)
compizconfig/compizconfig-python/setup.py (+7/-0)
compizconfig/compizconfig-python/tests/compiz_config_test.py (+3/-3)
debian/control (+1/-1)
debian/python3-compizconfig.install (+2/-2)
Changed in compiz: | |
status: | New → Fix Committed |
I have released version 0.9.14.2 today, which includes this fix.