system/weston
system/weston
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/weston synced 2024-07-21 10:44:25 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
weston/ivi-shell/meson.build

60 lines
1.4 KiB
Meson
Raw Normal View History

Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
if get_option('shell-ivi')
srcs_shell_ivi = [
'ivi-shell.c',
'ivi-layout.c',
'ivi-layout-transition.c',
ivi_application_server_protocol_h,
ivi_application_protocol_c,
input_method_unstable_v1_server_protocol_h,
input_method_unstable_v1_protocol_c,
]
plugin_shell_ivi = shared_library(
'ivi-shell',
srcs_shell_ivi,
build: simplify include_directories Define common_inc which includes both public_inc and the project root directory. The project root directory will allow access to config.h and all the shared/ headers. Replacing all custom '.', '..', '../..', '../shared' etc. include paths with common_inc reduces clutter in the target definitions and enforces the common #include directive style, as e.g. including shared/ headers without the subdirectory name no longer works. Unfortunately this does not prevent one from using private libweston headers with the usual include pattern for public headers. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-04-05 14:09:28 +00:00
include_directories: common_inc,
build: link libm explicitly In the future libweston will stop providing it for its users, since it's not part of libweston API. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-10-17 13:17:57 +00:00
dependencies: [
dep_libm,
Link Weston plugins to libexec-weston.so All these plugins use symbols that were exported by the weston executable and are now exported by libexec-weston.so. Linking these to libexec-weston.so fixes unresolved symbols. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-07-09 09:00:41 +00:00
dep_libexec_weston,
ivi-shell: add new signal to notify ivi shell destroying In the case the controlelrs are depended on ivi-shell resource, it must be destroy before the ivi shell destroy. To do this, add new ivi shell destroy signal on ivi shell, emit it on the begining of the shell destroying Suggested-by: Harsha M M <harsha.manjulamallikarjun@in.bosch.com> Suggested-by: Michael Olbrich <m.olbrich@pengutronix.de> Suggested-by: Marius Vlad <marius.vlad@collabora.com> Signed-off-by: Tran Ba Khang(MS/EMC31-XC) <Khang.TranBa@vn.bosch.com>
2022-11-09 02:24:12 +00:00
dep_libweston_public,
dep_libshared
build: link libm explicitly In the future libweston will stop providing it for its users, since it's not part of libweston API. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-10-17 13:17:57 +00:00
],
Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
name_prefix: '',
install: true,
build: add rpath to modules that use symbols from libexec_weston The cms-static, desktop-shell, hmi-controller, ivi-shell, and screen-share modules use symbols from libexec_weston, e.g.: $ ldd /usr/lib/x86_64-linux-gnu/weston/desktop-shell.so | grep "not found" libexec_weston.so.0 => not found Loading these modules from weston happens to work because the weston executable itself links against libexec_weston, and has an rpath set. Still, these modules depend on a library in a non-standard location. Adding an rpath could help static checkers to make sure all shared objects' dependencies are present. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
2020-02-04 23:40:01 +00:00
install_dir: dir_module_weston,
install_rpath: '$ORIGIN'
Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
)
env_modmap += 'ivi-shell.so=@0@;'.format(plugin_shell_ivi.full_path())
install_headers('ivi-layout-export.h', subdir: 'weston')
srcs_ivi_hmi = [
'hmi-controller.c',
ivi_hmi_controller_server_protocol_h,
ivi_hmi_controller_protocol_c,
]
plugin_ivi_hmi = shared_library(
'hmi-controller',
srcs_ivi_hmi,
build: simplify include_directories Define common_inc which includes both public_inc and the project root directory. The project root directory will allow access to config.h and all the shared/ headers. Replacing all custom '.', '..', '../..', '../shared' etc. include paths with common_inc reduces clutter in the target definitions and enforces the common #include directive style, as e.g. including shared/ headers without the subdirectory name no longer works. Unfortunately this does not prevent one from using private libweston headers with the usual include pattern for public headers. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-04-05 14:09:28 +00:00
include_directories: common_inc,
Link Weston plugins to libexec-weston.so All these plugins use symbols that were exported by the weston executable and are now exported by libexec-weston.so. Linking these to libexec-weston.so fixes unresolved symbols. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-07-09 09:00:41 +00:00
dependencies: [
dep_libexec_weston,
dep_libweston_public,
dep_libshared
],
Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
name_prefix: '',
install: true,
build: add rpath to modules that use symbols from libexec_weston The cms-static, desktop-shell, hmi-controller, ivi-shell, and screen-share modules use symbols from libexec_weston, e.g.: $ ldd /usr/lib/x86_64-linux-gnu/weston/desktop-shell.so | grep "not found" libexec_weston.so.0 => not found Loading these modules from weston happens to work because the weston executable itself links against libexec_weston, and has an rpath set. Still, these modules depend on a library in a non-standard location. Adding an rpath could help static checkers to make sure all shared objects' dependencies are present. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
2020-02-04 23:40:01 +00:00
install_dir: dir_module_weston,
install_rpath: '$ORIGIN'
Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
)
env_modmap += 'hmi-controller.so=@0@;'.format(plugin_ivi_hmi.full_path())
ivi_test_config = configuration_data()
ivi_test_config.set('bindir', dir_bin)
ivi-shell: bring back reference weston.ini In commit d8e09afc9f1e ("tests: Convert ivi-shell-app-test.c to use `weston_ini_setup`") the reference weston.ini for the ivi-shell was removed, because it is not required by the test anymore. The reference weston.ini still has value as an example for the ivi-shell and how the ivi-shell-user-interface has to be configured. Retrieving this information from the test case is not intuitive. Furthermore, the file is still referenced by the ivi-shell/README, and the configuration_data for generating the file was not fully removed. Bring back the reference weston.ini for the ivi-shell and, while at it, cleanup the configuration_data() to define only keys that are actually used in weston.ivi.in. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
2021-06-04 10:02:50 +00:00
ivi_test_config.set('westondatadir', dir_data / 'weston')
configure_file(
input: 'weston.ini.in',
output: 'weston.ini',
configuration: ivi_test_config
)
Add Meson build system Meson is a build system, currently implemented in Python, with multiple output backends, including Ninja and Make. The build file syntax is clean and easy to read unlike autotools. In practise, configuring and building with Meson and Ninja has been observed to be much faster than with autotools. Also cross-building support is excellent. More information at http://mesonbuild.com Since moving to Meson requires some changes from users in any case, we took this opportunity to revamp build options. Most of the build options still exist, some have changed names or more, and a few have been dropped. The option to choose the Cairo flavour is not implemented since for the longest time the Cairo image backend has been the only recommended one. This Meson build should be fully functional and it installs everything an all-enabled autotools build does. Installed pkg-config files have some minor differences that should be insignificant. Building of some developer documentation that was never installed with autotools is missing. It is expected that the autotools build system will be removed soon after the next Weston release. Signed-off-by: Daniel Stone <daniels@collabora.com> Co-authored-by: Pekka Paalanen <pq@iki.fi> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2016-11-24 15:54:51 +00:00
endif
Reference in a new issue Copy permalink