Ahh.

I think you'll just have to deal with detecting the library in your
configure or other script. Almost all libraries work the way crypto++
does so it isn't something out of the ordinary. It should be pretty
easy to do if you used cmake with the find_library call.

Chris


On Sun, Nov 9, 2008 at 12:53 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Basically, I'd like it to behave like a header-only library. I've
> successfully done this with other libraries that were meant to be
> precompiled, such as the Boost.Filesystem library. I'd like it this
> way so that I can make it as easy as possible for people to compile my
> project themselves -- one build step and they're done.
>
> On Nov 9, 12:41 am, Chris Morgan <[EMAIL PROTECTED]> wrote:
>> On Nov 9, 2008, at 12:26 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]
>>
>>  > wrote:
>>
>> > Hi,
>>
>> > I'm writing a program that requires hashing and public key encryption/
>> > decryption/signing. Crypto++ seems like a good choice, but I would
>> > prefer having all my libraries compile at once for simplicity's sake,
>> > so all I have to do is add them to my project and #include them. Is
>> > this possible with Crypto++? Doing so seems to lead to a failed build.
>>
>> What does "compile them all at once mean"? With a library like crypto+
>> + you'll want to build it and link to either it's shared or static
>> library. I'm not sure if a static library is built by default or
>> supported in the makefile but it's a pretty east change to add the
>> static library target.
>>
>> If you are asking to include some header files and then compile
>> your .c/.cpp files along with the crypto++ .cpp files that's a lot
>> more complex than just linking against the library.
>>
>> Chris
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [EMAIL PROTECTED]
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

Reply via email to