On Wed, Nov 21, 2012 at 6:44 PM, Derek Gaston <firstname.lastname@example.org> wrote:
I simply stated that the new system, for me, is frustrating.
Since you are asking, let me give you an example:In the old system, this was my libMesh workflow.svn up./configure && make -j24 && METHOD=dbg make -j24Then, I would make a change in some file in libMesh and rebuild using:make && METHOD=dbg makeNothing is simpler than that.Now let's examine the new system:svn up
./bootstrap # if even possiblemkdir build_optcd build_opt
make -j24make installcd ..mkdir build_dbgcd build_dbgexport METHOD=dbg../configure --prefix=~/libmesh_install
make -j24make install
Then I go make a change to libMesh and need to do:cd build_optmakemake installcd ..cd build_dbgexport METHOD=dbgmakemake installEvery single change I must now go into two different directories to build AND I must run "make install" for each one.
"make install" BTW is a non-trivial operation. On slow network filesystems it can take a significant amount of time.
We were trying to debug the PETSc issue we're having with the new build system yesterday... and holy smokes it is frustrating to make a tiny change then have to wait around while cd'ing to different directories and building and make installing. It is FRUSTRATING.