Zbigniew Jędrzejewski-Szmek
f00ccf93b7
We have two concepts: a list of files that should be extracted from an
intermediate build artifact to be used in a later build artifact, and for a
given artifact, a list "donors". The first list was called "extract", because
it is passed to the .extract_objects() meson function, and the second was
called "objects", because that is the meson parameter to specify pre-built
objects files (6350d2dbd9). But this naming is
confusing: we don't care about the 'extract' step, this is something internal
to the build machinery. And 'objects' is a very generic term.
Let's use 'export' for the stuff that is "exported" for other binaries to use,
and 'import' to say where to import from. Those terms are symmetrical and the
association between them should be intuitive. (If you think the terms are
actually assymetrical, there are precedents for confusing the import with the
import sources. E.g. in modern English, turkeys are called so because they were
imported from the Americas and guineafowls were imported from Africa via
Türkiye and all that foreign stuff is alike.)
19 lines
573 B
Meson
19 lines
573 B
Meson
# SPDX-License-Identifier: LGPL-2.1-or-later
|
|
|
|
if conf.get('ENABLE_HIBERNATE') != 1
|
|
subdir_done()
|
|
endif
|
|
|
|
executables += [
|
|
libexec_template + {
|
|
'name' : 'systemd-hibernate-resume',
|
|
'sources' : files('hibernate-resume.c'),
|
|
'export' : files('hibernate-resume-config.c'),
|
|
},
|
|
generator_template + {
|
|
'name' : 'systemd-hibernate-resume-generator',
|
|
'sources' : files('hibernate-resume-generator.c'),
|
|
'import' : ['systemd-hibernate-resume'],
|
|
},
|
|
]
|