Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,

2006, 2007, 2008, 2009 Free Software Foundation, Inc.

   Copying and distribution of this file, with or without modification,

are permitted in any medium without royalty provided the copyright

notice and this notice are preserved.  This file is offered as-is,

without warranty of any kind.

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

configure, build, and install this package.  The following

more-detailed instructions are generic; see the `README' file for

instructions specific to this package.  Some packages provide this

`INSTALL' file but do not implement all of the features documented

below.  The lack of an optional feature in a given package is not

necessarily a bug.  More recommendations for GNU packages can be found

in *note Makefile Conventions: (standards)Makefile Conventions.

the results of its tests to speed up reconfiguring.  Caching is

cache files.

`configure' by a program called `autoconf'.  You need `configure.ac' if

you want to change it or regenerate `configure' using a newer version

of `autoconf'.

   The simplest way to compile this package is:

     `./configure' to configure the package for your system.

     Running `configure' might take a while.  While running, it prints

     some messages telling which features it is checking for.

     the package, generally using the just-built uninstalled binaries.

     documentation.  When installing into a prefix owned by root, it is

     recommended that the package be configured and built as a regular

     user, and only the `make install' phase executed with root

     privileges.

  5. Optionally, type `make installcheck' to repeat any self-tests, but

     this time using the binaries in their final installed location.

     This target does not install anything.  Running this target as a

     regular user, particularly if the prior `make install' required

     root privileges, verifies that the installation completed

     correctly.

  6. You can remove the program binaries and object files from the

  7. Often, you can also type `make uninstall' to remove the installed

     files again.  In practice, not all packages have tested that

     uninstallation works correctly, even though it is required by the

     GNU Coding Standards.

  8. Some packages, particularly those that use Automake, provide `make

     distcheck', which can by used by developers to test that all other

     targets like `make install' and `make uninstall' work correctly.

     This target is generally not run by end users.

   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.

     ./configure CC=c99 CFLAGS=-g LIBS=-lposix

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

own directory.  To do this, you can use GNU `make'.  `cd' to the

source code in the directory that `configure' is in and in `..'.  This

is known as a "VPATH" build.

   With a non-GNU `make', it is safer to compile the package for one

architecture at a time in the source code directory.  After you have

installed the package for one architecture, use `make distclean' before

reconfiguring for another architecture.

   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

`configure' the option `--prefix=PREFIX', where PREFIX must be an

absolute file name.

you can set and what kinds of files go in them.  In general, the

default for these options is expressed in terms of `${prefix}', so that

specifying just `--prefix' will affect all of the other directory

specifications that were not explicitly provided.

   The most portable way to affect installation locations is to pass the

correct locations to `configure'; however, many packages provide one or

both of the following shortcuts of passing variable assignments to the

`make install' command line to change installation locations without

having to reconfigure or recompile.

   The first method involves providing an override variable for each

affected directory.  For example, `make install

prefix=/alternate/directory' will choose an alternate location for all

directory configuration variables that were expressed in terms of

`${prefix}'.  Any directories that were specified during `configure',

but not in terms of `${prefix}', must each be overridden at install

time for the entire installation to be relocated.  The approach of

makefile variable overrides for each directory variable is required by

the GNU Coding Standards, and ideally causes no recompilation.

However, some platforms have known limitations with the semantics of

shared libraries that end up requiring recompilation when using this

method, particularly noticeable in packages that use GNU Libtool.

   The second method involves providing the `DESTDIR' variable.  For

example, `make install DESTDIR=/alternate/directory' will prepend

`/alternate/directory' before all installation names.  The approach of

`DESTDIR' overrides is not required by the GNU Coding Standards, and

does not work on platforms that have drive letters.  On the other hand,

it does better at avoiding recompilation issues, and works well even

when some directory options were not specified in terms of `${prefix}'

at `configure' time.

Optional Features

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

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

   Some packages offer the ability to configure how verbose the

execution of `make' will be.  For these packages, running `./configure

--enable-silent-rules' sets the default to minimal output, which can be

