Port existing project

Before porting your project, you may wish to take a look at documentation on the transition to the new $G.

At this point, porting existing projects along with their source control histories involves CVS operations that can only be done by an administrator. Please see Brad if you need help with this process.

There are a few things to check for when migrating existing code.

• Organize the directories according to how you want them stored in CVS.

• Often existing projects use .C and .H suffixes. Where reasonable convert them to .cpp and .h.

• Some existing projects duplicate code already in CVS. If there is any duplicate code eliminate it and revise your code to use the common code.

• We would like to develop architecture neutral software. Where reasonable rewrite code that is not portable. Your code should not rely on Unix utilities or use links. We are standardizing on Python as a scripting language as it is easy to write portable scripts with it. You're not expected to completely port software; just avoid making that hard to do should someone want to in the future.

• Eliminate compiler warnings where possible. The build system lets you compile your code with several compilers; each of which will issue different warnings. Try out as many as you can. This process will often find bugs and in the long run saves everybody time.

• If the package uses libraries that are not already supported you will need to set them up.