From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110249] IGT command line tools load redundant GUI libraries
Date: Tue, 26 Mar 2019 14:31:10 +0000 [thread overview]
Message-ID: <bug-110249-502-n4qLCEGu26@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110249-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110249
--- Comment #2 from Emil Velikov <emil.l.velikov@gmail.com> ---
Some food for thought:
The old autotools build did not have this problem since it:
- was creating a static libigt library
- yet ^^ would lead to slightly longer build times and overall larger bundle
- ^^ would only pull the required dependencies into the linking process
For reference:
$ objdump -x /usr/bin/intel_gpu_top | grep -w NEEDED
NEEDED libpthread.so.0
NEEDED libc.so.6
If it were me I would:
- static link
- drop all the extra rpath from the meson build
- if size is an issue - enable LTO
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1549 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-26 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 13:11 [Bug 110249] IGT command line tools load redundant GUI libraries bugzilla-daemon
2019-03-26 13:41 ` bugzilla-daemon
2019-03-26 14:31 ` bugzilla-daemon [this message]
2019-03-26 14:35 ` bugzilla-daemon
2019-03-26 14:44 ` bugzilla-daemon
2019-03-26 16:05 ` bugzilla-daemon
2019-03-26 16:20 ` bugzilla-daemon
2019-04-09 11:16 ` bugzilla-daemon
2019-11-12 7:40 ` bugzilla-daemon
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=bug-110249-502-n4qLCEGu26@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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