Here are the steps to setup multiple uplinks through policy routing on Gentoo:

1. First of all, to access multiple networks, either you have multiple physical NICs or you need to configure your network uplink to let your network ports access multiple VLANs. For more information on VLANs configurations under Gentoo, you can check Gentoo Handbook section on VLANs.
2. On Linux kernel, you need to enable CONFIG_IP_MULTIPLE_TABLES option (in Linux kernel menuconfig, you find it under Networking support => Networking options => IP: policy routing). Recompile and install kernel.
3. Next, you need to install iproute2 package, which allows editing multiple routing tables:

   # emerge -av sys-apps/iproute2

4. Edit /etc/iproute2/rt_tables and add the following route table lines:

   100        T0
   101        T1

5. Edit your /etc/conf.d/net file to enable network startup configuration. First add the following lines, modifying addresses and interface names to suit your needs:

   config_eth0=( "192.168.0.100/24" )
   routes_eth0=(
       "192.168.0.0/24 src 192.168.0.100 table T0"
       "default via 192.168.0.1 table T0"
       "default nexthop via 192.168.0.1 weight 1"
   )
   rules_eth1=("from 192.168.1.1/32 table T0 priority 100" )
   
   config_eth1=( "192.168.1.200/24" )
   routes_eth0=(
       "192.168.1.0/24 src 192.168.1.200 table T1"
       "default via 192.168.1.1 table T1"
       "default nexthop via 192.168.0.1 weight 1"
   )
   rules_eth1=("from 192.168.1.100/32 table T1 priority 101" )

   Then uncomment the following functions (if you copied your /etc/conf.d/net from /etc/conf.d/net.example, they should be already there in comments):

   postup() {
          local x="rules_${IFVAR}[@]"
          local -a rules=( "${!x}" )
          if [[ -n ${rules} ]] ; then
                  einfo "Adding IP policy routing rules"
                  eindent
                  # Ensure that the kernel supports policy routing
                  if ! ip rule list | grep -q "^" ; then
                          eerror "You need to enable IP Policy Routing (CONFIG_IP_MULTIPLE_TABLES)"
                          eerror "in your kernel to use ip rules"
                  else
                          for x in "${rules[@]}" ; do
                                  ebegin "${x}"
                                  ip rule add ${x} dev "${IFACE}"
                                  eend $?
                          done
                  fi
                  eoutdent
                  # Flush the cache
                  ip route flush cache dev "${IFACE}"
          fi
   }
   
   postdown() {
          # Automatically erase any ip rules created in the example postup above
          if interface_exists "${IFACE}" ; then
                  # Remove any rules for this interface
                  local rule
                  ip rule list | grep " iif ${IFACE}[ ]*" | {
                          while read rule ; do
                                  rule="${rule#*:}"
                                  ip rule del ${rule}
                          done
                  }
                  # Flush the route cache
                  ip route flush cache dev "${IFACE}"
          fi
   
          # Return 0 always
          return 0
   }

6. Finally, reboot with your new kernel. My advice is to proceed with this step while you can access your machine locally, just in case anything goes wrong.

Some in-depth on what I described above: with policy routing you can insert additional routing tables and configure your system to use a set of rules to decide which table to apply for each IP packet. So if you create T0 and T1 tables, you can set your host to respond to requests from each interface back to the same interface and load balance routes going to outer network by giving the same weight to both gateways in generic route table.

If you use this setup to publish your server on multiple public networks, you will probably need to configure multiple DNS A records in round-robin over your IPs.

If you’re interested in more Gentoo tips, just subscribe to my feed or follow me on Twitter.

UPDATE: For more performance info, James Abley pointed me to a very complete benchmark of available Python asynchronous webservers. It looks like Tornado is a real monster of concurrency.

There are already some how-to’s on the web on plugging Django web framework into Tornado webserver. A quick recap:

1. A tutorial on Tornado, Django and nginx by Jeremy Bowers.
2. How to import django framework inside a Tornado project by Lincoln Loop.
3. A snippet by lawgon.

My approach is slightly different as I wanted to run Tornado using Django management command-line interface.

The 3 easy steps are:

