[Bf-committers] ./configure : I can help, python includes

[JLM aka cityhunter]

hello everybody
I'm currently creating an autoconf like tool that intends to be easier 
to maintain than the autotools stuff while still beeing powerfull/ posix 
portable
the tool is available at http://confiserie.berlios.de/
and I can create easely the tests  for blender if you provide me some 
information / c files
the c file solution is the best but I can create the tests easely 
without....

I need to know :
what packages are mandatory
what packages are optionals
how to test a package (what .h to include, if a version need to be 
tested, where to find the tested information, the library to link with)
what tools are used to create the package
what tools are optional (used if present at runtime)

if you can provide me a .c for the headers/function testing, this file 
don't need to be runnable but only compilable ie should fail to compile 
if a header is missing, if a c-pre-processor feature can't be tested (a 
#define version XXXX) or if a library is missing, for this it should 
only syntaxily correct....

an exemple is included


I just then want to report that my python includes are in 
/usr/include/python2.4/
so include "python.h" or include <python.h> will fail

-------------- next part --------------
//run me with CPPFLAGS="$CPPFLAGS -DTESTVERSION -DVERSION_TO_TEST=0xsomething"
//if you want to test openssl version
//by making the following test in your confiserie script :
//if $confiserie/test_compile_c.sh $confiserie/test_openssl.c; then
//....
//fi
//
//or 
//
//$confiserie/test_openssl.sh 0xsomething

#include <openssl/opensslv.h>
#include <openssl/ssl.h>

#ifdef TESTVERSION
#if VERSION_TO_TEST < OPENSSL_VERSION_NUMBER
#error openssl version is too old
#endif
#endif

void main()
{
	SSL myctx;
	char buff[25];
	SSL_write(&myctx, buff, 25);
}