From: Luca Barbato <lu_zero@gentoo.org>
To: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Useflag static split
Date: Mon, 22 Nov 2004 16:12:02 +0100 [thread overview]
Message-ID: <41A201C2.3020201@gentoo.org> (raw)
Lately I found lots of problems and inconsistency for the useflag static.
Sometimes it means "build only static", sometimes "build static and shared".
The problem:
If you need to build something static you need the static libs.
If the use flag depend is allowed probably that could be a dirty
solution. Luckly it isn't yet, so we have to find a cleaner one:
1- split static in static and static-lib (static-lib will make the
library build also the static version, static will build _just_ the
static lib)
2- make everly library build always the static library and let use
static just apply for executables.
Tell me what you think
lu
PS: some annoying examples: qemu:qemu-fast, openssh:static
--
Luca Barbato
Developer
Gentoo Linux http://www.gentoo.org/~lu_zero
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-11-22 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:12 Luca Barbato [this message]
2004-11-22 15:31 ` [gentoo-dev] Useflag static split Mike Frysinger
2004-11-22 17:38 ` Donnie Berkholz
2004-11-23 19:08 ` Paul de Vrieze
2004-11-22 17:37 ` Donnie Berkholz
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=41A201C2.3020201@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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