ZMQ test

git-svn-id: http://svn.net-core.org/repos/t-engine4@2745 51575b47-30f0-44d4-a5cc-537603b46e54

game/profile-thread/init.lua

@@ -19,10 +19,16 @@
 
 print("TE4Online starting...")
 
-local Client = require "xmpp.Client"
+local Client = require "profile-thread.Client"
+local c = nil
 
-while true do
-	local c = Client.new()
-	local ok, err = pcall(c.run, c)
-	if not ok and err then print("TE4Online error: ", err) end
+function step_profile()
+	if not c then c = Client.new() end
+	local ok, res = pcall(c.step, c)
+	if not ok and res then
+		print("TE4Online error: ", res)
+		c = nil
+		return false
+	end
+	return res
 end

premake4.lua

@@ -43,6 +43,7 @@ solution "TEngine"
 		"src/libtcod_import",
 		"src/physfs",
 		"src/physfs/zlib123",
+		"src/zeromq/include",
 		"/usr/include/SDL",
 		"/usr/include/GL",
 	}
@@ -89,7 +90,7 @@ project "TEngine"
 	language "C"
 	targetname "t-engine"
 	files { "src/*.c", }
-	links { "physfs", "lua".._OPTIONS.lua, "fov", "luasocket", "luaprofiler", "lualanes", "lpeg", "tcodimport", "lxp", "expatstatic", "luamd5" }
+	links { "physfs", "lua".._OPTIONS.lua, "fov", "luasocket", "luaprofiler", "lualanes", "lpeg", "tcodimport", "lxp", "expatstatic", "luamd5", "te4zmq" }
 	defines { "_DEFAULT_VIDEOMODE_FLAGS_='SDL_HWSURFACE|SDL_DOUBLEBUF'" }
 	defines { [[TENGINE_HOME_PATH='".t-engine"']] }
 
@@ -114,7 +115,7 @@ configuration "windows"
 	defines { [[TENGINE_HOME_PATH='"T-Engine"']], 'SELFEXE_WINDOWS' }
 
 configuration "linux"
-	links { "SDL", "SDL_ttf", "SDL_image", "SDL_mixer", "GL", "GLU", "m", "pthread" }
+	links { "SDL", "SDL_ttf", "SDL_image", "SDL_mixer", "GL", "GLU", "m", "pthread", "uuid" }
 	defines { [[TENGINE_HOME_PATH='".t-engine"']], 'SELFEXE_LINUX' }
 
 configuration {"linux", "Debug"}
@@ -266,3 +267,5 @@ project "luamd5"
 	targetname "luamd5"
 
 	files { "src/luamd5/*.c", }
+
+dofile("premake4_zeromq.lua")

src/main.c

@@ -46,6 +46,7 @@
 #define WIDTH 800
 #define HEIGHT 600
 
+void *Z; // ZMQ context
 lua_State *L = NULL;
 int nb_cpus;
 bool no_debug = FALSE;
