make error

[xuzhw]

How can I sovle this problem?
CXX=g++ version 4.73
boost version 1.43

[mavam]

In the file hash.cc at the very top, could you try including <stdexcept> and see if this helps?

#include <cassert>
#include <stdexcept>   // Bring in exception definitions.

If so, I'll push that fix out.

[xuzhw]

There are some other errors. I tried to solve them by updating my libboost to 1.53, and then make succeed,
But there is an errror when I run a test programme after I installed the libbf.

the src code of the test programme is as following:

Actually, This is the example programme in the Synopsis.
Maybe I made a mistake in using the libbf?
But how to use this lib exactly?

[mavam]

I'm missing a bit of context to assess the problem. Could you tell me what OS and compiler you are using? (The Boost dependency is only necessary for unit testing, 1.53 should suffice). What command line do you use for compiling your code?

Based on the error message, it looks like you forgot to link libbf into your application. Make sure you have -L /path/to/libbf/prefix as part of your compiler options and -lbf after your source, .e.g:

c++ -I /opt/libbf/include -L /opt/libbf/lib test.cc -lbf

To use libbf, you would typically include it the header file bf.h in your application and then start using the provided data structures.

Also, could you confirm that the include fix I proposed solved your initial problem?

[xuzhw]

well, my os version is ubuntu13.10, and the compiler I used here is g++4.73
the command line is as following:g++ testbf.cc -o testbf.out -std=c++11
I have make install before I run the command above.

I have trid to add link into the command as your reply.
But there are still some errors here.

I checked the path, the lib file is already placed there, there is no problem, well now I am confused.

[mavam]

It seems the compilation succeeded now. (Note: it's common to put no compiler flags after the linker flags, so I recommend to move the flag -std=c++11 to the beginning, right after g++).

At this point you need to make sure that your library path is set up properly. Because you installed libbf in a non-standard system location, you need to either add /usr/local/lib to your library search path, or what most folks do during testing, just export the environment variable LD_LIBRARY_PATH:

export LD_LIBRARY_PATH=/usr/local/lib
./bftest.out

[xuzhw]

Great!,the test passed. Thanks a lot,Matthias.
Well, I still have a question here, why must I add the link param into the compile command here?
I have include the bf.h and used the bf namespace in the test programme.
When I ref a lib, it is usually the only thing I must do to include the head file into the code.

[mavam]

Good to hear it works now!

Because libbf is not a header-only component but also ships with compiled code in the form of library, you need to do both: include the header and link the library to the object code from your own application. By separating the API from the implementation, I have more freedom in terms of the implementation.

In the future, I do plan to make it again a header-only library. It has such a small footprint that this would indeed be a relief from the usability perspective. Since the library does not rely on any other external dependencies, I don't see the need to hide dependencies in the implementation.