[systemd-devel] why are the systemd binaries so huge and can we do something about that?

[Michael Biebl]

2016-05-17 10:36 GMT+02:00 Lennart Poettering <lennart at poettering.net>:
> On Mon, 16.05.16 04:24, Michael Biebl (mbiebl at gmail.com) wrote:
>
>> Hi,
>
>> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ ?
>> What's up with systemd-analyze?
>
> it embedds much of PID1's logic actually, in order to do unit file
> checking.
>
>> Could we move more common functionality into a shared, private library
>> to counter the constant growth?
>
> This has been discussed, and yeah, this should be a good thing to
> do. It's just a matter of doing it. A shared, but explicitly private
> library would be good. I figure it should be built from the stuff in
> src/shared and src/basic. This would mean it won't help in the
> systemd-analyze in case, but I think it's OK, given that that's a
> debugging tool.

Looks like this is not quite that simple. I fiddled with this for a
bit without any success.
We have quite a bit of noinst libs atm [1].
Would you turn all those into pkglib_LTLIBRARIES?
Merge them into a single lib (or maybe two: libudev-internal and
libsystemd-internal?)

[1]
libbasic.la
libshared.la
libfirewall.la
libcore.la
libsystemd-internal.la
libsystemd-network.la
libudev-internal.la
libudev-core.la
libjournal-core.la
libsystemd-journal-internal.la
libmachine-core.la
libnetworkd-core.la
liblogind-core.la

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?