From: Joshua Lock <joshua.lock@collabora.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] systemd: build with compatibility libraries
Date: Mon, 19 Oct 2015 20:52:53 +0100 [thread overview]
Message-ID: <56254A15.20701@collabora.co.uk> (raw)
In-Reply-To: <20151019125722.GC16160@ad.chargestorm.se>
On 19/10/15 13:57, Anders Darander wrote:
> * Joshua Lock <joshua.lock@collabora.co.uk> [151016 17:52]:
>
>> There are recipes in the Core metadata that have optional systemd
>> support but expect the old, separate, libsystemd-foo pkg-config files
>> (not the newer unified libsystemd).
>
> Any size impact? Just wondering as you're changing the default.
> (Assuming that it was off by default previously?)
The compat-libs (libsystemd-daemon libsystemd-login libsystemd-journal
libsystemd-id128) are packaged separately, so you only see an increase
in image size if something pulls them in to your image.
The -dev, -dbg and -ptest package sizes all increase slightly:
joshuagl@owlbear:/srv/build/systemd-size$ buildhistory-diff -a | grep
PKGSIZE
packages/i586-poky-linux/systemd/systemd-dbg: PKGSIZE changed from
54364265 to 55148696 (+1%)
packages/i586-poky-linux/systemd/systemd-dev: PKGSIZE changed from 98921
to 105487 (+6%)
packages/i586-poky-linux/systemd/systemd-ptest: PKGSIZE changed from
3156181 to 3156103 (0%)
Regards,
Joshua
>
> Cheers,
> Anders
>
>
>> -PACKAGECONFIG ??= "xz ldconfig \
>> +PACKAGECONFIG ??= "xz ldconfig compat \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam', '', d)} \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'xkbcommon', '', d)} \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux', '', d)} \
>> @@ -89,6 +89,7 @@ PACKAGECONFIG[ldconfig] = "--enable-ldconfig,--disable-ldconfig,,"
>> PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux"
>> PACKAGECONFIG[valgrind] = "ac_cv_header_valgrind_memcheck_h=yes ac_cv_header_valgrind_valgrind_h=yes ,ac_cv_header_valgrind_memcheck_h=no ac_cv_header_valgrind_valgrind_h=no ,valgrind"
>> PACKAGECONFIG[qrencode] = "--enable-qrencode,--disable-qrencode,qrencode"
>> +PACKAGECONFIG[compat] = "--enable-compat-libs,--disable-compat-libs"
>
>> CACHED_CONFIGUREVARS += "ac_cv_path_KILL=${base_bindir}/kill"
>> CACHED_CONFIGUREVARS += "ac_cv_path_KMOD=${base_bindir}/kmod"
next prev parent reply other threads:[~2015-10-19 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 15:51 [PATCH 0/6] Various metadata tweaks Joshua Lock
[not found] ` <cover.1445010543.git.joshua.lock@collabora.co.uk>
2015-10-16 15:51 ` [PATCH 1/6] systemd: build with compatibility libraries Joshua Lock
2015-10-19 12:57 ` Anders Darander
2015-10-19 19:52 ` Joshua Lock [this message]
2015-10-20 4:48 ` Anders Darander
2015-10-20 3:23 ` Khem Raj
2015-10-20 9:40 ` Joshua Lock
2015-10-16 15:51 ` [PATCH 2/6] weston: add PACKAGECONFIG to build with systemd-login support Joshua Lock
2015-10-16 15:51 ` [PATCH 3/6] systemd: make dbus an optional build time dependency Joshua Lock
2015-10-16 15:51 ` [PATCH 4/6] weston: add a PACKAGECONFIG option for xwayland support Joshua Lock
2015-10-16 15:51 ` [PATCH 5/6] xserver-xorg: add Xwayland RRECOMMENDS Joshua Lock
2015-10-16 15:51 ` [PATCH 6/6] xserver-xorg: drop empty ${PN}-security-policy package Joshua Lock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56254A15.20701@collabora.co.uk \
--to=joshua.lock@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox