public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE flags names that make sense for boost lib suggestions needed
Date: Thu, 21 Apr 2005 11:24:08 -0500	[thread overview]
Message-ID: <20050421162408.GC22089@bmb38.uth.tmc.edu> (raw)
In-Reply-To: <42619F1F.3020202@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]

Daniel Goller wrote: [Sat Apr 16 2005, 06:26:23PM CDT]
> -----BEGIN PGP SIGNED MESSAGE-----
> 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'm not really sure what you mean by "debug" versions.  Are those
versions built with "-g"?  In that case you don't need a USE flag, just
let the user add "-g" to CFLAGS (and "nostrip" to FEATURES).

> 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.

Any idea what the difference in build time is?  If it's minor, then just
do both.  Just because something can be optional does not mean that it
must be optional.

> 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?)

In any event, would just ask vapier for his opinion, and do whatever he
says.  

-g2boojum-
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-04-21 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 23:26 [gentoo-dev] USE flags names that make sense for boost lib suggestions needed Daniel Goller
2005-04-21 16:24 ` Grant Goodyear [this message]

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=20050421162408.GC22089@bmb38.uth.tmc.edu \
    --to=g2boojum@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