Re: [cgi-devel] compile and build fastcgi

[Darren G. <lis...@gm...>]

Hi Josep,

On 28 December 2010 00:34, Josep M. <jm...@gm...> wrote:

> Hi,
>
> I found the FastCGI lib and I was quite impressed by the asyn I/O
> capabilities so I decided to give it a try. However, I was unable to
> build the library or compile any of the examples. Unfortunately there
> wasn't info at:
>
> http://cgi.sourceforge.net/docs/fastcgi___cgi/tutorial/running.html
>

The library is header-only by default so you only need to include the
headers you need. Probably:

#include <boost/cgi/cgi.hpp>
#include <boost/cgi/fcgi.hpp>
#include <boost/cgi/scgi.hpp>

There is installation instructions, as much as you need them at:

<http://cgi.sourceforge.net/docs/fastcgi___cgi/tutorial/running.html>
http://cgi.sourceforge.net/docs/fastcgi___cgi/tutorial/installation.html

After downloading and unpacking cgi-0.7.1, I get:
>
> boost/
> libs/
> README.txt
> project-root.jam
>
> Never seen jam before, but it looks like an ant-like builder... after
> install bjam (apt-get install bjam) I can only get to:
>
> Unable to load Boost.Build: could not find "boost-build.jam"
> ---------------------------------------------------------------
> Attempted search from /home/solso/test/cgi-0.7.1 up to the root
> and in these directories from BOOST_BUILD_PATH and BOOST_ROOT:
> /usr/share/boost-build.
> Please consult the documentation at 'http://www.boost.org'.
>
> I'm sure some of you will be laughing at the moment, but I not able to
> find out which directories I should put in the environment to build
> the library and to
> compile the example I wanted:
>
>
> http://cgi.sourceforge.net/docs/fastcgi___cgi/examples/fastcgi_examples.html#fastcgi___cgi.examples.fastcgi_examples.asynchronous_echo
>

No problem. Boost.Build / bjam are the standard Boost installation tools.

As it stands, as long as you have Boost installed, you can just add the
headers you need, link to Boost.System, Boost.Regex, Boost.Date_time and
Boost.Filesystem and you're off. On Windows that linking should be
automatic. The Jamfile at libs/cgi/build/Jamfile.v2 is provided to set up
the required dependencies. You should be able to grok from that what you
need to pass to your compiler of choice.

If there is enough traction I wouldn't be adverse to providing another type
of installation mechanism.

Cheers,
Darren