2006, 2007, 2008 Free Software Foundation, Inc.

   This file is free documentation; the Free Software Foundation gives

   Briefly, the shell commands `./configure; make; make install' should

   Some systems require unusual options for compilation or linking that

the `configure' script does not know about.  Run `./configure --help'

for details on some of the pertinent environment variables.

   You can compile the package for more than one kind of computer at the

   On MacOS X 10.5 and later systems, you can create libraries and

executables that work on multiple system types--known as "fat" or

"universal" binaries--by specifying multiple `-arch' options to the

compiler but only a single `-arch' option to the preprocessor.  Like

this:

     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \

                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \

                 CPP="gcc -E" CXXCPP="g++ -E"

   This is not guaranteed to produce working output in all cases, you

may have to build one architecture at a time and combine the results

using the `lipo' tool if you have problems.

   By default, `make install' installs the package's commands under

   Some packages pay attention to `--enable-FEATURE' options to

Particular systems

==================

   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU

CC is not installed, it is recommended to use the following options in

order to use an ANSI C compiler:

     ./configure CC="cc -Ae"

and if that doesn't work, install pre-built binaries of GCC for HP-UX.

   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot

parse its `<wchar.h>' header file.  The option `-nodtk' can be used as

a workaround.  If GNU CC is not installed, it is therefore recommended

to try

     ./configure CC="cc"

and if that doesn't work, try

     ./configure CC="cc -nodtk"

   There may be some features `configure' cannot figure out

automatically, but needs to determine by the type of machine the package

will run on.  Usually, assuming the package is built to be run on the

_same_ architectures, `configure' can figure that out, but if it prints

a message saying it cannot guess the machine type, give it the

   If you want to set default values for `configure' scripts to share,

you can create a site shell script called `config.site' that gives

default values for variables like `CC', `cache_file', and `prefix'.

   Variables not defined in a site shell script can be set in the

   `configure' recognizes the following options to control how it

operates.

     Print a summary of all of the options to `configure', and exit.

`--help=short'

`--help=recursive'

     Print a summary of the options unique to this package's

     `configure', and exit.  The `short' variant lists options used

     only in the top level, while the `recursive' variant lists options

     also present in any nested packages.

`--prefix=DIR'

     Use DIR as the installation prefix.  *Note Installation Names::

     for more details, including other options available for fine-tuning

     the installation locations.

`--no-create'

`-n'

     Run the configure checks, but stop before creating any output

     files.

	  /*

	    don't return here because options_init will have an overall

	    options help page

	  */

	/*

	   TODO: is strdup good or bad? what about

	   the idea that all libs should allow plugging different

	   malloc/free implementations in?

	 */

  /*

     give this error after the general arguments parsing so that

     the general help from options_init can have effect

  */

  /* if these following lines fail, it'll be reported as a core dump ;-) */

// !!! Killed for now because I'm doing other randomness !!! //

  // Please find a better way of doing this :( you can't strcat multiple strings.. meh

  // use something like sprintf

  //char *username = cfg_getstr(cfg, "username");

  //char *hostname = cfg_getstr(cfg, "hostname");

  //strcat(username, "@");

  //strcat(username, hostname);

  // SSH's to client machine with the username speficied.

  /*

    char buf[10];

    struct execio *testrem;

    char *execargv[] =

      {

	"ssh",

	"username", //cfg_getstr(cfg, "username") . "@" . cfg_getstr(cfg, "hostname"),

	"-i guest.rsa", //yeaaaah any better ideas?

	"sh",

	"-c",

	"\"echo hello from ${HOSTNAME}\"", // "\"useradd -M -c" strcat( cfg_getstr(cfg, "name") cfg_getstr(cfg, "email")) "-d /home/distren --gid 537" cfg_getstr(cfg, "username") "\"",

	(char *)NULL

      };

    size_t readlen;

    fprintf(stderr, "execio madness is occuring!");

    fprintf(stderr, "execio_open returns %d\n", execio_open(&testrem, "ssh", execargv));

    buf[9] = '\0';

    /*

    while(!execio_read(testrem, buf, 9, &readlen))

      {

	if(readlen > 9 )

	  {

	    fprintf(stderr, "execio_read doesn't set readlen correctly or read() is messed up\n");

	    return 1;

	  }

	buf[readlen] = '\0';

	fprintf(stderr, "read \"%s\"\n", buf);

      }

    execio_close(testrem);

    */

  // Can we prune off some of this code up here^? I'm not exactly sure how execio returns output, but it seems like more could be happening in execio itself, and less happening where it is actually called.

  // We need some code to ssh, and if the SSH fails, tell the user to register.

  // Killed the user reg code, as the php interface will take care of this. Although it should check for users...

  // ------------------------------

  // Ok, this is just to do something to keep distren aliveish... Kill if needed/wanted/meh'd. Borrowed some code from matt's blender.c

// Vars to fill:

    int os=1;

    unsigned int frame_to_render; // initialize this somewhere else...

    frame_to_render = 10; // temporary, the number 10 will be replaced with a function call

    char *filename;

    if(os == 1){char *bin[44] = "blender.exe";}

    else{char *bin[28] = "blender";}   // mac/*nix

    // Placeholders? figure out what the last one is...

    char *format = "%s -b \"%s\" -o %s -f %d -F JPEG -x 1",bin,input,output; /* the format string to pass to sprintf */

     size_t blenderstrlen;

     // This seems pretty ridik. Just sayin'. We gotta switch this up.

     blenderstrlen = strlen(format) - 2 * 2 /* format string minus placeholders */ + strlen(filename) + intstrlen(frame_to_render) + 1 /* NULL terminator */;

     char *blendercmd = malloc(blenderstrlen);

     snprintf(blendercmd, blenderstrlen, format, filename, frame_to_render);

     fprintf(stderr, "will run job num. %s ``%s''\n",jobid,blendercmd);

     free(blendercmd);

  // -------------End cruddy code that will eventually compose blender.c-----------------