[tahoe-dev] Fwd: that problem with comparing types across DLLs
Zooko Wilcox-O'Hearn
zooko at zooko.com
Tue May 26 13:27:03 UTC 2009
Thanks, Wei Dai. I'll ask the Debian and Fedora packaging experts
what they think.
Here is the list of files included in the libcrypto++-dev package in
Debian stable:
http://packages.debian.org/lenny/amd64/libcrypto++-dev/filelist
It does include libcryptopp.a. I'll try linking against that.
Dear Debian and Fedora packaging experts: please see Wei Dai's
message below. He is the author of Crypto++.
Does anyone know how to specify that the "-lcryptopp" on your g++
command line should use the static lib in preference to the dynamic one?
Regards,
Zooko
Begin forwarded message:
> From: "Wei Dai" <weidai at weidai.com>
> Date: May 26, 2009 5:22:37 AM MDT
> To: "Zooko Wilcox-O'Hearn" <zooko at zooko.com>
> Cc: "Crypto++ Users" <cryptopp-users at googlegroups.com>
> Subject: Re: that problem with comparing types across DLLs
>
> Zooko, do Debian and Fedora include Crypto++ in static library form
> (.a file) in addition to shared library (.so) form? If so, can you
> link to it instead? If not, can we petition for them to include it?
>
> Unfortunately I have little knowledge of how shared libraries work
> on Linux/Mac. Crypto++ includes many cryptographic algorithms, and
> any application will only use a fraction of them. A static library
> seems to make more sense as it allows the linker to discard the
> unused code. I didn't originally intend to support Crypto++ as a
> shared library, and that's why the makefile doesn't include an
> option to compile to shared library. (Crypto++ is supported as a
> Windows DLL, but that was forced on me by a FIPS requirement to
> have clear "cryptographic boundaries".)
>
> Maybe there is a case to be made for supporting Crypto++ as a
> shared library, but I haven't heard it yet. The distributions that
> included Crypto++ as a shared library did so without consulting me...
>
> --------------------------------------------------
> From: "Zooko Wilcox-O'Hearn" <zooko at zooko.com>
> Sent: Sunday, May 24, 2009 4:31 PM
> To: "Wei Dai" <weidai at weidai.com>
> Cc: "Crypto++ Users" <cryptopp-users at googlegroups.com>
> Subject: Re: that problem with comparing types across DLLs
>
>>
>> On May 24, 2009, at 9:29 AM, Wei Dai wrote:
>>
>>> Zooko, have you tried asking for advice on other mailing lists?
>>
>> Okay, some googling about showed me a mailing list that is likely to
>> help -- the Python cplusplus-sig list. Here is my summary of the
>> problem and the four possible solutions that I can think of:
>>
>> http://mail.python.org/pipermail/cplusplus-sig/2009-May/014531.html
>>
>> Please read it yourself in case doing so provides some flash of
>> insight that you can share with me.
>>
>> Thank you,
>>
>> Zooko
>> ---
>> Tahoe, the Least-Authority Filesystem -- http://allmydata.org
>> store your data: $10/month -- http://allmydata.com/?tracking=zsig
>> I am available for work -- http://zooko.com/résumé.html
>> --~--~---------~--~----~------------~-------~--~----~
>> You received this message because you are subscribed to the "Crypto
>> ++ Users" Google Group.
>> To unsubscribe, send an email to cryptopp-users-
>> unsubscribe at googlegroups.com.
>> More information about Crypto++ and this group is available at
>> http://www.cryptopp.com.
>> -~----------~----~----~----~------~----~------~--~---
>>
More information about the tahoe-dev
mailing list