From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] USE flags names that make sense for boost lib suggestions needed
Date: Sat, 16 Apr 2005 18:26:23 -0500 [thread overview]
Message-ID: <42619F1F.3020202@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
im currently changing the boost build process so users who require boost
only as a dependency of another app only get release versions,
developers would get debug versions as well (another ~40-90MB varying
from system to system it seems) USE=debug is easy choice there
i intended to then utilize USE=threads to add the multi threaded
versions of libs and single by default or -threads, here comes my
question, the build process allows for <threading>multi
<threading>single and <threading>multi/single, building only
multithreaded versions, only single threaded versions, or both.
do the three choices make sense or are we better off with only building
single threaded versions and on USE=threads (to use what already exists
rather then making a new USE flag) then build single/multi
else id need possibly two awkwardly named USE flags (and suggestions for
names (using threads and threadsonly, similar to nptl?)
similarly it allows for linking to static, dynamic or both
should the static USE flags be used to change from dynamic (proposed
default behaviour) to static, or ADD so build process uses
<runtime-link>static/dynamic
(using static and staticonly if 3 states are needed?)
i guess i could get away with only 2 new USE flags (threadsonly and
staticonly)
ok, do we need them, shouldnt we have them?
any ideas, suggestion, critcism welcome
Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCYZ8fUpKYMelfdYERAkDrAJwNsYnyDH03J9VmS9Ax7vbj6lmaJACfd+nd
64dwN4WTTw2AudeKOJETgpo=
=JFaH
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-04-16 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 23:26 Daniel Goller [this message]
2005-04-21 16:24 ` [gentoo-dev] USE flags names that make sense for boost lib suggestions needed Grant Goodyear
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=42619F1F.3020202@gentoo.org \
--to=morfic@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