Difference between revisions of "Talk:CryptoppDebian"
From AMule Project FAQ
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
I don't see the point on compiling Crypto++ through Debian sources. It would be better to have directly the binnaries installed IMHO. If there's some point in compiling sources first I'd appreciate the comment. Otherwise, I'll edit the page with the epropiate lines to install directly the binnaries and fix them with the sym-link. | I don't see the point on compiling Crypto++ through Debian sources. It would be better to have directly the binnaries installed IMHO. If there's some point in compiling sources first I'd appreciate the comment. Otherwise, I'll edit the page with the epropiate lines to install directly the binnaries and fix them with the sym-link. | ||
+ | |||
+ | '''Done.''' | ||
+ | |||
+ | Is there any point to this at all anymore, now that amule has crypto embedded? Even when I install the crypto libs on Debian amule doesn't use them. Is there any advantage to compiling with --disable-embedded-crypto? | ||
+ | |||
+ | '''Not anymore. It is still possible to use non-embedded crypto++ for compatibility on some systems, but not necessary on 99.9% systems anyway. If it works, just use embedded ;)''' |
Latest revision as of 18:19, 4 August 2005
I don't see the point on compiling Crypto++ through Debian sources. It would be better to have directly the binnaries installed IMHO. If there's some point in compiling sources first I'd appreciate the comment. Otherwise, I'll edit the page with the epropiate lines to install directly the binnaries and fix them with the sym-link.
Done.
Is there any point to this at all anymore, now that amule has crypto embedded? Even when I install the crypto libs on Debian amule doesn't use them. Is there any advantage to compiling with --disable-embedded-crypto?
Not anymore. It is still possible to use non-embedded crypto++ for compatibility on some systems, but not necessary on 99.9% systems anyway. If it works, just use embedded ;)