DistRen Changeset - e890b5f3ec9f · protofusion repositories

Changeset - e890b5f3ec9f

Parent rev.

Child rev.

[Not reviewed]

default

0 2 0

ethanzonca@localhost.localdomain - 16 years ago 2009-06-30 19:04:32
ethanzonca@localhost.localdomain

Added execioishness

2 files changed with 101 insertions and 21 deletions:

INSTALL

src/server/distrend.c

0 comments (0 inline, 0 general)

INSTALL

➞

Show inline comments

 Installation Instructions
 *************************
 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
 , 2007 Free Software Foundation, Inc.
+, 2007, 2008 Free Software Foundation, Inc.
 This file is free documentation; the Free Software Foundation gives
+   This file is free documentation; the Free Software Foundation gives
 unlimited permission to copy, distribute and modify it.
 Basic Installation
 ==================
 Briefly, the shell commands `./configure; make; make install' should
+   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.
    The `configure' shell script attempts to guess correct values for
 various system-dependent variables used during compilation.  It uses
@@ @@ -70,43 +70,57 @@ The simplest way to compile this package @@
 . Often, you can also type `make uninstall' to remove the installed
      files again.
 Compilers and Options
 =====================
 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.
    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 give `configure' initial values for configuration parameters
 by setting variables in the command line or in the environment.  Here
 is an example:
      ./configure CC=c99 CFLAGS=-g LIBS=-lposix
    *Note Defining Variables::, for more details.
 Compiling For Multiple Architectures
 ====================================
 You can compile the package for more than one kind of computer at the
+   You can compile the package for more than one kind of computer at the
 same time, by placing the object files for each architecture in their
 own directory.  To do this, you can use GNU `make'.  `cd' to the
 directory where you want the object files and executables to go and run
 the `configure' script.  `configure' automatically checks for the
 source code in the directory that `configure' is in and in `..'.
    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.
 Installation Names
 ==================
 By default, `make install' installs the package's commands under
+   By default, `make install' installs the package's commands under
 `/usr/local/bin', include files under `/usr/local/include', etc.  You
 can specify an installation prefix other than `/usr/local' by giving
 `configure' the option `--prefix=PREFIX'.
    You can specify separate installation prefixes for
 architecture-specific files and architecture-independent files.  If you
@@ @@ -123,32 +137,54 @@ you can set and what kinds of files go i @@
 with an extra prefix or suffix on their names by giving `configure' the
 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
 Optional Features
 =================
 Some packages pay attention to `--enable-FEATURE' options to
+   Some packages pay attention to `--enable-FEATURE' options to
 `configure', where FEATURE indicates an optional part of the package.
 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
 is something like `gnu-as' or `x' (for the X Window System).  The
 `README' should mention any `--enable-' and `--with-' options that the
 package recognizes.
    For packages that use the X Window System, `configure' can usually
 find the X include and library files automatically, but if it doesn't,
 you can use the `configure' options `--x-includes=DIR' and
 `--x-libraries=DIR' to specify their locations.
 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"
 Specifying the System Type
 ==========================
 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
    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
 `--build=TYPE' option.  TYPE can either be a short name for the system
 type, such as `sun4', or a canonical name which has the form:
      CPU-COMPANY-SYSTEM
 where SYSTEM can have one of these forms:
@@ @@ -168,24 +204,24 @@ platform different from the build platfo @@
 "host" platform (i.e., that on which the generated programs will
 eventually be run) with `--host=TYPE'.
 Sharing Defaults
 ================
 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'.
    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'.
 `configure' looks for `PREFIX/share/config.site' if it exists, then
 `PREFIX/etc/config.site' if it exists.  Or, you can set the
 `CONFIG_SITE' environment variable to the location of the site script.
 A warning: not all `configure' scripts look for a site script.
 Defining Variables
 ==================
 Variables not defined in a site shell script can be set in the
+   Variables not defined in a site shell script can be set in the
 environment passed to `configure'.  However, some packages may run
 configure again during the build, and the customized values of these
 variables may be lost.  In order to avoid this problem, you should set
 them in the `configure' command line, using `VAR=value'.  For example:
      ./configure CC=/usr/local2/bin/gcc
@@ @@ -198,17 +234,25 @@ an Autoconf bug. Until the bug is fixed @@
      CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
 `configure' Invocation
 ======================
 `configure' recognizes the following options to control how it operates.
    `configure' recognizes the following options to control how it
 operates.
 `--help'
 `-h'
      Print a summary of the options to `configure', and exit.
      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.
 `--version'
 `-V'
      Print the version of Autoconf used to generate the `configure'
      script, and exit.
@@ @@ -229,9 +273,19 @@ an Autoconf bug. Until the bug is fixed @@
      messages will still be shown).
 `--srcdir=DIR'
      Look for the package's source code in directory DIR.  Usually
      `configure' can determine that directory automatically.
 `--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.
 `configure' also accepts some other, not widely useful, options.  Run
 `configure --help' for more details.

src/server/distrend.c

➞

Show inline comments

@@ @@ -24,12 +24,15 @@ @@
  * ++ Make data availible for other apps to parse
  * Server<==>Client Communication
  * Upload while rendering
  */
 #include <stdio.h>
 #include "execio.h"
 #include "options.h"
 #define max 100
  // maximum number of stored jobs in memory, per job type (lux/blend). Eventually we can dump this data to disk, or atleast the remainder not in memory...
 int jobnum = 0;
 // Structures for storing job information
 struct {
@@ @@ -91,13 +94,36 @@ void queue(int type, char *name, char *s @@
   else{
     // Throw error.
+  }
 jobnum++;
+}
 // Mostly kinda copied from old code, but I understand it a tad better now :)
 char buf[10];
 struct execio *testrem;
 char *execargv[] =
+  {
 "ssh",
 "ethanzonca@protofusion.org",
 "sh",
 "-c",
 "\"echo hello from ${HOSTNAME}\"",
 (char *)NULL
  };
 size_t readlen;
 fprintf(stderr, "execio_open:", execio_open(&testrem, "ssh", execargv));
 buf[9] = '\0'; // null-terminating the array...
 while(!execio_read(testrem, buf, 9, &readlen)) // What's with the readlen stuff?
+  {
     if(readlen > 9) {
       fprintf(stderr, "Something is terribly wrong!\n");
+    }
    buf[readlen] = '\0'; // Null-terminating the end of it again based on how large the data is?
    fprintf(stderr, "read \"&s\"\n", buf);
+  }
 execio_close(testrem);
 ///////////////////////// SLAVE ///////////////////////////////
 /*
 Slave listens on server for a command in the format of each function...
 We need if's for returns... ==> watchdog

0 comments (0 inline, 0 general)