1. Add Tornado module to your django setup. If you use buildout, add Tornado git checkout to buildout.cfg using minitage.recipe.fetch recipe, like this:

   [buildout]
   ...
   parts =
   ...
       tornado
       django
   ...
   
   [tornado]
   recipe = minitage.recipe.fetch
   urls = git://github.com/facebook/tornado.git | git | | ${buildout:parts-directory}/tornado
   
   [django]
   recipe = minitage.recipe.scripts
   initialization =
       import os
       os.environ['DJANGO_SETTINGS_MODULE']='project.settings.development'
   scripts =
       django
   eggs =
       Django
       ...
   entry-points=
       django=django.core.management:execute_from_command_line
   extra-paths =
       ${buildout:directory}
       ${tornado:location}
   ...

2. Next, create a command-line extension hierarchy in your project’s main app:

   $ mkdir project/myapp/management
   $ touch project/myapp/management/__init__.py
   $ mkdir project/myapp/management/commands
   $ touch project/myapp/management/commands/__init__.py

3. Last, add a runtornado.py script in project/myapp/management/commands/ folder with the following content:

   from django.core.management.base import BaseCommand, CommandError
   from optparse import make_option
   import os
   import sys
   
   class Command(BaseCommand):
       option_list = BaseCommand.option_list + ()
       help = "Starts a Tornado Web."
       args = '[optional port number, or ipaddr:port]'
   
       def handle(self, addrport='', *args, **options):
           import django
           from django.core.handlers.wsgi import WSGIHandler
           from tornado import httpserver, wsgi, ioloop
   
   	sys.stdout = os.fdopen(sys.stdout.fileno(), 'w', 0)
   	sys.stderr = os.fdopen(sys.stderr.fileno(), 'w', 0)
   
           if args:
               raise CommandError('Usage is runserver %s' % self.args)
           if not addrport:
               addr = ''
               port = '8000'
           else:
               try:
                   addr, port = addrport.split(':')
               except ValueError:
                   addr, port = '', addrport
           if not addr:
               addr = '127.0.0.1'
   
           if not port.isdigit():
               raise CommandError("%r is not a valid port number." % port)
   
           quit_command = (sys.platform == 'win32') and 'CTRL-BREAK' or 'CONTROL-C'
   
           def inner_run():
               from django.conf import settings
               print "Validating models..."
               self.validate(display_num_errors=True)
               print "\nDjango version %s, using settings %r" % (django.get_version(), settings.SETTINGS_MODULE)
               print "Server is running at http://%s:%s/" % (addr, port)
               print "Quit the server with %s." % quit_command
               application = WSGIHandler()
               container = wsgi.WSGIContainer(application)
               http_server = httpserver.HTTPServer(container)
               http_server.listen(int(port), address=addr)
               ioloop.IOLoop.instance().start()
   
           inner_run()

To run your tornado webserver, you just need to call your usual management program like manage.py with runtornado command, with the same syntax as runserver. In my case, I just run production server using supervisord, with a command like this:

$ ./bin/django runtornado --settings=project.settings.production 8000

If you found this quick how-to useful, remember to follow me on Twitter or subscribe to my feed for more django tips.

1. Flash applet audio capture is very limited: only one device a time, only one stereo channel pair and doesn’t support devices without volume level mixer. It doesn’t allow any advanced setup like multi-channel digital mixers.
2. Audio and video are encoded on the fly and no local copy is recorded. Streaming services offer server-side recording, but after downsampling and packet loss, quality is very low. Even worse: any connection fault will interrupt your recording.

To achieve multi-channel audio capture and client-side recording, live events media producers traditionally have few options:

1. Process audio and video signals with external mixer and recording tools and then acquire analog output signals with an AD capture card. This makes multi-channel recording more expensive. Furthermore, if signal processing passes through analog components, streaming quality is degraded and HD video must be downscaled.
2. Record your audio-video using your camera and then use camera Firewire or analog output to stream to computer. To do this, you need to have audio inputs on your camera. This has three downsides: your recorded session may have lower video quality (miniDV or miniHDV tape recording quality may be lower than firewire output quality), you cannot record multitrack audio and you need to connect your audio mixer to your camera.
3. Use a digital mixer coupled with Flash Media Encoder software, which is only available on Windows, so if you’re a Mac OS X or Linux user, you’re out of luck. Also, you cannot record high quality encoded files but only FLV as they’re sent over to the broadcast.
4. Use UStream Producer Pro, a $199 tool released by UStream.tv for Windows and Mac OS X, that allows multi-camera management, HDV input, PIP and broadcasting output recording, at the same quality of the output stream.

For my live streaming setup, I wanted to use my MacBook laptop with Mac OS X, a Sony HVR-V1 HDV camera connected through Firewire and a Edirol M-16DX 16-channel digital audio mixer connected via USB to capture audio from a few condenser microphones. Methods mentioned above aren’t applicable, because they would require additional hardware and recording quality would be very low, compared to original signal quality.

