DevelopingWithFedoraAndCoda

When developing OpenISR with sources stored in Coda, your build and install directories should be kept outside of Coda to minimize Coda conflicts and allow you to develop from multiple machines. You should use private build and install directories so that you don't have to run make install as root, which would require you to have Coda tokens as root.

Installing dependencies

As root:

yum install fuse-devel fuse libcurl-devel zlib-devel xz-devel libuuid-devel \
        libarchive-devel gtk2-devel pygtk2 gtk-vnc-python rsync \
        autoconf automake libtool pkgconfig

Setting up directories

Assume three directories, $srcdir, $builddir, and $installdir. $srcdir is a checked-out OpenISR Git repository in Coda. $builddir and $installdir are not in Coda. Execute these commands as yourself, not as root.

1. cd $srcdir; ./autogen.sh
2. mkdir $builddir; cd $builddir
3. $srcdir/configure --prefix=$installdir
4. make; make install
5. Add $installdir/bin to your PATH

Developing

To test after making changes, you just need to do make install in $builddir and then run isr as normal.

It is safe to run make install from a subdirectory of $builddir, in which case only that part of the system will be updated.

If you want to run parcelkeeper directly, make install is not necessary; you can just do make; ./parcelkeeper <args> inside $builddir/parcelkeeper. However, you can't debug parcelkeeper by running gdb ./parcelkeeper inside $builddir/parcelkeeper; you have to say libtool --mode=execute gdb ./parcelkeeper.

Overriding the VMM

You can override the default VMM driver for a parcel by passing the -m flag to isr resume; e.g.:

isr resume myparcel -m shell

The shell VMM driver just starts a shell and waits for it to exit. It will print the path to the virtual disk image file before showing the first shell prompt.