@@ -786,6 +787,9 @@ void boot_lua(int state, bool rebooting, int argc, char *argv[])
 
 int main(int argc, char *argv[])
 {
+	// Init ZMQ lib
+	Z = zmq_init(1);
+
 	// Get cpu cores
 	nb_cpus = get_number_cpus();
 	printf("[CPU] Detected %d CPUs\n", nb_cpus);

src/main.h

@@ -21,13 +21,17 @@
 #ifndef _MAIN_H_
 #define _MAIN_H_
 
+#include "zmq.h"
+
 extern int resizeWindow(int width, int height);
 extern void do_resize(int w, int h, bool fullscreen);
 extern void setupRealtime(float freq);
 extern void setupDisplayTimer(int fps);
+extern int docall (lua_State *L, int narg, int nret);
 extern bool fbo_active;
 extern bool multitexture_active;
 extern long total_keyframes;
+extern void *Z; // ZMQ context
 
 /* Error handling */
 struct lua_err_type_s {

src/profile.c

@@ -25,11 +25,10 @@
 #include "core_lua.h"
 #include "tSDL.h"
 #include "types.h"
+#include "main.h"
 #include "profile.h"
 #include "lua_externs.h"
 
-extern int docall (lua_State *L, int narg, int nret);
-
 static profile_type *main_profile;
 
 int thread_profile(void *data)
@@ -38,29 +37,42 @@ int thread_profile(void *data)
 	lua_State *L = lua_open();  /* create state */
 	luaL_openlibs(L);  /* open libraries */
 	luaopen_core(L);
+	luaopen_socket_core(L);
+	luaopen_mime_core(L);
 	profile->L = L;
 
+	profile->s_req = zmq_socket(Z, ZMQ_SUB);
+	zmq_connect(profile->s_req, "tcp://te4.org:2257");
+
 	// And run the lua engine pre init scripts
 	if (!luaL_loadfile(L, "/loader/pre-init.lua")) docall(L, 0, 0);
 	else lua_pop(L, 1);
 
 	// Load the profile connector
-	if (!luaL_loadfile(L, "//.lua")) docall(L, 0, 0);
+	if (!luaL_loadfile(L, "/profile-thread/init.lua")) docall(L, 0, 0);
 	else lua_pop(L, 1);
 
+	int request_nbr=0;
 	while (profile->running)
 	{
 		if (!profile->running) break;
 
-		SDL_mutexP(profile->lock);
-		SDL_mutexV(profile->lock);
+		zmq_msg_t reply;
+		zmq_msg_init(&reply);
+		zmq_recv(profile->s_req, &reply, 0);
+		printf("Received reply %d: [%s]\n", request_nbr,
+			(char *) zmq_msg_data (&reply));
+		zmq_msg_close(&reply);
+
+		request_nbr++;
+
+
+//		lua_getglobal(L, "step_profile");
+//		docall(L, 0, 0);
 	}
 
 	// Cleanup
-
 	lua_close(L);
-
-	SDL_DestroyMutex(profile->lock);
 	printf("Cleaned up profile thread\n");
 
 	return(0);
@@ -73,7 +85,6 @@ void create_profile_thread()
 	profile_type *profile = calloc(1, sizeof(profile_type));
 	main_profile = profile;
 
-	profile->lock = SDL_CreateMutex();
 	profile->running = TRUE;
 
 	thread = SDL_CreateThread(thread_profile, profile);

src/profile.h

@@ -24,7 +24,8 @@
 typedef struct {
 	lua_State *L;
 	SDL_Thread *thread;
-	SDL_mutex *lock;
+	void *s_req; // ZMQ request socket
+//	void *s_rep; // ZMQ response socket
 	bool running;
 
 } profile_type;

src/zeromq/AUTHORS

+Contributors
+============
+
+Alexej Lotz <alexej.lotz@arcor.de>
+Asko Kauppi <askok@dnainternet.net>
+Barak Amar <barak.amar@gmail.com>
+Bernd Prager <bernd@prager.ws>
+Bernd Melchers <melchers@ZEDAT.FU-Berlin.DE>
+Brian Buchanan <bwb@holo.org>
+Burak Arslan <burak-github@arskom.com.tr>
+Chia-liang Kao <clkao@clkao.org>
+Chris Wong <chris@chriswongstudio.com>
+Christian Gudrian <christian.gudrian@fluidon.com>
+Conrad D. Steenberg <conrad.steenberg@caltech.edu>
+Dhammika Pathirana <dhammika@gmail.com>
+Dhruva Krishnamurthy <dhruva@ymail.com>
+Dirk O. Kaar <dok@dok-net.net>
+Erich Heine <sophacles@gmail.com>
+Erik Rigtorp <erik@rigtorp.com>
+Frank Denis <zeromq@pureftpd.org>
+George Neill <georgen@neillnet.com>
+Gonzalo Diethelm <gdiethelm@dcv.cl>
+Guido Goldstein <zmq@a-nugget.de>
+Ilja Golshtein <ilejncs@narod.ru>
+Ivo Danihelka <ivo@danihelka.net>
+Jacob Rideout <jacob.rideout@returnpath.net>
+Joe Thornber <joe.thornber@gmail.com>
+Jon Dyte <jon@totient.co.uk>
+Kamil Shakirov <kamils80@gmail.com>
+Marc Rossi <mrossi19@gmail.com>
+Martin Hurton <hurtonm@gmail.com>
+Martin Lucina <mato@kotelna.sk>
+Martin Pales <m.pales@gmail.com>
+Martin Sustrik <sustrik@250bpm.com>
+Matus Hamorsky <mhamorsky@gmail.com>
+Max Wolf <YIDIEPXGXGPN@spammotel.com>
+McClain Looney <m@loonsoft.com>
+Mikael Helbo Kjaer <mhk@designtech.dk>
+Mikko Koppanen <mkoppanen@php.net>
+Nir Soffer <nirsof@gmail.com>
+Pavel Gushcha <pavimus@gmail.com>
+Pavol Malosek <malosek@fastmq.com>
+Peter Bourgon <peter.bourgon@gmail.com>
+Pieter Hintjens <ph@imatix.com>
+Piotr Trojanek <piotr.trojanek@gmail.com>
+Sebastian Otaegui <feniix@gmail.com>
+Steven McCoy <steven.mccoy@miru.hk>
+Tamara Kustarova <kustarova.tamara@gmail.com>
+Taras Shpot <taras.shpot@eleks.com>
+Tero Marttila <terom@fixme.fi>
+Terry Wilson <terry@logivox.net>
+Toralf Wittner <toralf.wittner@gmail.com>
+Vitaly Mayatskikh <v.mayatskih@gmail.com>
+
+Credits
+=======
+
+Aamir Mohammad <aamirjvm@gmail.com>
+Adrian von Bidder <avbidder@fortytwo.ch>
+Aleksey Yeschenko <aleksey@yeschenko.com>
+Alessio Spadaro <alessio.spadaro@finservice.com>
+Alexander Majorov <alexander.majorov@intel.com>
+Anh Vu <vietanh.vu@m4x.org>
+Bernd Schumacher <bernd.schumacher@hp.com>
+Brett Cameron <Brett.Cameron@hp.com>
+Brian Granger <ellisonbg.net@gmail.com>
+Carsten Dinkelmann <din@foobar-cpa.de>
+David Bahi <dbahi@novell.com>
+Dirk Eddelbuettel <edd@debian.org>
+Evgueny Khartchenko <Evgueny.Khartchenko@intel.com>
+Frank Vanden Berghen <frank@applied-mathematics.net>
+John Apps <john.apps@hp.com>
+Markus Fischer <markus.fischer@hpc-solutions.com>
+Matt Muggeridge <Matt.Muggeridge@hp.com>
+Michael Santy <Michael.Santy@dynetics.com>
+Oleg Sevostyanov <oleg.sev@gmail.com>
+Paulo Henrique Silva <ph.silva@gmail.com>
+Peter Busser <busserpeter@gmail.com>
+Peter Lemenkov <lemenkov@gmail.com>
+Robert Zhang <robert@scout-trading.com>
+Toralf Wittner <toralf.wittner@gmail.com>
+

src/zeromq/COPYING.LESSER

+		         GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions. 
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version. 
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
+
+--------------------------------------------------------------------------------
+
+              SPECIAL EXCEPTION GRANTED BY IMATIX
+
+As a special exception, iMatix gives you permission to link this library with
+independent modules to produce an executable, regardless of the license terms
+of these independent modules, and to copy and distribute the resulting
+executable under terms of your choice, provided that you also meet, for each
+linked independent module, the terms and conditions of the license of that
+module. An independent module is a module which is not derived from or based on
+this library. If you modify this library, you must extend this exception to your
+version of the library.
+
+--------------------------------------------------------------------------------
+
+Parts of the software are licensed under the MIT (X11) license as follows:
+
+Copyright (c) 2007-2010 Contributors as listed in AUTHORS
+
+ Permission is hereby granted, free of charge, to any person
+ obtaining a copy of this software and associated documentation
+ files (the "Software"), to deal in the Software without
+ restriction, including without limitation the rights to use,
+ copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following
+ conditions:
+
+ The above copyright notice and this permission notice shall be
+ included in all copies or substantial portions of the Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ OTHER DEALINGS IN THE SOFTWARE.
+

src/zeromq/INSTALL

+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007 Free Software Foundation, Inc.
+
+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
+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
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`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:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./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.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  6. 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.
+
+   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
+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.
+
+Installation Names
+==================
+
+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
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+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
+`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.
+
+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
+`--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:
+
+     OS KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"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'.
+`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
+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
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+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' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

src/zeromq/MAINTAINERS

+Component: Atomic Operations
+Maintainer: Martin Lucina
+Contact: mato@kotelna.sk
+
+Component: Lock-free Algorithms
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: TCP transport
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: IPC transport
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: PGM transport
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: In-process transport
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: I/O Threads
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Application Threads and Differnet Socket Types
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Multiplexing (zmq_poll)
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Devices
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Generic Infrastructure (context, mailbox, command, pipe)
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Documentation
+Maintainer: Martin Lucina
+Contact: mato@kotelna.sk
+
+Component: Autotools build system
+Maintainer: Mikko Koppanen, Martin Lucina
+Contact: mato@kotelna.sk
+
+Component: MSVC build system
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+
+Component: Performance tests
+Maintainer: Martin Sustrik
+Contact: sustrik@250bpm.com
+

src/zeromq/Makefile.am

+ACLOCAL_AMFLAGS = -I config
+
+SUBDIRS = src doc perf devices tests
+DIST_SUBDIRS = src doc perf devices tests builds/msvc
+
+EXTRA_DIST = \
+	autogen.sh	\
+	version.sh	\
+	MAINTAINERS	\
+	foreign/openpgm/@pgm_basename@.tar.gz	\
+	foreign/xmlParser/xmlParser.cpp		\
+	foreign/xmlParser/xmlParser.hpp
+MAINTAINERCLEANFILES = \
+	$(srcdir)/aclocal.m4		\
+	$(srcdir)/autom4te.cache	\
+	$(srcdir)/configure		\
+	`find "$(srcdir)" -type f -name Makefile.in -print`
+
+dist-hook:
+	@if test -d "$(srcdir)/.git"; \
+	then \
+		echo Creating ChangeLog && \
+		( cd "$(top_srcdir)" && \
+		  echo '# Generated by Makefile. Do not edit.'; echo; \
+		  $(top_srcdir)/config/missing --run git log --stat ) > ChangeLog.tmp \
+		  && mv -f ChangeLog.tmp $(top_distdir)/ChangeLog \
+		  || ( rm -f ChangeLog.tmp ; \
+		       echo Failed to generate ChangeLog >&2 ); \
+	else \
+		echo A git clone is required to generate a ChangeLog >&2; \
+	fi
+	-cp $(top_srcdir)/builds/redhat/zeromq.spec $(distdir)/zeromq.spec
+	-sed s/\@PACKAGE_VERSION\@/@PACKAGE_VERSION@/ -i $(distdir)/zeromq.spec
+	-rm -rf $(distdir)/foreign/openpgm/@pgm_basename@
+distclean-local:
+	-rm -rf $(top_srcdir)/foreign/openpgm/@pgm_basename@
+maintainer-clean-local:
+	-rm -rf $(top_srcdir)/config

src/zeromq/README

+Welcome
+-------
+
+The 0MQ lightweight messaging kernel is a library which extends the
+standard socket interfaces with features traditionally provided by
+specialised messaging middleware products. 0MQ sockets provide an
+abstraction of asynchronous message queues, multiple messaging patterns,
+message filtering (subscriptions), seamless access to multiple transport
+protocols and more.
+
+
+Building and installation
+-------------------------
+
+See the INSTALL file included with the distribution.
+
+
+Resources
+---------
+
+Extensive documentation is provided with the distribution. Refer to
+doc/zmq.html, or "man zmq" after you have installed 0MQ on your system.
+
+Website: http://www.zeromq.org/
+
+Development mailing list: zeromq-dev@lists.zeromq.org
+Announcements mailing list: zeromq-announce@lists.zeromq.org
+
+Git repository: http://github.com/zeromq/zeromq2
+
+0MQ developers can also be found on the IRC channel #zeromq, on the
+Freenode network (irc.freenode.net).
+
+Copying
+-------
+
+Free use of this software is granted under the terms of the GNU Lesser General
+Public License (LGPL). For details see the files `COPYING` and `COPYING.LESSER`
+included with the 0MQ distribution.

src/zeromq/autogen.sh

+#!/bin/sh
+#   Copyright (c) 2007-2010 iMatix Corporation
+#
+#   This file is part of 0MQ.
+#
+#   0MQ is free software; you can redistribute it and/or modify
+#   it under the terms of the GNU General Public License as published by
+#   the Free Software Foundation; either version 3 of the License, or
+#   (at your option) any later version.
+
+#   0MQ is distributed in the hope that it will be useful,
+#   but WITHOUT ANY WARRANTY; without even the implied warranty of
+#   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#   GNU General Public License for more details.
+
+#   You should have received a copy of the GNU General Public License
+#   along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+# Script to generate all required files from fresh git checkout.
+
+command -v libtool >/dev/null 2>&1
+if  [ $? -ne 0 ]; then
+    echo "autogen.sh: error: could not find libtool.  libtool is required to run autogen.sh." 1>&2
+    exit 1
+fi
+
+command -v autoreconf >/dev/null 2>&1
+if [ $? -ne 0 ]; then
+    echo "autogen.sh: error: could not find autoreconf.  autoconf and automake are required to run autogen.sh." 1>&2
+    exit 1
+fi
+
+mkdir -p ./config
+if [ $? -ne 0 ]; then
+    echo "autogen.sh: error: could not create directory: ./config." 1>&2
+    exit 1
+fi
+
+autoreconf --install --force --verbose -I config
+if [ $? -ne 0 ]; then
+    echo "autogen.sh: error: autoreconf exited with status $?" 1>&2
+    exit 1
+fi

src/zeromq/builds/msvc/Makefile.am

+LIBZMQ_DIST = libzmq/libzmq.vcproj platform.hpp msvc.sln
+
+DEVICES_DIST = zmq_queue/zmq_queue.vcproj \
+               zmq_streamer/zmq_streamer.vcproj \
+               zmq_forwarder/zmq_forwarder.vcproj
+
+PERF_DIST = c_local_thr/c_local_thr.vcproj \
+            c_remote_thr/c_remote_thr.vcproj \
+            c_local_lat/c_local_lat.vcproj \
+            c_remote_lat/c_remote_lat.vcproj
+
+EXTRA_DIST = $(LIBZMQ_DIST) $(DEVICES_DIST) $(PERF_DIST)