forked from enlightenment/efl
meson: Fix evas engine install directory.
Evas module loading code assumes engines are installed in evas/modules/engines. As part of the fixes building evas with meson, the engines are under a subproject named evas/engines, causing the modules to be installed in libdir/evas/engines/modules by default. This commit adds a override of the directory the engine modules are installed to use the correct location. Reviewed-by: Marcel Hollerbach <mail@marcel-hollerbach.de> Differential Revision: https://phab.enlightenment.org/D8693
This commit is contained in:
parent
1799f79c54
commit
132c00a4cb
|
@ -38,7 +38,10 @@ foreach engine_conf : engines
|
|||
set_variable(var_name, engine_dep)
|
||||
|
||||
mod_full_name = engine
|
||||
mod_install_dir = join_paths(dir_package_modules, 'engines', engine, version_name)
|
||||
# root meson.build declares the root evas engines project as `evas/engines`,
|
||||
# but modules must be installed in evas/modules
|
||||
evas_package_modules = join_paths(dir_lib, 'evas', 'modules')
|
||||
mod_install_dir = join_paths(evas_package_modules, 'engines', engine, version_name)
|
||||
|
||||
subdir(engine)
|
||||
|
||||
|
|
Loading…
Reference in New Issue