Evolvotron is interactive "generative art" software to evolve
images/textures/patterns through an iterative process of random
mutation and user-selection driven evolution. If you like lava-lamps,
and still think the Mandelbrot set is cool, this could be the software
It uses C++ (and STL+Boost) & Qt (which is Qt Group's GUI
toolkit; it's ABSOLUTELY NOTHING TO DO WITH APPLE'S QUICKTIME!).
It's multithreaded (using Qt's threading API).
Home page: http://www.bottlenose.net/share/evolvotron
Author: timday at timday dot com
This file describes how to build evolvotron.
See the USAGE file for details of what the built executable can do.
If you manage to make practical use of evolvotron, especially
if evolvotron derived imagery makes it into print or other
mass media, I'd love to hear about it: please email!
This program 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 2
of the License, or (at your option) any later version.
This program 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, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
[The license should be in the LICENSE file in the same directory as this
There's no reason it shouldn't work on any platform with a correctly
set up qmake. You do NOT need to be root (there is no install stage).
In the top level directory, you can either do
qmake "VERSION_NUMBER=x.x.x" main.pro
or just have both done for you by doing
which will pick up the VERSION_NUMBER from the file VERSION in this directory.
Make will recurse into and build the libfunction & libevolvotron directories
(which is 99% of the work) and some additional subdirectories with
Among other things, this will give you an "evolvotron"
executable which you can run immediately with
and/or copy where you like (there are no shared libs or "resource files"
needing additional attention).
See the USAGE file (or in-app manual) for instructions.
The author mainly tracks Debian stable.
Non-linux platform issues
On the whole, Qt does an excellent job of insulating code from
platform specific details. However, there is a little bit of
linux-specific code in evolvotron.
If you don't have a PLATFORM_... define set, you'll get some warnings
about no default implementations of functions in platform_specific.cpp,
but should still get a working evolvotron (although missing some functionality
with regard to automatically choosing how many threads to run and controlling
All the platform specific code should live in
and is selected by compile options
-DPLATFORM_LINUX or -DPLATFORM_BSD
(with more potentially addable for other platforms).
Setting the appropriate build options is most easily set by editing
near the top of the
file. Qt doesn't make a fine enough distinction between unix platforms
to decide completely automatically, and the situation is further complicated
by e.g Fink's Qt not considering itself to be a Qt 'macx' build.
Many build failures are simply because the necessary Qt build tools
aren't in your path:
should both find something.
If you have gcc/c++ compile problems problems:
If you have to change anything, the chances are it should be changed in
common.pro. Remember that any Makefiles you can see are generated
by qmake from .pro files and therefore hacking on the Makefiles is
generally a fruitless exercise.
Some source releases have had problems with other versions of gcc than
the ones I test on. A COMPLETE record of a failed build would be
appreciated (including the initial display of the gcc version).
If you can fix it, then patches would be even better!
The evolvotron sources don't try to provide an installer.
The assumption is that packagers will have a better idea of where
files should be copied to on their systems, and the tools to do it.
will recursively descend into the various build directories, but
does nothing in each one.
The things you're likely to want to install are
(in order of interest):
The main executable and man page:
User documentation (standalone version of the builtin manual):
An HTML version of the above:
Command-line driven tools and their man pages:
There are NO extra supporting files built
(e.g shared libraries, config files, "resource" files)
which need to be in special places for the software to work.
There are a few things which might be useful to packagers:
- script to build .deb files (using the strangely unpopular
"yada", and pbuilder). This is used to build the .debs put
up on sourceforge, but the "official" Debian ones (and Ubuntu
derivatives) are more conventionally packaged by Gurkan Sengun.
Yada is obsoleted as of Debian's "Wheezy" release however.
- directory for contributed RPM related resources.
BUILDING CODE DOCUMENTATION
If you have doxygen (and graphviz too) and want to build
the source code documentation, execute
at the top level.
The code documentation then appears in ./doc/html/
This hasn't been tested in a long while now, although the
doxygen commenting style has been kept up.