After some research, I found a way to process audio and video signals before submitting them to Flash applet in Mac OS X. First, the requirements:

1. CamTwist: it’s a freeware software that creates a loopback video interface and allows multiple client apps to access a single video device at the same time. A number of video effects can be applied to the video stream by CamTwist.
2. Jack audio router: an Open Source application that allows custom routing of audio channels between multiple devices and programs simultaneously with very low latency.
3. An account on UStream.tv with an available broadcasting channel setup.

Once you’ve installed the programs and created the account, you can use the following checklist to configure your system to route your advanced audio-video stream both to UStream.tv and to your custom recording tools:

1. Connect your external camera and audio sources and wait until they’re properly recognised by the system.
2. Run CamTwist and select your video input from the Step 1 column and adjust input settings in the “Settings” column on the right. If you want, you can add effects in column Step 2 (check CamTwist documentation for details). If you need a preview, you can use Tools -> Preview menu (close it afterwards, so that it doesn’t eat up cpu cycles).
3. Run JackPilot program and configure access to hardware device from JackPilot -> Preferences menu (it should open automatically on first use). You need to select your audio driver (typically coreaudio), your hardware interface (select your multi-channel card), your hardware-specific setup (frequency, number input and output of channels) and then set your virtual Jack card channels and untick “Auto connect with physical ports”.
4. Once you’re done with Jack setup, close Preferences dialog and start Jack audio server by clicking on Run button in main dialog.
5. Open your audio-video recording tool and select CamTwist from available video input interfaces and JackRouter from audio input interfaces and start a new recording. For instance, if you use QuickTime to record your session, go to QuickTime -> Preferences menu and select Recording tab. In Video Source drop-down menu select CamTwist and in Microphone menu select JackRouter, then close dialog and open a new session with File -> New video recording menu and click on Record button to start recording. Important: if you don’t start recording, your tool may not show up in your Jack router setup, so do as you’re told
6. Open your browser (Firefox is better) and connect to UStream.tv, login with your account and click on Broadcast now button. A popup will open and once Flash applet is loaded, you can select your audio and video inputs just below the preview frame. Select CamTwist from Video drop-down menu and JackRouter from Audio menu. Check that you see video from your source in preview frame.
7. Go back to JackPilot and click on Routing button to open Routing panel. The panel contains 3 frames: on the first frame, you have your physical captures and your application audio outputs, on the second frame you have your physical outputs and your application inputs and on the third frame there’s a list of connection. What you have to do is create a series of mappings between items in first frame to items in second frame. To create a mapping, you need to select one item in first frame and double-click on item on second frame. To unbind the mapping, just repeat the same action again. In my setup, I create a mapping between stereo mix-down channels 17 and 18 of my mixer and Flash (Firefox) stereo input channels and then a mapping between the same mix-down channels and QuickTime stereo input. If you use a multi-track recording program like Cubase, you can add more virtual channels to Jack Router (in Preferences) and map each mixer input to its own virtual channel. Remember: if you need to change Jack Router settings to add more channels or change interface settings, you have to shut down Jack with Stop button first.
8. Now you’re ready to click on Broadcast button on your UStream.tv channel and go live. Check audio level with Flash Vu-meter and adjust volume slider accordingly. For what regards audio and video quality sliders, my advice is to keep audio above 70 and video at least 50: the more bandwith you have, the more you can raise video.

Be careful: audio and video streams are not synchronized, because there’s no common clock or timecoding between the source peripherals. This means that long audio-video sessions might get slightly out of sync if processing time is different between audio and video. My advice is to check wether your camera and audio mixer support timecoding synchronization in a common format: if they do, then set up a link between the two. If they don’t (which is probably your situation, if you’re using consumer devices), avoid running other cpu-intensive or disk-intensive processes during the streaming/recording activity and use a post-production tool like FinalCut Pro or Adobe Premiere Pro to match audio and video on recorded files by shifting and stretching appropriately. I will write more on this later.

That’s all. Have you found other ways to accomplish the same result? Need some hints for your setup or troubleshooting? Please share your thoughts using the comments box below and remember to subscribe to my feed for additional tips on AV techniques.

P.S.: Special thanks goes out to Maurizio Tognoni, who shared the hacking and testing efforts.

