apt-get install libboost-signals libboost-signals-devIf that works, you can skip to step 2. You may find that you need to install the whole of the Boost package, depending on how your distribution has it packaged. If you don't have a package manager, you can always compile it from source:
Download boost, following the instructions here, under "Get Boost":
http://www.boost.org/more/getting_started/unix-variants.htmlYou should get a file like boost_1_34_1.tar.bz2 - install it like this (as root):
tar jxf boost_1_34_1.tar.bz2 cd boost_1_34_1 ./configure --prefix=/usr make make install
tar zxf libircpp-0.1.tar.gz cd libircpp-0.1 ./configure --prefix=/usr make make install
gcc -o helloworld -lircpp -lboost_signals helloworld.cppThis will compile helloworld.cpp into an executable "helloworld". The -lircpp and -lboost_signals options tell the compiler to link with the two libraries: libircpp, and boost_signals.
Run it by typing ./helloworld - you should be able to see it join the channel you specified in helloworld.cpp, and say hello, like this:
libircpp (~libircpp@1.2.3.4) has joined #mychannel <libircpp> Hello world!When you're done, press Ctrl-C to kill it.
Compiling statically means that the libraries are built into the executable. This means that the executable is larger, but will run anywhere - it is "standalone". To compile statically, do:
g++ -o helloworld helloworld.cpp /usr/lib/libircpp.a /usr/lib/libboost_signals.a(Change the paths to the libraries if you have installed them somewhere other than /usr/lib). Compiling statically also provides a way of compiling if you do not have root access to install the libraries. You can compile both Boost Signals and libircpp, and copy the respective .a files into your working directory (you can find libircpp.a in libircpp/.libs/ and the libboost_signals.a in a similar place in the boost compilation directory). Then just include them in your build as if they were source files:
g++ -o helloworld helloworld.cpp libircpp.a libboost_signals.aNext: Signals