all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 46728@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#46728] [PATCH 0/7] gnu: aws-sdk-cpp: Update to 1.8.148.
Date: Tue, 02 Mar 2021 20:37:56 +0100	[thread overview]
Message-ID: <878s75uz1n.fsf_-_@gnu.org> (raw)
In-Reply-To: <CA+3U0Z=v3cOfb=WifVf4_eG=JRQfGHNXkJVxACRzNK_ZM2g-QA@mail.gmail.com> (Greg Hogan's message of "Thu, 25 Feb 2021 09:19:31 -0500")

Hi,

Greg Hogan <code@greghogan.com> skribis:

> The AWS packages (aws-sdk-cpp and dependencies) are currently built as
> static libraries. I would like to build both static and shared but could
> not find an example or simple method for building both using cmake. Do you
> think it would be worthwhile to extend the cmake-build-system to optionally
> configure, build, and install static libraries with additional phases? The
> gnu-build-system makes it easy to inline a new phase into the package
> definition (when the makefile has both 'make' and 'make static' targets)
> but with CMake we are forced to duplicate the configure phase, which is 44
> lines of code.

In general, it’s best to build only shared libraries.  That allows for
reduced memory usage, fast security updates via grafts, etc.  So if you
could make the AWS packages build as shared libraries only, that’d be
great.

It’s OK to optionally add static libraries, preferably in a separate
output or even a separate package, but that’s not what should be used by
default.

Does that make sense?

Thanks,
Ludo’.




  reply	other threads:[~2021-03-02 19:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 23:11 [bug#46728] [PATCH 0/7] gnu: aws-sdk-cpp: Update to 1.8.148 Greg Hogan
     [not found] ` <handler.46728.B.161412192713427.ack@debbugs.gnu.org>
2021-02-23 23:14   ` [bug#46728] [PATCH 1/7] gnu: aws-c-common: Update to 0.5.1 Greg Hogan
2021-02-23 23:15   ` [bug#46728] [PATCH 2/7] gnu: aws-checksums: Update to 0.1.11 Greg Hogan
2021-02-23 23:16   ` [bug#46728] [PATCH 3/7] gnu: Add aws-c-cal Greg Hogan
2021-02-23 23:17   ` [bug#46728] [PATCH 4/7] gnu: Add s2n Greg Hogan
2021-02-24 16:34     ` Leo Famulari
2021-02-25 14:19       ` Greg Hogan
2021-03-02 19:37         ` Ludovic Courtès [this message]
2021-03-02 20:13           ` [bug#46728] [PATCH 0/7] gnu: aws-sdk-cpp: Update to 1.8.148 Greg Hogan
2021-03-08 13:49             ` Ludovic Courtès
2021-03-11 21:37               ` Greg Hogan
2021-03-12 23:01                 ` bug#46728: " Ludovic Courtès
2021-02-23 23:18   ` [bug#46728] [PATCH 5/7] gnu: Add aws-c-io Greg Hogan
2021-02-23 23:18   ` [bug#46728] [PATCH 6/7] gnu: aws-c-event-stream: Update to 0.2.6 Greg Hogan
2021-02-23 23:19   ` [bug#46728] [PATCH 7/7] gnu: aws-sdk-cpp: Update to 1.8.148 Greg Hogan

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=878s75uz1n.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=46728@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.