From: Thomas Danckaert <post@thomasdanckaert.be>
To: Dave Love <dave.love@manchester.ac.uk>
Cc: 28690@debbugs.gnu.org
Subject: [bug#28690] provide a lib output for boost
Date: Thu, 19 Oct 2017 14:52:32 +0200 [thread overview]
Message-ID: <cuca80nxptb.fsf@thomasdanckaert.be> (raw)
In-Reply-To: <87d164b36m.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Tue, 03 Oct 2017 17:34:41 +0100")
Dave Love <dave.love@manchester.ac.uk> writes:
> I mentioned elsewhere noticing the large size of boost in closures.
> I've now realized what the problem was with making a lib output, and
> done one, as below. However, presumably it should have a dependency of
> out on lib for compatibility, and I don't know the right way to do that.
Yes, I've also noticed that, and also think it's worth to split the
package.
I don't think it's possible to have one output of a package depend on
another, though. We could just add boost:lib to the inputs for every
package which relies on boost (except for packages which only rely on
header-only parts of boost)?
Another solution might be to turn the 2 outputs into 2 separate guix
packages, "boost" and "boost-libs", where "boost" only contains the
headers, and has "boost-libs" as a propagated-input. I'm not sure if
this will do the right thing (i.e. make boost-libs available in the
build environment when boost is a regular input, but not propagate it
further), someone should try it out ;).
Thomas
next prev parent reply other threads:[~2017-10-19 12:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 16:34 [bug#28690] provide a lib output for boost Dave Love
2017-10-11 8:39 ` Roel Janssen
2017-10-19 10:57 ` Dave Love
2017-10-19 14:19 ` Roel Janssen
2017-10-20 12:58 ` Ludovic Courtès
2017-10-20 13:21 ` Thomas Danckaert
2017-10-20 16:14 ` Ludovic Courtès
2017-10-22 16:50 ` Dave Love
2017-10-22 19:03 ` Ludovic Courtès
2017-10-24 13:28 ` Thomas Danckaert
2017-10-24 15:30 ` Ludovic Courtès
2017-12-03 23:07 ` Ricardo Wurmus
2017-12-04 8:19 ` Thomas Danckaert
2017-10-20 16:09 ` Dave Love
2017-10-20 20:14 ` Ludovic Courtès
2017-10-19 12:52 ` Thomas Danckaert [this message]
2017-10-20 9:20 ` Dave Love
2017-10-20 9:46 ` Thomas Danckaert
2017-10-20 15:34 ` Dave Love
2022-01-13 15:45 ` zimoun
2022-02-03 2:30 ` zimoun
2022-06-23 10:01 ` zimoun
2022-06-23 11:35 ` Thomas Danckaert via Guix-patches
2022-10-08 15:06 ` bug#28690: " zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cuca80nxptb.fsf@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=28690@debbugs.gnu.org \
--cc=dave.love@manchester.ac.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).