overridden with `make V=1'; while running `./configure

--disable-silent-rules' sets the default to verbose, which can be

overridden with `make V=0'.

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 -D_XOPEN_SOURCE=500"

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"

   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This

directory contains several dysfunctional programs; working variants of

these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'

in your `PATH', put it _after_ `/usr/bin'.

   On Haiku, software installed for all users goes in `/boot/common',

not `/usr/local'.  It is recommended to use the following options:

     ./configure --prefix=/boot/common

   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

     OS

     KERNEL-OS

   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

overridden in the site shell script).

Unfortunately, this technique does not work for `CONFIG_SHELL' due to

an Autoconf bug.  Until the bug is fixed you can use this workaround:

     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash

   `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.

	src/server/slave.c \

	src/server/simpleslave.c

/* simpleSlave functions */

/** Memory struct for curl */

struct _web_memorystruct {

  char *memory;

  size_t size;

};

static void *_web_myrealloc(void *ptr, size_t size);

static void *_web_myrealloc(void *ptr, size_t size)

{

  /* There might be a realloc() out there that doesn't like reallocing

     NULL pointers, so we take care of it here */

  if(ptr)

    return realloc(ptr, size);

  else

    return malloc(size);

}

static size_t _web_writememorycallback(void *ptr, size_t size, size_t nmemb, void *data)

{

  size_t realsize = size * nmemb;

  struct _web_memorystruct *mem = (struct _web_memorystruct *)data;

  mem->memory = _web_myrealloc(mem->memory, mem->size + realsize + 1);

  if (mem->memory) {

    memcpy(&(mem->memory[mem->size]), ptr, realsize);

    mem->size += realsize;

    mem->memory[mem->size] = 0;

  }

  return realsize;

}

struct _web_memorystruct _web_getrequest(char *url){

  fprintf(stderr,"Preparing to get request at %s",url);

  CURL *curl;

  CURLcode res;

  struct _web_memorystruct chunk;

  chunk.memory=NULL; /* we expect realloc(NULL, size) to work */

  chunk.size = 0;    /* no data at this point */

  curl = curl_easy_init();

  if(curl) {

    curl_easy_setopt(curl, CURLOPT_URL, url);

    curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, _web_writememorycallback);

    curl_easy_setopt(curl, CURLOPT_WRITEDATA, (void *)&chunk);

    curl_easy_setopt(curl, CURLOPT_USERAGENT, "libcurl-agent/1.0");

    res = curl_easy_perform(curl);

    curl_easy_cleanup(curl);

  }

  /* we're done with libcurl, so clean it up */

  curl_global_cleanup();

  return chunk; // 0 is OK, 1 is 404 or other error

}

void _web_finishframe(int slavekey, char *slavepass, int jobnum, int framenum){

  char *url;

  _distren_asprintf(&url,"http://dev.distren.org/slave/act.php?mode=finishframe&slavekey=%d&slavepass=%s&jobnum=%d&framenum=%d", slavekey, slavepass, jobnum, framenum);

  struct _web_memorystruct data = _web_getrequest(url);

  if(data.memory)

    free(data.memory);

}

void _web_startframe(int slavekey, char *slavepass, int jobnum, int framenum){

}

void _web_getwork(int slavekey, char *slavepass, int *jobnum, int *framenum){

}

void _web_setrenderpower(int slavekey, char *slavepass, int jobnum, int framenum){

}

/* Simple slave */

struct _web_memorystruct;

static void *_web_myrealloc(void *ptr, size_t size);

static size_t _web_writememorycallback(void *ptr, size_t size, size_t nmemb, void *data);

struct _web_memorystruct _web_getrequest(char *url);

void _web_finishframe(int slavekey, char *slavepass, int jobnum, int framenum);

void _web_startframe(int slavekey, char *slavepass, int jobnum, int framenum);

void _web_getwork(int slavekey, char *slavepass, int *jobnum, int *framenum);

void _web_setrenderpower(int slavekey, char *slavepass, int jobnum, int framenum);