*~
*.orig
*.pyc
*.rej
.installed.cfg
__minitage__*
bin/*
develop-eggs
downloads
eggs
log
parts
project/media/uploads
tmp

As usual, feel free to post your additions as comments.

Shell prompt

First of all, you should check you’re using bash shell:

$ env | grep ^SHELL=
SHELL=/bin/bash

If not, you should check if bash package is already installed. If it’s already there, just change your user shell (and possibly root shell) with chsh or consult your OS manual. Be careful: if bash is not listed in /etc/shells, you might lock yourself out.

To set Gentoo-like colors on bash prompt, edit ~/.profile (or /etc/profile for system-wide defaults) and add the following:

if [[ ${EUID} == 0 ]] ; then
        PS1='\[\033[01;31m\]\h\[\033[01;34m\] \W \$\[\033[00m\] '
else
        PS1='\[\033[01;32m\]\u@\h\[\033[01;34m\] \w \$\[\033[00m\] '
fi

GNU ls

If you use GNU ls (use –version to check) and dircolors utility is available (from GNU coreutils), you can have colorful outputs by adding the following snippet to your bash profile (see above):

if type -P dircolors >/dev/null ; then
        if [[ -f ~/.dir_colors ]] ; then
                eval $(dircolors -b ~/.dir_colors)
        elif [[ -f /etc/DIR_COLORS ]] ; then
                eval $(dircolors -b /etc/DIR_COLORS)
        fi
fi
alias ls='ls --color=auto'

To enable colors, you need to save Gentoo color defs to ~/.dir_colors (or /etc/DIR_COLORS for system-wide defaults).
Alternatively, if you miss dircolors binary on your system, save output from dircolors on a Gentoo machine and copy’n'paste it into bash profile:

LS_COLORS='...weird colon-separated string...'
export LS_COLORS
alias ls='ls --color=auto'

BSD ls implementation

A special trick is required for FreeBSD and Mac OS X: add the following line to your bash profile:

export CLICOLOR=1 LSCOLORS="ExGxFxDxCxDxDxhbhdacEc"

If you want to further customize colors on your Mac OS X Terminal, you can use SIMBL TerminalColours plugin (Snow Leopard version).

GNU grep

You can enable coloring of the matched part by appending the following alias to your bash profile:

alias grep='grep --colour=auto'

As usual, if you have any coloring tips’n'tricks you want to share, please use the comment box below.

UPDATE: Vinicius Mendes commented on using django.template.loaders.app_directories.Loader to solve the problem (a similar module exists for eggs, which is named django.template.loaders.eggs.Loader). It’s definitely the easiest way if you don’t mind importing all of your applications templates. Instead, if you need to pick only selected directories or non-standard directory names, keep on reading.

The solution is to add a dynamic path that is resolved at runtime using add-on egg’s path. Here’s an example of how I got django-reversion templates added:

import os
from  pyclbr import readmodule_ex

TEMPLATE_DIRS = (
    os.path.join(os.path.dirname(__file__), "../templates"),
    os.path.join(os.path.dirname(readmodule_ex('reversion')['__path__'][0]), "templates"),
)

ldap: This does an LDAP lookup using a query in the form of a URL, and returns attributes from a single entry. There is a variant called ldapm that permits values from multiple entries to be returned. A third variant called ldapdn returns the Distinguished Name of a single entry instead of any attribute values.

In some situations, it would be interesting to have a fourth query type: a lookup type that returned multiple DNs.

For instance, if your LDAP database also serves a DNS server with an ldap backend, your DNS subtree entries may look like this:

dc=mail, dc=example, dc=com, ou=domains, o=MyCompany, c=US

In this case, you could extract MX records from a list of DNs that match a particular filter like:

(&(objectClass=dNSDomain)(mXRecord=* $primary_hostname))

The complete query may look like this:

domainlist local_domains = @ : ${sg{${tr{${sg{${sg{${lookup ldapmdn { \
    ldap:///??sub?(&(objectClass=dNSDomain)(mXRecord=10 $primary_hostname))} { $value } \
    }}{,ou=domains,o=MyCompany,c=US}}}{}}}{dc=}{}}}{,}{.}}}{\n}{ : }}

To achieve this result, you need a small extension that enables a new query type called ldapmdn, whose syntax is similar to ldapdn but allows for multiple DNs. Here’s the patch for exim 4.69:

--- src/drtables.c.orig
+++ src/drtables.c
@@ -281,6 +281,23 @@
 #endif
   },

+/* LDAP lookup, allowing DN from more than one entry to be returned */
+
+  {
+  US"ldapmdn",                   /* lookup name */
+  lookup_querystyle,             /* query-style lookup */
+#ifdef LOOKUP_LDAP
+  eldap_open,       /* sic */    /* open function */
+  NULL,                          /* check function */
+  eldapmdn_find,                 /* find function */
+  NULL,                          /* no close function */
+  eldap_tidy,       /* sic */    /* tidy function */
+  eldap_quote       /* sic */    /* quoting function */
+#else
+  NULL, NULL, NULL, NULL, NULL, NULL /* lookup not present */
+#endif
+  },
+
 /* Linear search of single file */

   {
--- src/lookups/ldap.c.orig
+++ src/lookups/ldap.c
@@ -83,6 +83,7 @@
 #define SEARCH_LDAP_SINGLE 1         /* Get attributes from one entry only */
 #define SEARCH_LDAP_DN 2             /* Get just the DN from one entry */
 #define SEARCH_LDAP_AUTH 3           /* Just checking for authentication */
+#define SEARCH_LDAP_MULTIPLE_DN 4    /* Get just the DN from multiple entries */

 /* In all 4 cases, the DN is left in $ldap_dn (which post-dates the
 SEARCH_LDAP_DN lookup). */
@@ -185,6 +186,7 @@
     "sizelimit=%d timelimit=%d tcplimit=%d\n",
     (search_type == SEARCH_LDAP_MULTIPLE)? "m" :
     (search_type == SEARCH_LDAP_DN)? "dn" :
+    (search_type == SEARCH_LDAP_MULTIPLE_DN)? "mdn" :
     (search_type == SEARCH_LDAP_AUTH)? "auth" : "",
     ldap_url, server, s_port, sizelimit, timelimit, tcplimit);

@@ -577,7 +579,8 @@
     entries, the DNs will be concatenated, but we test for this case below, as
     for SEARCH_LDAP_SINGLE, and give an error. */

-    if (search_type == SEARCH_LDAP_DN)   /* Do not amalgamate these into one */
+    if (search_type == SEARCH_LDAP_DN ||
+      search_type == SEARCH_LDAP_MULTIPLE_DN) /* Do not amalgamate these into one */
       {                                  /* condition, because of the else */
       if (new_dn != NULL)                /* below, that's for the first only */
         {
@@ -820,7 +823,8 @@

 /* The search succeeded. Check if we have too many results */

-if (search_type != SEARCH_LDAP_MULTIPLE && rescount > 1)
+if (search_type != SEARCH_LDAP_MULTIPLE &&
+	search_type != SEARCH_LDAP_MULTIPLE_DN && rescount > 1)
   {
   *errmsg = string_sprintf("LDAP search: more than one entry (%d) was returned "
     "(filter not specific enough?)", rescount);
@@ -1126,6 +1130,14 @@
 return(control_ldap_search(ldap_url, SEARCH_LDAP_AUTH, result, errmsg));
 }

+int
+eldapmdn_find(void *handle, uschar *filename, uschar *ldap_url, int length,
+  uschar **result, uschar **errmsg, BOOL *do_cache)
+{
+/* Keep picky compilers happy */
+do_cache = do_cache;
+return(control_ldap_search(ldap_url, SEARCH_LDAP_MULTIPLE_DN, result, errmsg));
+}

 /*************************************************
--- src/lookups/ldap.h.orig
+++ src/lookups/ldap.h
@@ -16,6 +16,8 @@
                  uschar **, BOOL *);
 extern int     eldapm_find(void *, uschar *, uschar *, int, uschar **,
                  uschar **, BOOL *);
+extern int     eldapmdn_find(void *, uschar *, uschar *, int, uschar **,
+                 uschar **, BOOL *);
 extern void    eldap_tidy(void);
 extern uschar *eldap_quote(uschar *, uschar *);

In vanilla django, using “manage.py sql” or “manage.py sqlindexes” you can generate respectively “CREATE TABLE” and “CREATE INDEX” sql statements to setup your database schema (if you use manage.py syncdb, generated sql is feeded into your database). Table names are defined in db_table variable in model’s meta class and default name is generated using the following statement in django.db.models.options:

self.db_table = "%s_%s" % (self.app_label, self.module_name)

Now, if your generated db_table is greater than 64 characters (quite easy if your application name is long), django doesn’t truncate it and when sql is feeded into mysql, table creation routine will fail. A similar trouble happens for index creation routine (typically used with unique constraints) and using dmigrations tool instead of plain syncdb doesn’t get any better.

At this point, there are two options for table naming:

1. Renaming tables in models.py by hand (quite boring if your project is big).
2. Patching django to apply a truncation to db_table.

For option 2, here’s the simple one-liner patch you need for django 1.1.1:

--- django/db/backends/mysql/base.py.orig
+++ django/db/backends/mysql/base.py
@@ -214,6 +214,9 @@
         second = '%s-12-31 23:59:59.99'
         return [first % value, second % value]

+    def max_name_length(self):
+        return 64
+
 class DatabaseWrapper(BaseDatabaseWrapper):

     operators = {

In dmigrations, index names are defined as:

index_name = '%s_%s_%s' % (app, model, column)

You can fix the length problem in r29 with this simple patch:

--- dmigrations/mysql/migrations.py.orig
+++ dmigrations/mysql/migrations.py
@@ -141,7 +141,7 @@
     def __init__(self, app, model, column):
         model = model.lower()
         self.app, self.model, self.column = app, model, column
-        index_name = '%s_%s_%s' % (app, model, column)
+        index_name = '%s_refs_id_%s' % (column, abs(hash((app, model, column))))
         super(AddIndex, self).__init__(
             sql_up = [self.add_index_sql % (index_name, app, model, column)],
             sql_down = [self.drop_index_sql % (app, model, index_name)],

You can find download and install instructions to start a buildout barebone here, however I will do a small recap:

First, check that your python installation has setuptools installed (platform-specific install instructions here).

Then run the following commands to create your new project and fetch bootstrapping script:

$ mkdir projectdir
$ cd projectdir
$ wget http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py
$ mkdir downloads # this is needed, as buildout won't create it by itself.

Next step is writing buildout.cfg, an ini-style configuration file that specifies the setup for your deployment. The generic section is named “buildout” and its “parts” attribute refers to other sections that must be evaluated. I’ve created two parts: an example named “myproject”, which downloads, builds and installs a couple of fake eggs with wxPython in PYTHONPATH and a “wxPython” part, which downloads, builds and installs wxPython inside “parts” directory.

Each part is evaluated using a recipe, which is a plugin that is dynamically download from eggs repository or any other repository you pass through a find-links attribute. For my purposes I’ve employed two recipes from minitage project, a software deployment project developed by a nice french dude called kiorky (you can chat with him and obtain support at #minitage on irc.freenode.net).

[buildout]
download-cache = downloads
parts =
    wxPython
    myproject

[myproject]
recipe = minitage.recipe.egg
eggs =
    myegg
    myotheregg
extra_paths = ${wxPython:location}/lib/python

[wxPython]
recipe = minitage.recipe.cmmi
url = http://downloads.sourceforge.net/wxpython/wxPython-src-2.8.10.1.tar.bz2
post-make-hook = ${buildout:directory}/hooks.py:wxpython_post_make_hook
configure-options =
    --enable-debug --enable-debug_gdb # replace with --enable-optimize in production code
    --enable-display
    --enable-geometry
    --enable-graphics_ctx
    --enable-mediactrl
    --enable-sound
    --enable-unicode
    --with-libjpeg=builtin
    --with-libpng=builtin
    --with-libtiff=builtin
    --with-opengl
    --with-sdl
    --with-zlib=builtin
# Platform-dependent options, add as needed. Platform names are from sys.platform.lower().
configure-options-darwin = --with-mac --enable-monolithic
configure-options-linux2 = --with-gtk2

Configure-make-make-install recipe, namely minitage.recipe.cmmi, has a series of special options called “hooks” that allow extending the building process with non-standard actions through python code. I’ve added a call to wxpython_post_make_hook in hooks.py to deal with special post-install code:

import os
import sys
import subprocess

def wxpython_post_make_hook(o, b):
    return subprocess.call([sys.executable, 'setup.py',
        'WX_CONFIG=%s' % os.path.join(o['location'], 'bin', 'wx-config'),
        'BUILD_GIZMOS=0', 'BUILD_STC=0',
        'install', '--home=%s' % o['location'],
        ], cwd=os.path.join(o['compile-directory'], 'wxPython'))

Please note that I’ve disabled gizmos and stc support from wxPython, because I don’t need them and  they would require additional building in contrib.

Finally, launch the bootstrapping code:

$ python2.6 ./bootstrap.py

Of course, if you have a different version of python installed, adjust the command accordingly.

Now buildout is ready to be executed with:

$ ./bin/buildout

That’s all folks!