Buildcpp/Configure filles need added, re-written, or modified.

[nusbaume]

The CAMDEN code is now at a point where it will run through "Buildcpp", but of course dies without any "configure" script present. So, I personally see at least three possible ways forward:

1. Copy the current CAM configure script into CAMDEN directly. This will be the quickest way to fix this issue, but will not improve this infrastructure in any meaningful way.

2. Write a new configure script, ideally in python. This will allow for the configure script to be cleaned-up and potentially improved (and reduce the reliance on perl). The disadvantage, of course, is that this will take time.

3. Add all the needed processes/actions into the "Buildcpp" script directly. This will provide the same benefits as option 2, but will also remove the "configure" script entirely. The dis-advantage of course is that this will also take time, and could make "buildcpp" a very large script (which could make readability worse).

What do you all think? I am happy to work on whatever option is decided on, but I didn't want to assign myself just yet in case someone else wants to tackle it instead.

[gold2718]

#3 FTW!
Advantage: It is one less file and the intent of buildcpp in the CIME infrastructure is to do what the old CAM configure script did.
Advantage: By building a data-driven configure process, the code should remain fairly compact. If it starts growing when we try to add additional features, we are not doing it right.

[nusbaume]

Great! I can go-ahead and take a first swing at this, at least up until the physics testbed compset is passing along everything it needs to.