For your configuration I would recommend multiple local clones. Once you
have the first petsc clone just do
git clone petsc petsc-clone-1
git clone petsc petsc-clone-2
Now you have three PETSc directories and can have different branches in
each. Note that git is “smart” and does not copy the entire repository for each
clone; it maintains one repository but three working directories.
The problem with using different PETSC_ARCH for each branch is that when you
switch the branches it will sometimes/often change an include file that many of
the C files are dependent on so make gmake will require recompiling much of the
library, with different working directories this will not happen.
Barry
On Sep 6, 2014, at 4:21 PM, Alp Kalpalp <[email protected]> wrote:
> Hi,
>
> Nowadays I am trying to build a branch and sometimes I am swittching back to
> master branch.
> I experienced that configuring and making a branch requires almost 30 minutes
> on cygwin.
> I wonder;
>
> 1- How do you manage more than one branches?
> 2- Do we need to reconfigure after a git pull?
> 3- Are switching back and forward in between branches like me? or just using
> seperate work-dir for each branch?
>
> please help me I am so exhausted to configure and make petsc!!!!
