There are a number of FCGX_ routines, declared in "fcgiapp.h", which may be 
useful.  I've used them in a project where recompiling all sources was not 
possible (other code distributed as binary shared library).

Not sure how easy to integrate into Fossil, but as I recall Fossil has at least 
some of its own output routines (for formatting HTML output, etc) so might not 
be too tough.

On Aug 13, 2013, at 11:39 AM, Stephan Beal <sgb...@googlemail.com> wrote:

> On Sun, Aug 11, 2013 at 6:25 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> - FastCGI replaces read() and write() with its own "drop-in" replacements, so 
> all code has to be compiled using them. However, they got the signature wrong 
> on the write() routine. They take a non-const (void*) for the src argument), 
> meaning that no compliant code can compile against it.
> 
> i had to prove to myself that my memory was correct there:
> 
> http://www.fastcgi.com/devkit/include/fcgi_stdio.h
> DLLAPI size_t     FCGI_fread(void *ptr, size_t size, size_t nmemb, FCGI_FILE 
> *fp);
> DLLAPI size_t     FCGI_fwrite(void *ptr, size_t size, size_t nmemb, FCGI_FILE 
> *fp);
> that (brain-dead) non-const first pointer to their fwrite() replacement 
> requires a cast in all fwrite()-using code. They macro-alias fwrite() to 
> FCGI_fwrite() (which is how they offer drop-in support).
> 
> -- 
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to