DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] static libraries
Date: Sat, 05 Jan 2013 12:05:37 +0100	[thread overview]
Message-ID: <50E80901.5040103@gmail.com> (raw)
In-Reply-To: <CAFnMBaQjOgP0aHoV4EdqP85+jfY8Ep68fJETdTunvVd6je84zw@mail.gmail.com>

On 01/05/2013 10:05 AM, .. ink .. wrote:
> i build 1.6.0-rc1 with the following config options:
> 
>  ./configure --prefix=/usr --enable-cryptsetup-reencrypt --enable-static-cryptsetup
> 
> then i looked at the static libraries with the following command:
>  find . -iname *.a
> 
> and the results where:
> ./lib/crypto_backend/.libs/libcrypto_backend.a
> ./lib/verity/.libs/libverity.a
> ./lib/tcrypt/.libs/libtcrypt.a
> ./lib/luks1/.libs/libluks1.a
> ./lib/loopaes/.libs/libloopaes.a
> 
> Is the list of static objects complete? it seem incomplete to me as i dont see a static object to handle plain volumes or other functions.

What are you trying to do here?

These are INTERNAL libraries, never ever use them directly.

> Shouldnt also there be a libcryptsetup.a static library?

$ ls -l lib/.libs/libcryptsetup.a 
-rw-r--r-- 1 milan milan 567052 Jan  5 11:57 lib/.libs/libcryptsetup.a

This is the only library which is provided externally.

Above compiled with (on Debian)
./configure --enable-static --enable-static-cryptsetup

Milan

  reply	other threads:[~2013-01-05 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05  9:05 [dm-crypt] static libraries .. ink ..
2013-01-05 11:05 ` Milan Broz [this message]
2013-01-05 12:12   ` .. ink ..
2013-01-05 17:56     ` Milan Broz
2013-01-05 22:15       ` .. ink ..
2013-01-05 22:48         ` .. ink ..
2013-01-06 10:21         ` Milan Broz
2013-01-06 10:50           ` .. ink ..

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=50E80901.5040103@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=mhogomchungu@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox