[Chromium-users] running chromium

[Peter K. <kir...@at...>]

Have others noticed chromium's cvs progressing?  Lately 20-30 files a
day are being updated. I built chromium( cvs 6/18/01) on Linux, but I
was unclear on how to run it or what the results should be.  I read the
archives, looked at some of the code, and made a few lucky guesses.
Here's what I remember:

1)Python-2.0 is required in order to *build* (doh!) not just run.  I
changed cr/config/Linux.mk:
    PYTHON=/usr/local/src/Python-2.0.1/python
    LDFLAGS += -L/usr/X11R6/lib -L/usr/local/src/gm/binary/lib
    CFLAGS += -DLINUX -Wall -Werror -I/usr/local/src/gm/binary/include
    and the same for CXXFLAGS
    This said, I haven't actually verified gm operation.
    The make completed without a hitch.

2) some of the executables like to find their .so's in the current
working directory.  Is it a win32 thing? A direct approach is to run
crserver from cr/lib/linux .  For convenience,
    cd cr/lib/Linux
    ln -s ../../bin/Linux/* .
to pick up the executables

3) I set up my login to export the cr/lib/Linux dir in the
LD_LIBRARY_PATH and to export CRMOTHERSHIP set to the hostname that will
be running mothership (invoked by "python mural.conf").  I put my
python2 installation in my path before other pythons.

4) Customize cr/mothership/server/mural.conf for your system.  At first
glance it may be unclear what to change and what to leave alone.  Here
are my suggestions for a first-time test.

line 9-ish
    TILE_COLS=1
    TILE_ROWS=1
        # this is a single-server test...

line 22-ish
    SPUdir = '/usr/local/src/cr/lib/Linux'
        #again, we've linked the executables from this directory

line 24-ish
    clientnode = CRApplicationNode( 'myappnode')
        # at the risk of belaboring the obvious,
        #    replace myappnode with the hostname that will run your
application

line 27-ish

clientnode.SetApplication(r'/usr/local/src/wiregl_1.2.1/bin/Linux/atlantis')

        # Maybe the path isn't needed but it helps remove ambiguity.
        # Pick your favorite. For me the glut atlantis demo makes a
handy self-animating test.
        # btw the leading "r" leaves backslashes in, a nice thing for
windows folks,
        #      see http://www.python.org/doc/current/ref/strings.html

line 40-ish
    node=CRNetworkNode('server%d' % (row*TILE_COLS + col ))
        # note row and col start at zero... so 'server0' is the first
server hostname
        # perhaps just put in the hostname for the single server this
time around, i.e.
        # node=CRNetworkNode('server0');

5) start in sequence the mothership, the crserver, and the crappfaker
    a) on CRMOTHERSHIP,
            cd cr/mothership/server
            python mural.conf
There will ordinarily be no output on this xterm until step b:

    b) on server0 (through n)
            cd cr/lib/Linux
            ./crserver

There will be lots of verbose dialog displayed on this xterm and
mothership's if the connection is successful.  Some messages (e.g. "Got
a line: quit" and "Bye") are fine, they only sound dire.  crserver will
open a window (until there is something to draw you'll just see the
frame) on server0.

    c) on myappnode
            cd cr/lib/Linux
            ./crappfaker

There will be a bunch of debug messages from from this xterm and a
continuing stream of messages on the crserver xterm.  'atlantis' will be
showing/animating on server0 in the 'Chromium Render SPU" window (but if
you obscure the GLUT Atlantis demo window on myappnode, the animation
stops).


Pete