all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel@gnu.org
Subject: Re: Building a library as both static and dynamic
Date: Tue, 29 Sep 2020 08:09:31 +0300	[thread overview]
Message-ID: <20200929050931.GE1386@E5400> (raw)
In-Reply-To: <5F6328DA-112E-45F9-B6F0-2132E43A6BB0@greghogan.com>

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

On Sun, Sep 27, 2020 at 07:57:19AM -0400, Greg Hogan wrote:
> Is there a best practice or example for building a library twice, both static and dynamic? I submitted patch #43620, and in working on another library have the same issue. These are cmake builds with a parameter declaration for either a static or dynamic build, not both. I would like to create a single package with both “out” and “static” outputs, which looks to be standard across Guix.
> 
> One idea is to run the configure / make / make install phases twice. modify-phases does not currently support copying phases (though add-after could work with the right function reference from cmake-build) and #:configure-flags would need to be set differently.
> 
> Another option would be to patch the source build files, but this problem feels solvable in Guix without duplicating the code from cmake-build’s configure.
> 
> Thanks,
> Greg

x265 is a package that uses cmake and is built multiple times with
different options and with a separate static output.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-29  5:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 11:57 Building a library as both static and dynamic Greg Hogan
2020-09-29  5:09 ` Efraim Flashner [this message]
2020-10-05 13:39 ` Ludovic Courtès

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=20200929050931.GE1386@E5400 \
    --to=efraim@flashner.co.il \
    --cc=code@greghogan.com \
    --cc=guix-devel@gnu.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.
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.