gnome/nautilus
gnome/nautilus
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/nautilus synced 2024-11-04 19:08:23 +00:00
Code Issues Projects Releases Packages Wiki Activity
nautilus/data/meson.build

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

161 lines
3.9 KiB
Meson
Raw Permalink Normal View History

Revert "Revert "build: Don't loop over icons"" This reverts commit 37799d64caed4a6e06b5ed534012664b5afaf812
2018-09-14 05:12:34 +00:00
icondir = join_paths('icons', 'hicolor', 'scalable', 'apps')
install_data(
build: Use new nightly icon for the Devel profile A variant of the app icon has been introduced in the previous commit. Let's use it for the Devel profile. Part ot https://gitlab.gnome.org/GNOME/Initiatives/issues/12
2019-10-13 15:51:35 +00:00
join_paths(icondir, 'org.gnome.Nautilus' + profile + '.svg'),
Revert "Revert "build: Don't loop over icons"" This reverts commit 37799d64caed4a6e06b5ed534012664b5afaf812
2018-09-14 05:12:34 +00:00
install_dir: join_paths(datadir, icondir),
rename: '@0@.svg'.format(application_id)
)
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
build: Use install_data() to rename icons Since 0.46.0, Meson allows renaming files when installing them. This is useful to replace any workarounds to achieve the same (namely, the icons).
2018-04-28 17:15:35 +00:00
icondir = join_paths('icons', 'hicolor', 'symbolic', 'apps')
install_data(
join_paths(icondir, 'org.gnome.Nautilus-symbolic.svg'),
install_dir: join_paths(datadir, icondir),
rename: '@0@-symbolic.svg'.format(application_id)
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
)
meson: Update to 0.59
2022-02-18 16:03:14 +00:00
po_dir = join_paths(meson.project_source_root(), 'po')
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
desktop_conf = configuration_data()
desktop_conf.set('icon', application_id)
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
desktop = i18n.merge_file(
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
input: configure_file(
input: files('org.gnome.Nautilus.desktop.in.in'),
output: 'org.gnome.Nautilus.desktop.in',
configuration: desktop_conf
),
output: '@0@.desktop'.format(application_id),
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
install: true,
install_dir: desktopdir,
po_dir: po_dir,
type: 'desktop'
)
desktop_autorun_software = i18n.merge_file(
input: 'nautilus-autorun-software.desktop.in',
output: 'nautilus-autorun-software.desktop',
install: true,
install_dir: desktopdir,
po_dir: po_dir,
type: 'desktop'
)
appdata: Use build date between releases Although build date is wrong for releases, we still need a date between releases to pass appstream validation. Partly revert commit b7e44006b66b2aff2f6c51afb6100b3bab40557c To make it easy for future releases, provide copy-pastable templates and introduce release type attributes. In the future we may want to use the new "snapshot" type and drop the date, as per https://github.com/ximion/appstream/issues/570 Reference: https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Releases.html
2024-01-09 16:38:15 +00:00
# get current date, used as build date for snapshots between releases
today = 'unknown'
date = find_program('date', required: false)
if date.found()
r = run_command(date, '-I')
if r.returncode() == 0
today = r.stdout().strip()
endif
endif
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
appdata_conf = configuration_data()
appdata_conf.set('appid', application_id)
appdata: Use build date between releases Although build date is wrong for releases, we still need a date between releases to pass appstream validation. Partly revert commit b7e44006b66b2aff2f6c51afb6100b3bab40557c To make it easy for future releases, provide copy-pastable templates and introduce release type attributes. In the future we may want to use the new "snapshot" type and drop the date, as per https://github.com/ximion/appstream/issues/570 Reference: https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Releases.html
2024-01-09 16:38:15 +00:00
appdata_conf.set('build-date', today)
build: autappdata build version As suggested by @naheemsays on Matrix and inspired by https://gitlab.gnome.org/GNOME/gtk/-/commit/775dbec2e6a0c90015e8bc39f433f5d76f12bd41
2023-10-05 06:26:07 +00:00
appdata_conf.set('release-version', meson.project_version())
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
appdata = i18n.merge_file(
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
input: configure_file(
appdata: Use non-legacy file extension https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#spec-component-location
2024-01-09 16:45:38 +00:00
input: files('org.gnome.Nautilus.metainfo.xml.in.in'),
output: 'org.gnome.Nautilus.metainfo.xml.in',
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
configuration: appdata_conf
),
appdata: Use non-legacy file extension https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#spec-component-location
2024-01-09 16:45:38 +00:00
output: '@0@.metainfo.xml'.format(application_id),
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
install: true,
build: Install appstream metadata to non-deprecated location This was already done in 5d75a4a5 but accidentally reverted in 983892a6
2018-01-30 17:30:08 +00:00
install_dir: join_paths(datadir, 'metainfo'),
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
po_dir: po_dir
)
service_conf = configuration_data()
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
service_conf.set('appid', application_id)
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
service_conf.set('bindir', join_paths(prefix, bindir))
configure_file(
input: 'org.gnome.Nautilus.service.in',
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
output: '@0@.service'.format(application_id),
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
configuration: service_conf,
install_dir: servicedir
)
configure_file(
input: 'org.freedesktop.FileManager1.service.in',
output: 'org.freedesktop.FileManager1.service',
configuration: service_conf,
install_dir: servicedir
)
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
2018-03-16 15:24:11 +00:00
search_provider_conf = configuration_data()
search_provider_conf.set('appid', application_id)
search_provider_conf.set('profile', profile)
configure_file(
configuration: search_provider_conf,
input: files('org.gnome.Nautilus.search-provider.ini.in'),
install_dir: join_paths(datadir, 'gnome-shell', 'search-providers'),
output: '@0@.search-provider.ini'.format(application_id)
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
)
data/meson.build: Compile gschemas during the build In particular this can be useful when running tests from the build directory in Builder.
2018-03-24 16:02:49 +00:00
gnome.compile_schemas(
build_by_default: true,
depend_files: 'org.gnome.nautilus.gschema.xml'
)
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
install_data(
'org.gnome.nautilus.gschema.xml',
install_dir: join_paths(datadir, 'glib-2.0', 'schemas')
)
desktop_file_validate = find_program('desktop-file-validate', required: false)
if desktop_file_validate.found()
test(
'validate-desktop',
desktop_file_validate,
args: [
desktop.full_path()
ci: Specify test dependencies to fix pipeline The `validate-desktop`, `validate-desktop-autorun-software` and `validate-appdata` meson tests fail currently because of the updated meson. This is because of the recent change, which requires explicit specification of dependencies. Let's specify them to fix the pipeline. https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/372
2021-04-21 08:18:55 +00:00
],
depends: [
desktop,
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
]
)
test(
'validate-desktop-autorun-software',
desktop_file_validate,
args: [
desktop_autorun_software.full_path()
ci: Specify test dependencies to fix pipeline The `validate-desktop`, `validate-desktop-autorun-software` and `validate-appdata` meson tests fail currently because of the updated meson. This is because of the recent change, which requires explicit specification of dependencies. Let's specify them to fix the pipeline. https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/372
2021-04-21 08:18:55 +00:00
],
depends: [
desktop_autorun_software,
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
]
)
build: add tests for data files This will help avoid potentially breaking pre-release changes in the future. https://bugzilla.gnome.org/show_bug.cgi?id=786104
2017-08-10 10:20:43 +00:00
endif
appdata: Improve appdata for AppStream 1.0 - Add the `<developer><name>` tag - Mark the `<developer_name>` tag as deprecated - Use appstreamcli to validate appdata
2023-12-21 19:47:23 +00:00
appstreamcli = find_program('appstreamcli', required: false)
if appstreamcli.found()
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
test(
appdata: Improve appdata for AppStream 1.0 - Add the `<developer><name>` tag - Mark the `<developer_name>` tag as deprecated - Use appstreamcli to validate appdata
2023-12-21 19:47:23 +00:00
'validate-appdata', appstreamcli,
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
args: [
appdata: Improve appdata for AppStream 1.0 - Add the `<developer><name>` tag - Mark the `<developer_name>` tag as deprecated - Use appstreamcli to validate appdata
2023-12-21 19:47:23 +00:00
'validate', '--no-net', appdata.full_path()
ci: Specify test dependencies to fix pipeline The `validate-desktop`, `validate-desktop-autorun-software` and `validate-appdata` meson tests fail currently because of the updated meson. This is because of the recent change, which requires explicit specification of dependencies. Let's specify them to fix the pipeline. https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/372
2021-04-21 08:18:55 +00:00
],
depends: [
appdata,
build: general cleanups This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
2017-12-13 18:13:54 +00:00
]
)
build: add tests for data files This will help avoid potentially breaking pre-release changes in the future. https://bugzilla.gnome.org/show_bug.cgi?id=786104
2017-08-10 10:20:43 +00:00
endif
Port to Tracker 3 Mostly the port is straightforward, we connect to tracker-miner-fs explicitly over D-Bus instead of the centralized tracker-store daemon we connected to previously. The search-engine-tracker test is now isolated from the user's real Tracker index using the `tracker-sandbox` script provided by Tracker, and it lets tracker-miner-fs index the test file rather than trying to synthesize the expected database contents. There are more changes in nautilus-tag-manager.c. Until now, starred file information was stored in the tracker-miner-fs database. This has some downsides, firstly the data is deleted if someone runs `tracker reset --hard`, secondly it isn't possible to do this from inside a Flatpak sandbox with Tracker 3.0. because the This commit changes the NautilusTagManager to set up a private database inside XDG_DATA_HOME/nautilus/tags. This stores the starred file information. The database is managed with Tracker, which allows us to continue using the rename-tracking that tracker-miner-fs provides. The same limitations apply as before that only files in indexed locations can be starred.
2020-05-02 14:46:28 +00:00
portal: Introduce implementation stub From now on nautilus claims to implement the FileChooser portal. For now it's a lie. But the next few commits will make it true.
2024-04-20 10:51:51 +00:00
portal_impl_conf = configuration_data()
portal_impl_conf.set('appid', application_id)
configure_file(
input: 'nautilus.portal.in',
output: 'nautilus.portal',
configuration: portal_impl_conf,
install_dir: datadir / 'xdg-desktop-portal' / 'portals',
)
Port to Tracker 3 Mostly the port is straightforward, we connect to tracker-miner-fs explicitly over D-Bus instead of the centralized tracker-store daemon we connected to previously. The search-engine-tracker test is now isolated from the user's real Tracker index using the `tracker-sandbox` script provided by Tracker, and it lets tracker-miner-fs index the test file rather than trying to synthesize the expected database contents. There are more changes in nautilus-tag-manager.c. Until now, starred file information was stored in the tracker-miner-fs database. This has some downsides, firstly the data is deleted if someone runs `tracker reset --hard`, secondly it isn't possible to do this from inside a Flatpak sandbox with Tracker 3.0. because the This commit changes the NautilusTagManager to set up a private database inside XDG_DATA_HOME/nautilus/tags. This stores the starred file information. The database is managed with Tracker, which allows us to continue using the rename-tracking that tracker-miner-fs provides. The same limitations apply as before that only files in indexed locations can be starred.
2020-05-02 14:46:28 +00:00
subdir('ontology')
Use Tracker Miners inside Flatpak when not available on the host This means the Nautilus flatpak will be able to use Tracker on systems which don't have Tracker 3 available on the host. It comes at a cost of increased resource consumption inside the Flatpak due running an extra indexer process there.
2020-08-01 15:25:27 +00:00
subdir('tracker')
Reference in a new issue Copy permalink