From: Efraim Flashner <efraim@flashner.co.il>
To: Hamzeh Nasajpour <h.nasajpour@pantherx.org>
Cc: SuarezMiguelC via <help-guix@gnu.org>
Subject: Re: Why the static library will delete after the package installation of dlib?
Date: Thu, 13 Aug 2020 11:27:45 +0300 [thread overview]
Message-ID: <20200813082745.GA1228@E5400> (raw)
In-Reply-To: <2491a28a-543d-475f-a6bc-1112c92ffe45@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Wed, Aug 12, 2020 at 05:48:29PM +0430, Hamzeh Nasajpour wrote:
> Hi,
>
> I'm using `dlib` in a project and I found that the static library will be deleted in the `delete-static-library` phase in the package installation. Why?
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/machine-learning.scm#n814
>
> Is there any problem to comment these lines for using the `dlib` as library? (line 814 - 817)
>
> Regards,
> Hamzeh
We normally try to delete the static library so the shared library is
available and overall the package takes less space. I see, however, that
dlib defaults to static and doesn't build both by default, leaving out
package without any library installed.
This should be fixed shortly, with a shared library now in the lib
directory.
--
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 --]
prev parent reply other threads:[~2020-08-13 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 13:18 Why the static library will delete after the package installation of dlib? Hamzeh Nasajpour
2020-08-13 8:27 ` Efraim Flashner [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
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=20200813082745.GA1228@E5400 \
--to=efraim@flashner.co.il \
--cc=h.nasajpour@pantherx.org \
--cc=help-guix@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.
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).