...
For read-only repository access:
| No Format |
|---|
git clone git://fiz.stanford.edu/git/ramcloud.git
cd ramcloud
git submodule update --init
ln -s ../../hooks/pre-commit .git/hooks/pre-commit
|
...
For those with fiz accounts clone from here for write access:
| No Format |
|---|
git clone ssh://fiz.stanford.edu/git/ramcloud.git
cd ramcloud
git submodule update --init
ln -s ../../hooks/pre-commit .git/hooks/pre-commit
|
...
CentOS 5.5 has ancient default versions of g++ and Python. Fortunately there is an optional gcc4.4 "preview" package and we've installed Python 2.7 from source on the development machines. To make use of them by default, do the following:
| No Format |
|---|
mkdir -p ~/bin
cd ~/bin
ln -s /usr/local/bin/python27 python
ln -s /usr/bin/gcc44 gcc
ln -s /usr/bin/gcc44 cc
ln -s /usr/bin/g++44 g++
ln -s /usr/bin/g++44 c++
|
...
Next, update your LD_LIBRARY_PATH to include /usr/local/lib. If you do not do so, you'll get cryptic errors claiming libramcloud.so cannot be found. It can, but some of its dependencies in /usr/local/lib cannot. Do the following:
| No Format |
|---|
echo "export LD_LIBRARY_PATH=/usr/local/lib" >> ~/.bashrc
export LD_LIBRARY_PATH=/usr/local/lib [or log out and back in]
|
...
We have a comprehensive style guide for how code should be formatted in RAMCloud. Please check it out or we'll probably ask you to reformat your patchesActually, we don't quite follow what that style guide says, but we do keep a consistent style.
If you use GNU EMACS this configuration can help.
...