all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 28190-done@debbugs.gnu.org
Subject: bug#28190: [PATCH] gnu: Build the shared library for yaml-cpp.
Date: Wed, 23 Aug 2017 10:10:11 +0100	[thread overview]
Message-ID: <20170823101011.21ef8165@cbaines.net> (raw)
In-Reply-To: <87h8wz2trl.fsf@fastmail.com>

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

On Tue, 22 Aug 2017 23:10:38 +0200
Marius Bakke <mbakke@fastmail.com> wrote:

> Christopher Baines <mail@cbaines.net> writes:
> 
> > On Tue, 22 Aug 2017 22:58:34 +0200
> > Marius Bakke <mbakke@fastmail.com> wrote:
> >  
> >> Christopher Baines <mail@cbaines.net> writes:
> >>   
> >> > * gnu/packages/serialization.scm (yaml-cpp)[arguments]: Add
> >> >   -DBUILD_SHARED_LIBS=ON to #:configure-flags.    
> >> 
> >> Does this disable building the static library too?  If not, should
> >> we do that while at it?  LGTM, anyway.  
> >
> > I'm not quite sure, but I think so, these are the files in lib now,
> > and the .a file that was there before has disappeared.
> >
> > └── lib
> >     ├── libyaml-cpp.so -> libyaml-cpp.so.0.5
> >     ├── libyaml-cpp.so.0.5 -> libyaml-cpp.so.0.5.3
> >     ├── libyaml-cpp.so.0.5.3
> >     └── pkgconfig
> >         └── yaml-cpp.pc  
> 
> Great!  Static libraries cannot be reliably grafted, so it's good to
> avoid them when we can.  Thanks!

I've pushed this now, thanks for your review Marius :)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2017-08-23  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 20:36 [bug#28190] [PATCH] gnu: Build the shared library for yaml-cpp Christopher Baines
2017-08-22 20:58 ` Marius Bakke
2017-08-22 21:00   ` Christopher Baines
2017-08-22 21:10     ` Marius Bakke
2017-08-23  9:10       ` Christopher Baines [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=20170823101011.21ef8165@cbaines.net \
    --to=mail@cbaines.net \
    --cc=28190-done@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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.